I Deployed the code to live server. Its CentOs using vhosts.
I am having difficulties debugging. It does not shows laravel error with stack trace. It takes directly to apache 500 error page.
Error Screenshot
Although, it logs the error in storage/logs/laravel.log. It is really cumbersome to debug through laravel.log file.
PS. There are some other sites ruuning on vshosts which I don't want to get messed up if I change server setting.
So it's work as it should. Stack trace on production is not a good idea. But, if you really need it go to .env file and set:
APP_DEBUG=true
Related
So I have anaconda installed and make a separate environment for all my projects. Normally I just use PYDEV to create a new interpreter pointing to the anaconda enviornment and load the project in eclipse and all is good. After doing the last one though 95% of the time I go to debug I keep getting the error
An internal error occurred during: "Debug Source Lookup".
java.lang.IllegalArgumentException
The other 5% it kind of works as I can follow one script or a function before it starts breaking.
I've tried reloading the project, interpreter and conda enviornment to no luck. All my past projects which use to work are also now giving the same error.
The funny thing is when I'm in the debug perspective though it does seem to be working (I can see the Variables and use the interactive console to test stuff), but anytime I try to step into, over ect I get the error (even though it does seem to be working). So for the image above I can go through the code fine until it tries to jump to the other file which throws the error, but if I step into it I can manually open that file and walk through the function (just each step throws the error) and still interact with the code which is in the position through the console.
Any ideas how to fix?
Well, it may be something specific to this use-case (for instance, if the code for some object is evaluated and the source code is not really available for the debugger this is actually expected).
Can you provide the full stacktrace from the error log? (see: http://www.pydev.org/faq.html#HowdoIReportaBUG for details on how to get it)
I've been having trouble getting a weblogic server to run in eclipse, which have resulted in me not being able to open eclipse ni my current workspace at all. It is not my first attempt to work with weblogic servers in eclipse, and I do not know why it suddenly decided to stop working. I have had multiple errors, which all seem to be related to an abnormal high memory consumption.
One of my last errors, before eclipse quit on me for good, was an out of memory exception, on PermGenSpace. I set variables to 1024m, but it still complained it wasn't enough. After a lot of restarts, Eclipse suddenly wouldn't open my current workspace. I have tried others, and they work fine, but with my current one, the splash/loading screen disappears after about 10% of the loading bar is complete, and nothing happens at all. Except the fact that eclipse.exe shows up in the running processes tab on Windows task list. It does not show in the running programs list.
My attempts to start weblogic servers had the exact same symptoms. They showed in the process list, but did not respond when I tried to open the console in my browser.
Both eclipse and the weblogic tasks (shown as java.exe) has had over 400.000KB of memory consumption each, which I find very high.
I do not expect anyone to be able to find a complete solution here, but I am absolutely stuck. I cannot access any of my previous error messages. I have no experience debugging an error like this. Does anyone have any idea on how to find the error in a case like this?
My Weblogic version is 10.3.2, which is a company standard for now.
My Eclipse version is:
Eclipse Java EE IDE for Web Developers.
Version: Kepler Service Release 2
Build id: 20140224-0627
Adding the comment as an answer since it provided some help.
Try starting up to a new empty workspace; If you dont get to select workspace at startup use the argument "-data " If you still get issues, look at the log in /.metadata/.log
I installed the Redmine-Mylyn-Connector in Eclipse and had our admin install the Mylyn-Plugin for Redmine. The connection to Server seems to work:
When I try to add a query, I receive a Server Error:. Unfortunately no more details are available.
What are potential reasons for this error, and how can I solve the problem?
There might be useful details in the Error Log. Open the Error Log view (Alt+Shift+Q then L, or use Window > Show View...). I would clear the log first (using the red X button in its toolbar), then reproduce the error. You should see error details in the Error Log which might point you to the source of the problem.
I'm working on win 7 and trying to get Zend Eclipse to run properly for a CakePHP project. But when try to access the plugin list via the welcome page I get this error:
A problem occurred while accessing the update site.
RemoteBundleDiscoveryStrategy failed with an error
Unable to read repository at http://downloads.zend.com/studio-eclipse/updates-extra/10_0/pdt_directory.xml.
Connect timed out
I've tried severalt solutions I found on the net but nothing worked. My proxy settings are fine since I can access all sites via the internal browser of eclipse. My guess is, that there is some restriction in the Windows administration that is keeping me from getting the plugin list.
When I try to update Eclipse the update window tries half an hour to contact the software site and after that I get this error message:
Some sites could not be found. See the error log for more detail.
Communication with repository at http://downloads.zend.com/studio-eclipse/updates/10_0 failed.
Connect timed out
Finally!!
The problem was that is were actually two problems. First one was that Eclipse wasn't saving the username and password for the proxy settings. After finally finding the eclipse error log in
"{eclipse-workspace}/.metadata/.log"
(there seems to be no way to view the file in zend-eclipse itself) I found out that Eclipse was trying to save the password-file into the Administrator's user directory but had no access. (Oh what a surprise)
Putting this into the "zend-eclipse-php.ini" worked for me:
-eclipse.keyring C:\eclipse\keyring.txt
After this was done I could finally save username and password for the proxy but still no connection. When I took another look into the error log I found this error:
"!MESSAGE System property http.proxyHost is not set but should be {proxyname}
!MESSAGE System property http.proxyPort is not set but should be {proxyport}"
and 4 more for https and socks. After googling this error I came upon a fixed bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=281472
where it states that maybe the proxy refuses SOCKS. So I cleared the settings for SOCKS and tried again and IT WORKED! Finally!
Hope this description can anyone else with these problems.
There is a problem that I can't resolve. I am developing a project and test on my computer which runs as expected. But when I move the project to testing server, which also has Zend Server CE, it gives blank page. Display errors function is ON and I put try catch at the very begining, but it still shows a blank page. When ever I write "exit;" command at the end of related view script, page works normally!
What can couse this problem ?
Thanks
My first guess would be a problem with your include path. That's a very common issue when deploying from one server to another.
But clearly it's some kind of fatal error. I haven't used Zend Server, but in Apache I'd look in the error_log, since any fatal error output ends up there. Does Zend Server have something similar?
...aha, Zend Server seems to have a log, accessed through Monitor > Logs in the admin interface. Try looking in the PHP Error Log for reports of fatal errors.