[uds://tmp/lshttpd/lsphp5.sock] Request in process stage, fail with 503

D

DraCoola

Well-Known Member
#22
#22
I just found that this 4.0.7 came from lsws whm plugin still resulting 503 error :(
So I have to raise Initial Request Timeout (secs) to 500.
Is it safe with 500 seconds?
 
R

robfrew

Well-Known Member
#28
#28
Installed 4.0.8 and so far, no 503 errors. It's been running on an active server for about 20 minutes now. Previously, I would see 503 errors within a minute or two.
 
Last edited:
R

robfrew

Well-Known Member
#29
#29
Ok, 503 has returned, here the log when debug is toggled on:

2009-07-26 21:10:04.833 NOTICE [xx.8.12.59:53226-1#???.net] Content len: 13, Request line: POST /fns/images_fns.php HTTP/1.1
2009-07-26 21:10:04.856 NOTICE [???.net] stop worker processes
2009-07-26 21:10:04.879 NOTICE [???.net] stop worker processes
2009-07-26 21:10:04.903 NOTICE [???.net] stop worker processes
2009-07-26 21:10:04.903 NOTICE [xx.8.12.59:53226-1#???.net:lsapi] Max retries has been reached, 503!
2009-07-26 21:10:04.903 NOTICE [xx.8.12.59:53226-1#???.net:lsapi] oops! 503 Service Unavailable
2009-07-26 21:10:04.903 NOTICE [xx.8.12.59:53226-1#???.net:lsapi] Content len: 13, Request line: POST /fns/images_fns.php HTTP/1.1
 
R

robfrew

Well-Known Member
#32
#32
Here it is with INFO turned on:

2009-07-27 08:42:27.632 INFO [xx.111.121.36:58526-0#???.com] connection to [uds://tmp/lshttpd/???.com_lsphp.sock] on request #525, confirmed: 1, Connection reset by peer!
2009-07-27 08:42:27.632 NOTICE [xx.111.121.36:58526-0#???.com] [uds://tmp/lshttpd/???.com_lsphp.sock] Request in process stage, fail with 503
2009-07-27 08:42:27.632 NOTICE [xx.111.121.36:58526-0#???.com] oops! 503 Service Unavailable
2009-07-27 08:42:27.632 NOTICE [xx.111.121.36:58526-0#???.com] Content len: 910, Request line:
POST /signup.php HTTP/1.1
 
Last edited:
H

harrinp1

Member
#33
#33
I'm seeing same issue on OS X, not sure when it started.

I've upgraded to 4.0.8 and using php 5.2.8.

2009-07-27 16:01:46.649 [INFO] [72.30.12.109:48724-0#villa] connection to [uds://tmp/lshttpd/lsphp.sock] on request #0, confirmed: 0, Connection reset by peer!
2009-07-27 16:01:46.649 [NOTICE] [72.30.12.109:48724-0#villa] Max retries has been reached, 503!
2009-07-27 16:01:46.649 [NOTICE] [72.30.12.109:48724-0#villa] oops! 503 Service Unavailable
2009-07-27 16:01:46.649 [NOTICE] [72.30.12.109:48724-0#villa] Content len: 0, Request line:
GET /page/golf HTTP/1.1
 
R

robfrew

Well-Known Member
#34
#34
After further research, it looks like XCache died. Removed XCache and no more 503 errors. Will try to investigate why XCache all of a sudden started having issues.
 
Last edited:
R

robfrew

Well-Known Member
#39
#39
Proud to report that LSWS 4.0.9 has been running for 4 hours without any issues. No 503 errors, nothing. 4 hours may not seem like a long time but I have a busy server and if something is going to go wrong, it is going to happen fast.

I have also been able to work out Xcache and it too is working great. Unfortunately, I cannot try EA as it is not ready for PHP 5.3. Xcache is 5.3 ready and honestly, I have no complaints.

LSWS is running fast and furious! Our sites are blazing fast.
 
Last edited:
You must log in or register to reply here.
Top