503 error started to happen after update

[hsnDnz]

Hello,

After updating Litespeed to version 5.3.8, we always get error 503. We've cleared all the cache, including opcache, but the problem doesn't improve. The only way to fix is to return to version 5.3.7.

The errors we have are:

***Redirect: #1, URL: /index.php
[APVH_***_Sulsphp72:] force stop requested, stopping ...
[19070] [95.1.81.60:17390] connection to [uds://tmp/lshttpd/lsphp72.sock.19065] on request #0, confirmed, 0, associated process: 0, running: 0, error: Resource temporarily unavailable!
[19070] [217.73.208.143:51021] No request delivery notification has been received from LSAPI process group [-1], possible run away process.
[19070] [217.73.208.143:51021] Max retries has been reached, 503!
[19070] [APVH_***_Sulsphp72:] request force stop: too many 503 errors
[19070] [95.1.124.34:22306] No request delivery notification has been received from LSAPI process group [-1], possible run away process.

What do we have to do to solve the problem?

 

[NiteWave]

how about 5.4RC4 ?

/usr/local/lsws/admin/misc/lsup.sh -f -d -v 5.4RC4

I've tested it in recent days, it's quite stable now.

also please ensure your license has no problem, the serial.no is correct.

 

[hsnDnz]

There is no problem in the license:

[OK] Leased license key 1 will expire in 11 days!
2019-05-27 10:18:16.200612 [NOTICE] Memory size is: 32331692KB.
2019-05-27 10:18:16.908725 [NOTICE] [OK] Updated license key has been created at /usr/local/lsws/conf/license.key.

I have updated to version 5.4, but it seems to continue with the same errors. There's a detail. After removing htaccess from the following code, the error has decreased, but it has not completely recovered:

<IfModule mod_headers.c>
<filesmatch "\(ico|flv|gif|swf|eot|woff|otf|ttf|svg)$">
Header set Cache-Control "max-age=2592000, public"
</filesmatch>
<filesmatch ".(jpg|jpeg|png)$">
Header set Cache-Control "max-age=1209600, public"
</filesmatch>
<filesmatch ".(eot|woff|otf|ttf|svg)$">
Header set Cache-Control "max-age=2592000, public"
</filesmatch>
# css and js should use private for proxy caching https://developers.google.com/speed/docs/best-practices/caching#LeverageProxyCaching
<filesmatch ".(css)$">
Header set Cache-Control "max-age=31536000, private"
</filesmatch>
<filesmatch ".(js)$">
Header set Cache-Control "max-age=1209600, private"
</filesmatch>
<FilesMatch ".(ico|pdf|jpg|jpeg|png|gif|html|htm|xml|txt|xsl|ttf|otf|eot|woff|font.css)$">
Header set Access-Control-Allow-Origin "*"
</FilesMatch>
</IfModule>

 

[NiteWave]

please log a ticket, looks like need our dev's investigation.

 

[hsnDnz]

I don't have Client Area membership. Is there an e-mail address where I can send server information?

 

[NiteWave]

you can send to support@, it'll create a ticket automatically

 

[hsnDnz]

I sent. Thank you NiteWave.

 

[hsnDnz]

For those interested in the process:

The 503 error I experienced after updating 5.3.8 could not be resolved. On the support ticket, the technical team established the 5.4 DBG version first, but the problem persisted. He then redirected me to the "503 error solution" page, but I did this.

What I'm noticing is that when I disable the cache-related features on the server, the number of errors is decreasing. But the problem is not solved completely.

I had to go back to LS 5.3.7 as the solution. In addition, after this update, I started to get the following error when switching between versions of LS:

HttpListener :: start (): Can't listen at address 159.253.33.200:80: Address already in use!

To solve this, I need to restart the network from the console each time.

Hopefully the problem will be solved with new updates.

Thanks everyone.