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:config:understanding_500 [2018/09/20 13:32] Jackson Zhang [PHP Code with wrong php configuration settings] |
litespeed_wiki:config:understanding_500 [2019/01/11 18:43] Jackson Zhang [CloudLinux LVE Limit Reached] |
||
|---|---|---|---|
| Line 133: | Line 133: | ||
| ===== PHP Code with wrong php configuration settings ===== | ===== PHP Code with wrong php configuration settings ===== | ||
| - | Sometimes, 500 error may be not easy to locate. If you move .htaccess to .htaccess.bak and move php.ini to php.ini, the 500 error still happens, it might be something wrong in the PHP code and it might be hard to find. | + | Sometimes, a 500 error may be not easy to locate. If you move ''.htaccess'' to ''.htaccess.bak'' and move ''php.ini'' to ''php.ini.bak'', and the 500 error still happens, it might mean there is something wrong in the PHP code. That can be hard to find. |
| - | We experienced a case with WHMCS. In configuration.php, someone placed **wrong php setting** there: | + | We experienced a case with WHMCS. Someone placed an incorrect setting in ''configuration.php'': |
| $display_errors = E_All; | $display_errors = E_All; | ||
| - | "E_All" is an incorrect value for PHP setting "$display_errors" and it is for "$error_reporting". "$display_errors" should be either "true"/"false", or "on"/"off". Changed it to the following as "true" and it fixed the 500 error. | + | |
| + | ''E_All'' is an incorrect value for the PHP ''$display_errors'' setting. Rather, it is meant for the ''$error_reporting'' setting. ''$display_errors'' should be either ''true''/''false'', or ''on''/''off''. We changed it to ''true'', and that fixed the 500 error. | ||
| $display_errors = true; | $display_errors = true; | ||
| - | |||
| - | |||
| - | |||
| ===== PHP Handler Not Set ===== | ===== PHP Handler Not Set ===== | ||
| Line 148: | Line 146: | ||
| ===== CloudLinux LVE Limit Reached ===== | ===== CloudLinux LVE Limit Reached ===== | ||
| When using CloudLinux, If the site is limited by memory or process limits, then the user may receive 500 errors because the server cannot execute the script. [[https://docs.cloudlinux.com/index.html?lve.html| Learn more.]] | When using CloudLinux, If the site is limited by memory or process limits, then the user may receive 500 errors because the server cannot execute the script. [[https://docs.cloudlinux.com/index.html?lve.html| Learn more.]] | ||
| + | |||
| + | For example, you might see some error like the following: | ||
| + | |||
| + | 2019-01-11 00:14:23.330946 [ERROR] [APVH_xsrvnecw_Sulsphp56:]: Failed to start one instance. Resource limit reached! | ||
| + | |||
| + | The above indicates an Error by Cloudlinux. Increasing the LVE for that user may fix the issue. | ||
| + | |||
| ===== PHP Upgrade ===== | ===== PHP Upgrade ===== | ||