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-errors [2018/09/14 16:05] Michael Alegre [The lsphp process is killed unexpectedly by CSF/LFD] |
litespeed_wiki:php:503-errors [2018/10/01 20:17] Jackson Zhang [Misconfiguration of lsphp external application] |
||
|---|---|---|---|
| Line 290: | Line 290: | ||
| These settings will need to be adjusted on a per case basis as each scenario will be different. They should be increased slightly higher than the current values until the issue stops occurring. For the changes to take effect, both csf and lfd will need to be restarted. This can either be done via the WHM Plugin or through a shell terminal with the following command: ''csf -r; service lfd restart'' | These settings will need to be adjusted on a per case basis as each scenario will be different. They should be increased slightly higher than the current values until the issue stops occurring. For the changes to take effect, both csf and lfd will need to be restarted. This can either be done via the WHM Plugin or through a shell terminal with the following command: ''csf -r; service lfd restart'' | ||
| + | ==== Misconfiguration of lsphp external application ==== | ||
| + | During the LSWS installation, external application will be automatically set to the best value of the general situation. However, sometimes the user intentionally removes something which causes misconfiguration and may cause 503 error. | ||
| + | |||
| + | For PHP external app, LSWS will normally add the following to it as default. | ||
| + | <memSoftLimit>2047M</memSoftLimit> | ||
| + | <memHardLimit>2047M</memHardLimit> | ||
| + | <procSoftLimit>1400</procSoftLimit> | ||
| + | <procHardLimit>1500</procHardLimit> | ||
| + | |||
| + | but some user intentionally removed the above without any clear purpose. When the resource limit was not set, LSWS will use CGI resource limit as default while the CGI resource limit is too low to meet the requirement. | ||
| + | |||
| + | If the user configured PHP to have 500 max connections. | ||
| + | <maxConns>500</maxConns> | ||
| + | It requires to have 500 children processes: | ||
| + | <env>PHP_LSAPI_CHILDREN=500</env> | ||
| + | |||
| + | "500 max connections" setting requires "process limit" to be set at a minimum of "1000", while the user incorrectly removed PHP process limit settings. The above misconfiguration caused 503 PHP error when running LSWS. | ||
| + | |||
| + | We recommend not to remove anything if you are unsure and cause an uncertain problem, such as 503 error as this case. | ||
| ==== Apache and LiteSpeed using unmatched PHPs could cause problems for control panel users ==== | ==== Apache and LiteSpeed using unmatched PHPs could cause problems for control panel users ==== | ||
| If you use a control panel such as cPanel or Plesk, make sure both PHPs for Apache and LiteSpeed are matching each other. To test this, you can create a phpinfo page under your domain and switch between both web servers to check. If these PHPs do not match you could end up with 503 errors. | If you use a control panel such as cPanel or Plesk, make sure both PHPs for Apache and LiteSpeed are matching each other. To test this, you can create a phpinfo page under your domain and switch between both web servers to check. If these PHPs do not match you could end up with 503 errors. | ||