Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:php_503_error [2014/02/05 17:09] Michael [3. Opcode Caches (APC, xCache, EAccelerateor)] |
litespeed_wiki:php_503_error [2014/04/23 17:22] Kevin Fwu [3. Enable Core Dump (or just turn off opcode caching)] |
||
|---|---|---|---|
| Line 39: | Line 39: | ||
| ==== 2. Check for Corresponding Entries in stderr.log ==== | ==== 2. Check for Corresponding Entries in stderr.log ==== | ||
| - | The stderr.log logs errors from the standard error stream. This log can give you additional information about errors that occurred. Using the time stamps and PIDs you've gotten from the error log, you may be able to find relevant errors in the stderr.log. | + | The stderr.log logs errors from the standard error stream. This log can give you additional information about errors that occurred. Using the time stamps and PIDs you've gotten from the error log, you may be able to find relevant errors in the stderr.log. The stderr.log can usually be found in the same directory as the error log. |
| Here are some sample entries we might find in stderr.log: | Here are some sample entries we might find in stderr.log: | ||
| Line 57: | Line 57: | ||
| To enable a core dump, add the environment value ''LSAPI_ALLOW_CORE_DUMP=1'' to your external application settings (WebAdmin console > Configuration > External App). Next time the application crashes, a core dump will be generated. The core file created can usually be found in the directory holding the PHP script affected. | To enable a core dump, add the environment value ''LSAPI_ALLOW_CORE_DUMP=1'' to your external application settings (WebAdmin console > Configuration > External App). Next time the application crashes, a core dump will be generated. The core file created can usually be found in the directory holding the PHP script affected. | ||
| - | **Note:** As noted below, opcode caches are frequently a cause of PHP crashes. If you find your PHP crashed, you may want to try turning off any opcode caching you have. This addressed further [[litespeed_wiki:php_503_error#opcode_caches_apc_xcache_eaccelerateor|below]]. | + | **Note:** As noted below, opcode caches are frequently a cause of PHP crashes. If you find your PHP crashed, you may want to try turning off any opcode caching you have. This is addressed further [[litespeed_wiki:php_503_error#opcode_caches_apc_xcache_eaccelerateor|below]]. |
| ==== 4. Analyze Core File with GNU Debugger ==== | ==== 4. Analyze Core File with GNU Debugger ==== | ||
| Line 155: | Line 155: | ||
| The above example shows the use of GDB to show that opcode cache was causing a crash. | The above example shows the use of GDB to show that opcode cache was causing a crash. | ||
| + | |||
| + | [[litespeed_wiki:php_503_error_example3|Opcode Cache Crashes PHP 2]] | ||
| + | |||
| + | The above example shows another error that was solved by turning off the opcode cache. | ||
| [[http://www.litespeedtech.com/support/forum/showthread.php?t=5545|ZenGuardLoader Bug]] | [[http://www.litespeedtech.com/support/forum/showthread.php?t=5545|ZenGuardLoader Bug]] | ||