4.2 - 503 Errors

J

JulesR

Member
#1
#1
Brand new server, running CloudLinux and a new install of LS 4.2:

2012-09-23 18:43:15.814 [INFO] [142.166.3.122:2444-0#APVH_XXXXXXXX] connection to [uds://tmp/lshttpd/lsphp5.sock] on request #0, confirmed, 0, associated process: -1, running: 0, error: No such file or directory!
2012-09-23 18:43:15.814 [INFO] [uds://tmp/lshttpd/lsphp5.sock] Connection refused, restart!
2012-09-23 18:43:15.814 [INFO] [142.166.3.122:2444-0#APVH_XXXXXXXX] connection to [uds://tmp/lshttpd/lsphp5.sock] on request #0, confirmed, 0, associated process: -1, running: 0, error: No such file or directory!
2012-09-23 18:43:15.814 [INFO] [uds://tmp/lshttpd/lsphp5.sock] Connection refused, restart!
2012-09-23 18:43:15.814 [INFO] [142.166.3.122:2444-0#APVH_XXXXXXXX] connection to [uds://tmp/lshttpd/lsphp5.sock] on request #0, confirmed, 0, associated process: -1, running: 0, error: No such file or directory!
2012-09-23 18:43:15.814 [INFO] [uds://tmp/lshttpd/lsphp5.sock] Connection refused, restart!

The only way to "fix" this is to touch /tmp/lshttpd/lsphp5.sock and then restart lsws. The error randomly comes back though, so we were forced to install 4.1.13.
 
M

mistwang

LiteSpeed Staff
#2
#2
It is a unix domain socket associated with the PHP suEXEC daemon created when LSWS starts.
You must have some kind of cron job removing /tmp/lshttpd/lsphp5.sock. it should not be touched.
Or running out of space on /tmp partition.
 
J

JulesR

Member
#3
#3
No, there is no cronjob on the server removing this file (why would there be anyway?).

It's a brand new server so there is plenty of space on the /tmp partition.
 
M

mistwang

LiteSpeed Staff
#6
#6
2012-09-23 18:43:15.814 [INFO] [142.166.3.122:2444-0#APVH_XXXXXXXX] connection to [uds://tmp/lshttpd/lsphp5.sock] on request #0, confirmed, 0, associated process: -1, running: 0, error: No such file or directory!
Click to expand...
this issue should have been fixed with our latest 4.2 update. please give it try.

/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2
 
C

colorprint

Member
#7
#7
[solved]

mistwang said:
this issue should have been fixed with our latest 4.2 update. please give it try.

/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2
Click to expand...
I have the same problem with both 4.2 and 4.2.1 litespeed when compile new php binaries... with the old php binaries it works.
How to fix this?
 
Last edited by a moderator:
C

colorprint

Member
#13
#13
I have compiled the php5.4.11 without Zend, APC or any additional modules enabled...
The only errors I see are these:

2013-01-31 19:24:53.059 [INFO] [83.239.187.182:42845-0#APVH_acc01.c1.server-1.biz] connection to [/tmp/lshttpd/lsphp54.sock.617] on request #0, confirmed, 0, associated process: 69618, running: 0, error: Operation timed out!
2013-01-31 19:24:53.059 [NOTICE] [83.239.187.182:42845-0#APVH_acc01.c1.server-1.biz] Suspicious request timeout, associated process: 69618, running: 0.
2013-01-31 19:24:59.005 [INFO] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] ExtConn timed out while processing.
2013-01-31 19:24:59.005 [INFO] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] connection to [/tmp/lshttpd/lsphp54.sock.617] on request #0, confirmed, 0, associated process: 69618, running: 0, error: Operation timed out!
2013-01-31 19:24:59.005 [NOTICE] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] Suspicious request timeout, associated process: 69618, running: 0.
2013-01-31 19:25:04.045 [INFO] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] ExtConn timed out while processing.
2013-01-31 19:25:04.045 [INFO] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] connection to [/tmp/lshttpd/lsphp54.sock.617] on request #0, confirmed, 0, associated process: 69618, running: 0, error: Operation timed out!
2013-01-31 19:25:04.045 [NOTICE] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] Suspicious request timeout, associated process: 69618, running: 0.
2013-01-31 19:25:09.060 [INFO] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] ExtConn timed out while processing.
2013-01-31 19:25:09.060 [INFO] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] connection to [/tmp/lshttpd/lsphp54.sock.617] on request #0, confirmed, 0, associated process: 69618, running: 0, error: Operation timed out!
2013-01-31 19:25:09.060 [NOTICE] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] Suspicious request timeout, associated process: 69618, running: 0.
2013-01-31 19:25:09.060 [NOTICE] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] Max retries has been reached, 503!
2013-01-31 19:25:09.067 [NOTICE] [83.239.187.182:42856-0#APVH_acc01.c1.server-1.biz] oops! 503 Service Unavailable

Also I see that when old working php running (compiled a year ago, 5.2.17) it creates new processes for requests under user who has the domain requested... but with last php builds with 503-errors issue there is only 1 php process runing all the time, with nobody user...
 
B

bzerangue

Member
#17
#17
I am still getting 503 errors when I've updated from 4.2 to 4.2.1 and when I upgraded to 4.2.2. I don't see any setting for LSAPI_ACCEPT_NOTIFY=1. Where is this LSAPI_ACCEPT_NOTIFY setting?

Also, can you think of anything else. I would like to use the latest version of 4.2.2.
 
M

mistwang

LiteSpeed Staff
#19
#19
bzerangue said:
I am still getting 503 errors when I've updated from 4.2 to 4.2.1 and when I upgraded to 4.2.2. I don't see any setting for LSAPI_ACCEPT_NOTIFY=1. Where is this LSAPI_ACCEPT_NOTIFY setting?

Also, can you think of anything else. I would like to use the latest version of 4.2.2.
Click to expand...
You cannot use "PHP suEXEC daemon" mode when you configure a vhost via vhost template. turn it off, it works as expected.

4.2 does not support "PHP suEXEC daemon" mode, so not affected.
 
B

bzerangue

Member
#20
#20
mistwang said:
You cannot use "PHP suEXEC daemon" mode when you configure a vhost via vhost template. turn it off, it works as expected.

4.2 does not support "PHP suEXEC daemon" mode, so not affected.
Click to expand...
4.2 does not support PHP suEXEC daemon mode????? Forgive me if I didn't understand, then why did y'all post the following blog post, saying just the opposite, "LSWS 4.2 introduces PHP suEXEC daemon mode"???? It makes it sound like it is supported in y'alls blog post.

Also, why can't you use PHP suEXEC daemon mode when configuring a vhost via vhost template?

Sorry, forgive me for my lack of understanding, could you explain why this is the case?

Thanks for your help.
 
You must log in or register to reply here.
Top