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

Discussion in 'General' started by danyclaut, Jul 5, 2009.

  1. DraCoola

    DraCoola Member

  2. DraCoola

    DraCoola Member

    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?
  3. mistwang

    mistwang LiteSpeed Staff

    Please download 4.0.7 package again, the initial build may have 503 error, should have been fixed.
  4. anewday

    anewday Moderator

    Numerous past versions have 503 errors after it is released and then fixed soon after. :confused:
  5. robfrew

    robfrew New Member

    I am starting to get these now. Just recently updated to 4.0.7. Didn't see these errors prior to 4.0.7. What's up?
  6. mistwang

    mistwang LiteSpeed Staff

    Please download 4.0.7 again and have a manual update see if you still get it.
  7. mistwang

    mistwang LiteSpeed Staff

    4.0.8 release package is available to address bugs in 4.0.7, please download and give it a try.
  8. robfrew

    robfrew New Member

    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: Jul 27, 2009
  9. robfrew

    robfrew New Member

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

    mistwang LiteSpeed Staff

    Please enable INFO level logging, no enough information to analyze it.
    It could be a real one.
  11. DraCoola

    DraCoola Member

    After couple hours of using 4.0.8... still resulting random 503 errors.
    So I went back to 4.0.6 again :)
  12. robfrew

    robfrew New Member

    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: Jul 27, 2009
  13. harrinp1

    harrinp1 New Member

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

    robfrew New Member

    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: Jul 27, 2009
  15. anewday

    anewday Moderator

    Eaccelerator is the most compatible with LSAPI.
  16. robfrew

    robfrew New Member

    Thanks, I will look into it. Right now, Xcache is causing me grief with SHM settings.
  17. harrinp1

    harrinp1 New Member

    I don't believe I have xcache configure - I'm just rebuilding php anyway.
  18. mistwang

    mistwang LiteSpeed Staff

    4.0.7 and 4.0.8 may have random 503 errors, 4.0.9 should have addressed that. please upgrade.
  19. robfrew

    robfrew New Member

    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: Jul 28, 2009
  20. mistwang

    mistwang LiteSpeed Staff

    Thanks for the update. Glad you found a working opcode cache for 5.3.

Share This Page