[PHP] Guaranteed Way to Get Error Message Wanted
It looks like you are running the thread-safe version with FastCGI, which I understand to be counter to the recommendations. Thank you for the comment. I switched to PHP5.4.17-NTS-VC9, but the application still crashes. And still no clue as to why. So, still looking for that magic method to get PHP to report what's happening on a 500 Internal Server Error when it's (presumably? not sure...) not the server's fault. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Guaranteed Way to Get Error Message Wanted
On 6 July 2013 19:50, Brian Smither bhsmit...@gmail.com wrote: It looks like you are running the thread-safe version with FastCGI, which I understand to be counter to the recommendations. Thank you for the comment. I switched to PHP5.4.17-NTS-VC9, but the application still crashes. And still no clue as to why. So, still looking for that magic method to get PHP to report what's happening on a 500 Internal Server Error when it's (presumably? not sure...) not the server's fault. Have you got all your extensions updated? Enable display_startup_errors. Try running the command line PHP ... php -r echo 1; With your config. Just to see if there is anything ultra obvious missing. -- Richard Quadling Twitter : @RQuadling
[PHP] Guaranteed Way to Get Error Message Wanted
Have you got all your extensions updated? I would think so. Just to state the required disclaimers: phpinfo.php with ? phpinfo() ? works. Liberally peppering a tracer routine throughout the application shows it is getting executed up until one spot. But there is nothing obviously wrong with the code. Nothing! That's why I need the guaranteed message delivery on why PHP does not like the code. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Guaranteed Way to Get Error Message Wanted
On 6 July 2013 21:45, Brian Smither bhsmit...@gmail.com wrote: Have you got all your extensions updated? I would think so. Just to state the required disclaimers: phpinfo.php with ? phpinfo() ? works. Liberally peppering a tracer routine throughout the application shows it is getting executed up until one spot. But there is nothing obviously wrong with the code. Nothing! That's why I need the guaranteed message delivery on why PHP does not like the code. Turn on all your error reporting/logging. Add a try/catch if appropriate. Turn off any unhandled exception processing. Load in XDebug and get a trace going, what is the code doing prior to failure? -- Richard Quadling Twitter : @RQuadling
[PHP] Guaranteed Way to Get Error Message Wanted
I have an application running under PHP-5.4.17-TS-VC9 (and .14 as of yesterday) with Aprelium's Abyss X1 v2.8 web server in FastCGI mode on WinXPSP3. An earlier version of this application works. The current version causes a 500 Internal Server Error. There is no entry in PHP's (fully active) error log. I cannot decipher Abyss's logging, so I cannot determine if a clue was reported by Abyss or not. The current version works on a different system (Server 2003, PHP 5.3.5-TS-VC6 (Apache module), Apache 2.2). What I would like to have is a method of getting PHP to report in some undeniable manner, short of total system failure, what it doesn't like about whatever killed it. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP] Guaranteed Way to Get Error Message Wanted
Check the permissions on the files/directories involved. I get this on Linux when the files/directories are too open. Ken At 05:38 PM 7/5/2013, Brian Smither wrote: I have an application running under PHP-5.4.17-TS-VC9 (and .14 as of yesterday) with Aprelium's Abyss X1 v2.8 web server in FastCGI mode on WinXPSP3. An earlier version of this application works. The current version causes a 500 Internal Server Error. There is no entry in PHP's (fully active) error log. I cannot decipher Abyss's logging, so I cannot determine if a clue was reported by Abyss or not. The current version works on a different system (Server 2003, PHP 5.3.5-TS-VC6 (Apache module), Apache 2.2). What I would like to have is a method of getting PHP to report in some undeniable manner, short of total system failure, what it doesn't like about whatever killed it. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
