[solved] Max retries has been reached, 503!

[track1]

after more tests, and reproducing own 503 errors with a large cookie,
found that reducing cookie size had no error.

[webizen]

Good to hear.

The error below (from your debug log) indicates php crashed. lsapi tried to recover connection and failed (Max retries has been reached). Usually, should let PHP dump core file and find out what the root cause is.

2011-02-03 18:31:07.114 [INFO] [123.123.123.123:52532-0#APVH_site.com:lsapi] connection to [/tmp/lshttpd/lsphp5.sock.993] on req
uest #94, confirmed, 1, associated process: 27581, running: 1, error: Connection reset by peer!
2011-02-03 18:31:07.114 [DEBUG] [123.123.123.123:52532-0#APVH_site.com:lsapi] [ExtConn] close()
2011-02-03 18:31:07.114 [DEBUG] [123.123.123.123:52532-0#APVH_site.com:lsapi] HttpExtConnector::tryRecover()...
2011-02-03 18:31:07.114 [NOTICE] [123.123.123.123:52532-0#APVH_site.com:lsapi] Max retries has been reached, 503!

[track1]

problems seems to be cookie size > 4kb
but why Apache/PHP don't crash?

[mistwang]

If Apache/PHP crash, user only got a blank page.different symptom.
Likely a PHP internal issue as LSAPI does not deal with cookies at all.

[track1]

yes, but apache simply does not crash (do not show a blank page with cookies over 4kb), while litespeed shows 503 error.

[mistwang]

It is a mystery now why PHP crash with large cookie size. If you could create a simple test script to trigger it, we would like to investigate it in our lab.

[xnetua]

Why the thread is marked as solved?
I have the same problem:

2011-02-10 11:58:39.584 [NOTICE] [213.111.228.103:51337-2#p16932:xxxxx.ru] Redirect: #1, URL: /index.php
2011-02-10 11:59:32.539 [NOTICE] [213.111.228.103:51398-0#p16932:xxxxx.ru] Max retries has been reached, 503!
2011-02-10 11:59:32.539 [NOTICE] [213.111.228.103:51398-0#p16932:xxxxx.ru] oops! 503 Service Unavailable
2011-02-10 11:59:32.539 [NOTICE] [213.111.228.103:51398-0#p16932:xxxxx.ru] Content len: 0, Request line: 'GET / HTTP/1.1'

2011-02-10 11:26:48.571 [NOTICE] [213.111.228.103:50456-0#p16932:xxxxx.ru] Max retries has been reached, 503!
2011-02-10 11:26:48.571 [NOTICE] [213.111.228.103:50456-0#p16932:xxxxx.ru] oops! 503 Service Unavailable
2011-02-10 11:26:48.571 [NOTICE] [213.111.228.103:50456-0#p16932:xxxxx.ru] Content len: 263, Request line: 'POST /wp-admin/admin-ajax.php HTTP/1.1'

2011-02-10 11:59:32.539 [INFO] [uds://usr/local/lsws/tmp/p16932_lsphp.sock] Connection refused, restart!
2011-02-10 11:59:32.539 [INFO] [uds://usr/local/lsws/tmp/p16932_lsphp.sock] Connection refused, restart!
2011-02-10 11:59:32.539 [INFO] [uds://usr/local/lsws/tmp/p16932_lsphp.sock] Connection refused, restart!
2011-02-10 11:59:32.539 [NOTICE] [213.111.228.103:51398-0#p16932:xxxxx.ru] Max retries has been reached, 503!
2011-02-10 11:59:32.539 [NOTICE] [213.111.228.103:51398-0#p16932:xxxxx.ru] oops! 503 Service Unavailable

[webizen]

Is 503 error consistent or sporadic? If consistent, it is more of a php problem. Turn off opcode cache if any to troubleshoot. Also check stderr.log and see if there is anything when the 503 error happened.

[NiteWave]

Why the thread is marked as solved?

need add a note here for future search:
they changed the php code to reduce the cookie size, and fixed 503 error.

503 is a general error, there are many reasons to cause 503.for example, if a php script fail to get enough memory, a 503 error may occur.

please create a new thread for better trace your issue. Will mark this thread back to "solved"