HTTP status 503 while HEAD request

Discussion in 'General' started by KAhlers, Jul 14, 2008.

  1. KAhlers

    KAhlers Member


    I've got a problem regarding HEAD-requests on the LSWS. I'm using version 3.3.15 and rails 2.

    2008-07-14 16:01:54.044 [INFO] [*.*.*.*:56997-0#Default:lsapi] connection to [uds://tmp/lshttpd/Default:_.sock] on request #13, error: Connection reset by peer!
    2008-07-14 16:01:54.044 [NOTICE] [*.*.*.*:56997-0#Default:lsapi] oops! 503 Service Unavailable
    2008-07-14 16:01:54.044 [NOTICE] [*.*.*.*:56997-0#Default:lsapi] Content len: 0, Request line:
    HEAD /uptime HTTP/1.1
    2008-07-14 16:01:54.044 [NOTICE] [*.*.*.*:56997-0#Default:lsapi] Redirect: #1, URL: /dispatch.lsapi
    In the log entry I had to mask the IP of the access for security reasons but I think they are not necessary.

    Every time the request is made by curl there is no problem and it is responded with a status of 200.

    lwp-request or the will get every time an error 503.

    The logexcerpt above is made from an lwp-request.

    Does anyone know this problem or a solution?

    Kind regards,
    K. Ahlers
  2. mistwang

    mistwang LiteSpeed Staff

    Please enable the debug logging in LSWS, also check Rails log.
    Looks like Rails app crashed while handling the HEAD request.
    You can also try curl with a HEAD request.
  3. KAhlers

    KAhlers Member


    the log above is from the HIGH-debug level.

    In the rails log I can't find anything which looks like a crashed rails app.

    With curl the request (HEAD) returns a status 200, with others 503.

    Best Regards,
    K. Ahlers
  4. mistwang

    mistwang LiteSpeed Staff

    Have you tried mongrel or other RoR server?
    It might be Rails internal bug.
    What you can do is to strace the ruby process to find out why lwp crash it.
  5. KAhlers

    KAhlers Member

    Together with a technican I've investigated the problem again and it seems like it was a problem in the rails app.

    Thank you for your help.

Share This Page