503 error after 36 seconds

Discussion in 'Install/Configuration' started by Sindre, Aug 31, 2013.

  1. Sindre

    Sindre Member

    I have a problem where certain pages will not load. They seem to load for 36 seconds, and then boom.. 503 error and this in the logs:

    2013-08-30 19:12:21.706 INFO [84.209.71.211:56635-0#APVH_domain.com] connection to [uds://tmp/lshttpd/lsphp5.sock.91919] on request #0, confirmed, 1, associated process: -1, running: 0, error: Connection reset by peer!
    2013-08-30 19:12:21.706 NOTICE [84.209.71.211:56635-0#APVH_domain.com] request already in process for 36 seconds, fail with 503
    2013-08-30 19:12:21.706 NOTICE [84.209.71.211:56635-0#APVH_domain.com] oops! 503 Service Unavailable
    2013-08-30 19:12:21.706 NOTICE [84.209.71.211:56635-0#APVH_domain.com] Content len: 0, Request line: 'GET /entertainment.html HTTP/1.1'
    2013-08-30 19:12:21.706 INFO [84.209.71.211:56635-0#APVH_domain.com] Cookie len: 292, __atuvc=2%7C35; adminhtml=4640ed24f51d3fa01264cb7bd882325e; frontend=9b12f9a22cb35e4d849db607ab846b99; __utma=27957153.1115337076.1377892608.1377901357.1377904081.4; __utmb=27957153.1.10.1377904081; __utmc=27957153; __utmz=27957153.1377892608.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)


    I am running CloudLinux with limits 1 full CPU core and 1024MB RAM, so don't think that is the problem. In LiteSpeed, soft/hard memory limits are not set for the external application.

    Any advise?
  2. NiteWave

    NiteWave Administrator

    please check

    External App -> lsphp5 -> Initial Request Timeout (secs)

    if it matches the 36 seconds.
  3. Sindre

    Sindre Member

    I already tried to increase the Initial Request Timeout.

    For what it matters, this error only happens after I enabled the "Flat Catalog Category" feature on a Magento site if you are familiar with it. The CPU of the lsphp5 process stays on 100% and then the application crashes after 30-40 seconds with 503 error. No other error in stderr.log.

    I already contacted CloudLinux and they say it is a Litespeed issue.

Share This Page