Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
litespeed_wiki:cpanel:troubleshooting [2018/07/25 13:50] Eric Leu [mod_ruid2 Incompatibility] |
litespeed_wiki:cpanel:troubleshooting [2021/01/12 16:45] (current) Lisa Clarke Removed old irrelevant content, added Imunify360 downtime issue |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| </file> | </file> | ||
| - | To fix this, try increasing the "Max cPanel process memory (Minimum: 512)" in WHM > Server Configuration > Tweak Settings. | + | To fix this, try increasing the **Max cPanel process memory (Minimum: 512)** in **WHM > Server Configuration > Tweak Settings**. |
| ===== LiteSpeed Does Not Restart When Configuration Changes ===== | ===== LiteSpeed Does Not Restart When Configuration Changes ===== | ||
| - | In order for configuration changes to take effect, LiteSpeed Web Server should restart automatically. Do **NOT** uncheck the "httpd" service under WHM > Service Configuration > Service Manager. If unchecked, WHM will not restart LiteSpeed automatically when configurations have been changed. | + | In order for configuration changes to take effect, LiteSpeed Web Server should restart automatically. Do **NOT** uncheck the ''httpd'' service under **WHM > Service Configuration > Service Manager**. If unchecked, WHM will not restart LiteSpeed automatically when configurations have been changed. |
| ===== Incorrect gcc Permissions ===== | ===== Incorrect gcc Permissions ===== | ||
| - | cPanel may set permissions for /usr/bin/gcc to 0700. This will break our PHP build script. To fix this, change the permissions for the directory: | + | cPanel may set permissions for ''/usr/bin/gcc'' to ''0700''. This will break our PHP build script. To fix this, change the permissions for the directory: |
| chmod 0755 /usr/bin/gcc | chmod 0755 /usr/bin/gcc | ||
| Line 45: | Line 45: | ||
| chmod 0700 /usr/bin/gcc | chmod 0700 /usr/bin/gcc | ||
| - | ===== mod_ruid2 Incompatibility ===== | + | ===== mod_lsapi Incompatibility ===== |
| + | LSWS is not compatible with mod_lsapi so we recommend disabling it //before// installing LiteSpeed. All the functionality that mod_lsapi offers is already built directly inside of LSWS, so mod_lsapi is unnecessary, and in fact may cause issues and performance decreases. | ||
| - | LSWS is not compatible with mod_ruid2 because LSWS does not allow the process user to change mid-process. Make sure that mod_ruid2 is disabled in your WHM settings when using LSWS. LSWS is compatible with Apache prefork or event MPM. | + | ===== Unexplained site downtime ===== |
| - | + | If you have sites experiencing unexplained downtime, and you are using a proxy shield (such as CloudLinux Imunify360) we recommend disabling the shield. If the downtime ceases, then this is likely not a LiteSpeed or cPanel issue. Please contact the proxy shield software's support team. | |
| - | If mod_ruid2 is enabled, a variety of functionality may be disrupted due to WHM creating files that the web server user cannot access. | + | |
| - | + | ||
| - | However, starting in October 2014, there's been a new version of the WHM Plugin that automatically checks to see if mod_ruid2 is enabled. The Plugin now automatically removes the cPanel "fileprotect" file if it finds mod_ruid2 enabled. This should change the permissions to make them compatible with LSWS. | + | |
| - | + | ||
| - | ===== mod_lsapi Incompatibility ===== | + | |
| - | Using mod_laspi with LSWS may cause performance issues. | + | |