Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
litespeed_wiki:php:503-errors [2018/11/06 14:27]
Jackson Zhang [CloudLinux Limits Reached]
litespeed_wiki:php:503-errors [2019/03/20 19:24] (current)
Lisa Clarke [CPanel webdisk 503 errors] Proofreading
Line 347: Line 347:
 After (re)installation of LiteMage Cache extension in Magento Connect manager or enable other modules in Magento 2, Magento site may be placed in maintenancence mode and couldn'​t be accessed and may give 503 errors. ​ Please refer [[litespeed_wiki:​cache:​litemage:​troubleshooting:​connect-cache-session-cleaning-error|this]] for details. After (re)installation of LiteMage Cache extension in Magento Connect manager or enable other modules in Magento 2, Magento site may be placed in maintenancence mode and couldn'​t be accessed and may give 503 errors. ​ Please refer [[litespeed_wiki:​cache:​litemage:​troubleshooting:​connect-cache-session-cleaning-error|this]] for details.
  
 +==== CloudLinux Imunify360 error ====
  
 +Check ''​stderr.log''​. It shows:
 +<​code>​
 +  *** Error in '​lsphp:/​home/​ukrainia/​public_html/​index.php':​ malloc(): memory corruption (fast): 0x00007fa380d45e40 ***
 +  ======= Backtrace: =========
 +  /​lib64/​libc.so.6(+0x7f574)[0x7fa37c07f574]
 +  /​lib64/​libc.so.6(+0x82c90)[0x7fa37c082c90]
 +  /​lib64/​libc.so.6(__libc_malloc+0x4c)[0x7fa37c0857dc]
 +  /​opt/​cpanel/​ea-php54/​root/​usr/​lib64/​php/​modules/​i360.so(+0xb80b)[0x7fa375fbe80b]
 +  /​opt/​cpanel/​ea-php54/​root/​usr/​lib64/​php/​modules/​i360.so(map_increment_int_+0xa2)[0x7fa375fbeaa2]
 +</​code>​
 +
 +If you try the following:
 +
 +**/​opt/​cpanel/​ea-php54/​root/​usr/​lib64/​php/​modules>​** ''​mkdir backup''​
 +
 +**/​opt/​cpanel/​ea-php54/​root/​usr/​lib64/​php/​modules>​** ''​mv i360.so backup/''​
 +
 +**/​opt/​cpanel/​ea-php54/​root/​usr/​lib64/​php/​modules>​** ''​ls -l i360.so backup/''​
 +
 +You will get this result:
 +
 +  ls: cannot access i360.so: No such file or directory
 +  backup/:  ​
 +  total 88
 +  -rwxr-xr-x 1 root root 86568 Nov 15 12:37 i360.so
 +
 +The issue is fixed by disabling CloudLinux'​s ''​i360.so''​. This is a CloudLinux bug. Please be aware that it may have been fixed by the CloudLinux team by the time you read this wiki, but it was a cause of 503 errors at one time.
 +
 +==== Plesk 503 error ====
 +Some versions of Plesk PHP, such as php71 and php56, have a buggy APCu module that may cause a 503 error on LSWS. Generally, only one object cache or value cache should be enabled. Enabling two or more may cause conflicts between modules. ​ Disabling the APCu module should fix the problem. ​
 +
 +Navigate to **Plesk Admin > Tools and configuration > PHP configuration > 7.1.x FastCGI application**. Unselect ''​apcu''​ and press the **TO ACCEPT** button.
 +{{ :​litespeed_wiki:​php:​plesk-503-disable-apcu.png?​800 |}}
 +
 +==== CPanel WebDisk 503 Errors ====
 +You might see some errors like the following:
 +  2019-03-12 12:​14:​00.324041 [INFO] [51.68.79.11:​54920:​proxy] connection to [127.0.0.1:​2077] on request #1, confirmed, 0, associated process: 0, running: 0, error: Connection refused!
 +  2019-03-12 12:​14:​00.324165 [INFO] [51.68.79.11:​54920:​proxy] connection to [127.0.0.1:​2077] on request #1, confirmed, 0, associated process: 0, running: 0, error: Connection refused!
 +  2019-03-12 12:​14:​00.324194 [NOTICE] [51.68.79.11:​54920:​proxy] Max retries has been reached, 503!
 +  2019-03-12 12:​14:​00.324206 [INFO] [http://​127.0.0.1:​2077] request force stop: too many 503 errors
 +
 +Check ''/​etc/​apache2/​conf/​httpd.conf'':​
 +   ​ProxyPass "/​___proxy_subdomain_webdisk"​ "​http://​127.0.0.1:​2077"​ max=1 retry=0
 +
 +The errors are coming from cPanel WebDisk service. If this service generates too many 503 errors, you might consider disabling it. To disable cPanel WebDisk, you can log into WHM and disable **cPanel DAV Daemon** in the **Service Manager**.
 ===== Advanced Troubleshooting Guide ===== ===== Advanced Troubleshooting Guide =====
  
Line 446: Line 492:
  
 This backtrace shows us that the program crashed soon after accessing the opcode cache. This suggests that the issue is with the opcode cache. The user can then try upgrading the opcode cache or changing their PHP version. If neither of those work, the user should try to disable the opcode cache. This backtrace shows us that the program crashed soon after accessing the opcode cache. This suggests that the issue is with the opcode cache. The user can then try upgrading the opcode cache or changing their PHP version. If neither of those work, the user should try to disable the opcode cache.
 +
 +===== The "Auto Fix 503 Error" Feature =====
 +In LiteSpeed Web Server'​s WebAdmin Console, there is a feature to **Auto Fix 503 Error**. It specifies whether to try to fix the "503 Service Unavailable"​ error by restarting the server gracefully. A "​503"​ error is usually caused by malfunctioning external applications and a web server restart can often fix the error temporarily. If **Auto Fix 503 Error** is set to ''​Yes'',​ the server will restart automatically whenever there are more than 30 "​503"​ errors within a 30 seconds span. This feature is enabled by default, but you can disable it by navigating to **LSWS Admin -> Server -> General** and setting **Auto Fix 503 Error** to ''​No''​. ​
 +
 +{{ :​litespeed_wiki:​php:​auto-fix-503-error.png?​800 |}}
 +
 +**Auto Fix 503 Error** is not a permanent fix. You should not rely on this feature to fix recurring 503 errors. Going through the above steps to find a permanent fix is always recommended. ​
  
 ===== Real World Examples ===== ===== Real World Examples =====
  • Admin
  • Last modified: 2018/11/06 14:27
  • by Jackson Zhang