Hi,

According to HAProxy logs, your errors seems application related:

     SH   The server aborted before sending its full HTTP response headers, or
          it crashed while processing the request. Since a server aborting at
          this moment is very rare, it would be wise to inspect its logs to
          control whether it crashed and why. The logged request may indicate a
          small set of faulty requests, demonstrating bugs in the application.
          Sometimes this might also be caused by an IDS killing the connection
          between haproxy and the server.



2011/7/12 Alexey Vlasov <ren...@renton.name>:
> Hi.
>
> I've got such a scheme on the shared hosting:
>                      +- apache_pool1
>                      |
> apache_fe -> haproxy -|- apache_pool2
>                      |
>                      +- apache_pool3
>             ...
>
> haproxy.conf:
> ====
> defaults
>    log         127.0.0.1 local1 notice
>    mode        http
>    retries     10
>    maxconn     2000
>    timeout     client 50000
>    timeout     connect 5000
>    timeout     server 5m
>    balance     roundrobin
>    option      forwardfor except 111.111.111.111/32
>    stats       enable
>    stats       uri /haproxy-1gb?stats
>
> listen  backend_pool1   111.111.111.111:9099
>    option  httplog
>    log     127.0.0.1 local2
>    cookie  SERVERID
>    option  httpchk
>    capture request header Host len 40
>    server  pool1 111.111.111.111:8099 weight 256 cookie pool1 check inter 800 
> fall 3 rise 2 maxconn 500
>    server  pool2 111.111.111.111:8100 weight   1 cookie pool2 check inter 800 
> fall 3 rise 2 maxconn 250
>    server  pool3 111.111.111.111:8101 backup
> ====
>
> Unfortunately, I can't understand myself the cause of these errors:
> 1. log from apache_fe:
> ===
> 217.212.230.49 - - [12/Jul/2011:22:28:02 +0400] "GET 
> /?option=com_sobi2&sobi2Task=sobi2Details&sobi2Id=80&default=80&Itemid=7 
> HTTP/1.1" 502 107 
> "http://clientvhost.com/index.php?option=com_sobi2&Itemid=7&catid=1529"; 
> "Opera/9.80 (J2ME/MIDP; Opera Mini/4.3.24214/25.669; U; ru) Presto/2.5.25 
> Version/10.54"
> ===
>
> 2. haproxy access.log:
> Jul 12 22:28:04 l19 haproxy_aux2_pools[4944]: 111.111.111.111:42001 
> [12/Jul/2011:22:28:02.281] backend_pool1 backend_pool1/pool1 0/0/0/-1/2084 
> 502 204 - - SH-- 24/6/6/6/0 0/0 {clientvhost.com:9099} "GET 
> /?option=com_sobi2&sobi2Task=sobi2Details&sobi2Id=80&default=80&Itemid=7 
> HTTP/1.1"
>
> 3. apache_pool1:
> 10 217.212.230.49 - - [12/Jul/2011:22:28:19 +0400] www.clientvhost.com "GET 
> /?option=com_sobi2&sobi2Task=sobi2Details&sobi2Id=20&default=20&Itemid=7 
> HTTP/1.1" 200 425885 
> "http://clientvhost.com/index.php?option=com_sobi2&Itemid=7&catid=1529"; 
> "Opera/9.80 (J2ME/MIDP; Opera Mini/4.3.24214/25.669; U; ru) Presto/2.5.25 
> Version/10.54"
>
> there are few of them (taking into account 10k sites on the server),
> but still. Moreover users sometimes complain on such problems.
>
> Right from the log you can see that the request has been processed
> normally (normal size of a response, 425885 bytes - apache_pool1 log)
> for 10 seconds , but haproxy somehow returned to the client 502-th error.
>
> "show errors" doesn't show anything.
>
> Does anyone know what else can be added into the options of haproxy
> logging? Or maybe somebody just knows how this can be fixed.
>
> Thank you in advance.
>
> --
> BRGDS. Alexey Vlasov.
>
>

Reply via email to