Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
litespeed_wiki:php_503_error [2014/02/05 17:13] Michael [Real World Examples] |
litespeed_wiki:php_503_error [2014/04/23 17:22] Kevin Fwu [3. Enable Core Dump (or just turn off opcode caching)] |
||
|---|---|---|---|
| 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 ==== | ||