Hi.
Please keep the ML in the loop, thanks.
Thu Aug 29 22:42:18 GMT+02:00 2019 Karthik P :
> Thanks for your response. Here are the details
> Log:
> ST=-1 http_request="POST /api/v2 HTTP/1.1" sslc=ECDHE-RSA-AES256-GCM-SHA384
> sslv=TLSv1.2 Th=107 ci=10.X.X.X B=6830 si=10.Y.Y.Y b=ch s=service_onprem rc=0
> U=1603 Tr=-1 Tc=-1 Tt=192 ts=--
Okay so you have your own log format
Is ts "termination_state"?
I miss the be/se part, can you try to use the default format for the debug
session, as you can see there are some more Info's the in your format
Quote from doc.
```
>>> haproxy[18113]: 127.0.0.1:34548 [15/Oct/2003:15:18:55.798] px-http \
px-http/ -1/-1/-1/-1/8490 -1 0 - - CR-- 2/2/2/0/0 0/0 ""
=> the client never completed its request and aborted itself ("C---") after
8.5s, while the proxy was waiting for the request headers ("-R--").
Nothing was sent to any server.
```
> haproxy -vv:
Looks like you have built your own haproxy , right?
> HA-Proxy version 1.9.5 2019/03/19 - https://haproxy.org/
> [https://haproxy.org/]
> Build options :
> TARGET = linux2628
> CPU = generic
> CC = gcc
> CFLAGS = -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv
> -Wno-unused-label -Wno-sign-compare -Wno-unused-parameter
> -Wno-old-style-declaration -Wno-ignored-qualifiers -Wno-clobbered
> -Wno-missing-field-initializers -Wtype-limits
> OPTIONS = USE_OPENSSL=1 USE_LUA=1
> Default settings :
> maxconn = 2000, bufsize = 16384, maxrewrite = 1024, maxpollevents = 200
> Built with OpenSSL version : OpenSSL 1.0.1e-fips 11 Feb 2013
> Running on OpenSSL version : OpenSSL 1.0.1e-fips 11 Feb 2013
> OpenSSL library supports TLS extensions : yes
> OpenSSL library supports SNI : yes
> OpenSSL library supports : SSLv3 TLSv1.0 TLSv1.1 TLSv1.2
> Built with Lua version : Lua 5.3.3
> Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT
> IP_FREEBIND
> Built without compression support (neither USE_ZLIB nor USE_SLZ are set).
> Compression algorithms supported : identity("identity")
> Built without PCRE or PCRE2 support (using libc's regex instead)
> Encrypted password support via crypt(3): yes
> Built with multi-threading support.
> Available polling systems :
> epoll : pref=300, test result OK
> poll : pref=200, test result OK
> select : pref=150, test result OK
> Total: 3 (3 usable), will use epoll.
> Available multiplexer protocols :
> (protocols marked as cannot be specified using 'proto' keyword)
> h2 : mode=HTX side=FE|BE
> h2 : mode=HTTP side=FE
> : mode=HTX side=FE|BE
> : mode=TCP|HTTP side=FE|BE
> Available filters :
> [SPOE] spoe
> [COMP] compression
> [CACHE] cache
> [TRACE] trace
>
>
> Let me know if the above helps.
Not too much.
> Let me know if you need any other information.
The anonymized config would help a lot.
> I can try 2.x. But would like to know if there is any known issue with 1.9
I would strongly recommend to go directly to 2.0, jm2c.
> Thanks, Karthik
Regards
Aleks
> On Thu, Aug 29, 2019 at 11:52 AM Aleksandar Lazic < al-hapr...@none.at [] >
> wrote:
>
>>
>> Hi.
>>
>> Thu Aug 29 20:33:46 GMT+02:00 2019 Karthik P :
>>
>> > Hello, Can someone please help? We tried to upgrade haproxy from 1.8 to 1.9
>> > By doing this we started seeing status_code (%ST) = -1
>> > Can someone please provide some direction on how to approach debugging
>> > this issue?
>> > Did anything change in 1.9 which is causing this?
>>
>> Ähm there are a lot of changes between 1.8 and 1.9. You should share some
>> more informations about the setup and the line with ST -1.
>>
>> haproxy -vv
>> Your config
>> The whole logline with -1 entry
>>
>> Quote from doc
>>
>> ```
>> - "status_code" is the HTTP status code returned to the client. This status
>> is generally set by the server, but it might also be set by haproxy when
>> the server cannot be reached or when its response is blocked by haproxy.
>> ```
>>
>> As you see in the code could be there several reasons for the -1 and this
>> shows not the possibilities from origin server.
>>
>> http://git.haproxy.org/?p=haproxy-1.9.git=search=HEAD=grep=status_code
>>
>> [http://git.haproxy.org/?p=haproxy-1.9.git=search=HEAD=grep=status_code]
>>
>>
>> Why not using 2.0.5?
>>
>> > Thanks, Karthik
>>
>> Regards
>> Aleks
>>
>>
>
