RE: Understanding haproxy logs

From: Lauro, John <jlauro#umflint.edu>
Date: Wed, 24 Oct 2007 09:25:52 -0400


I am new to haproxy, so I could be wrong... but I think it's because the conn timeouts don't apply to the data transfer portion, and are for initial connection and maybe headers. The other timeouts would be reset after every packet, and 284k would take 180 or so chunks of data.

> -----Original Message-----
> From: Unai Rodriguez [mailto:me#u-journal.org]
> Sent: Wednesday, October 24, 2007 6:22 AM
> To: haproxy#formilux.org
> Subject: Understanding haproxy logs
>
> Hi everyone,
>
> My HAProxy's configuration is here:
>
> http://pastebin.ca/747718
>
> Looking at the logs, I can see lines like this one for example:
>
>


--

> 1 process_name '[' pid ']:' haproxy[29733]
> 2 client_ip ':' client_port 10.190.0.38:1798
> 3 '[' date ']'
[24/Oct/2007:16:10:55]
> 4 listener_name dpsop-api
> 5 server_name 10.123.8.112
> 6 Tq '/' Tw '/' Tc '/' Tr '/' Tt 0/0/4/39/396377
> 7 HTTP_return_code 200
> 8 bytes_read 284639
> 9 captured_request_cookie -
> 10 captured_response_cookie -
> 11 termination_state --VN
> 12 srv_conn '/' listener_conn '/' process_conn 4/4/4
> 13 position in srv_queue / listener_queue 0/0
> 14 '{' captured_request_headers '}'
> 15 '{' captured_response_headers '}'
> 16 '"' HTTP_request '"' "GET
> /DPDataServices/SOP_CustomerWebService.asmx?wsdl HTTP/1.1"
>
---------------------------------------------------------------------- --
>
> I don't understand why:
>
> Given the fact that the timeout has been set to 300 seconds (client
&
> server), the http response is 200 (OK) and the termination state is
> successful BUT the Tt: (total session duration time) is 396 seconds.
>
> Any comments to bring me a little bit of light?
>
> Thank you so much!
> unai
Received on 2007/10/24 15:25

This archive was generated by hypermail 2.2.0 : 2007/11/04 19:21 CET