4.2 - 503 Errors

[colorprint]

Well, I have upgraded to lsws 4.2.2 and recompiled the php, but still have the same problem with 503 errors on php pages

[webizen]

seems more of php related issue. see if below helps.

https://store.litespeedtech.com/stor...aycat&catid=12

[colorprint]

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...

[mistwang]

you can PM me a temp root access, I can take a look.

[mistwang]

It is cause by a bug in php-litespeed-6.1 release when LSAPI_ACCEPT_NOTIFY=1 is used. fixed now.

[colorprint]

Originally Posted by mistwang

It is cause by a bug in php-litespeed-6.1 release when LSAPI_ACCEPT_NOTIFY=1 is used. fixed now.

Ok. Thanks!

[bzerangue]

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.

[mistwang]

Please PM me a temp root access, I can take a look.

[mistwang]

Originally Posted by bzerangue

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.

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.

[bzerangue]

Originally Posted by mistwang

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.

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.