Re: Log levels when logging to stdout

2020-07-16 Thread Martin Grigorov
On Thu, Jul 16, 2020 at 10:22 AM Jerome Magnin  wrote:

> Hi Martin,
>
> On Thu, Jul 16, 2020 at 10:05:40AM +0300, Martin Grigorov wrote:
> >
> > I am using such logging configuration (HAProxy built from master branch):
> >
> > global
> >   log stdout format raw local0 err
> >   ...
> > defaults
> >   log global
> >   option dontlog-normal
> >   option httplog
> >   option dontlognull
> >   ...
> >
> > But HAProxy still logs entries like the following:
> >
> > 0001:test_fe.clireq[001c:]: GET /haproxy-load HTTP/1.1
> > 0002:test_fe.clihdr[001e:]: host: 192.168.0.206:8080
> > 0006:test_fe.accept(0004)=0020 from [:::192.168.0.72:46768]
> > ALPN=
> > 0001:test_fe.clihdr[001c:]: host: 192.168.0.206:8080
> > 0002:test_fe.clihdr[001e:]: content-type: application/json
> > 0004:test_fe.accept(0004)=0024 from [:::192.168.0.72:46754]
> > ALPN=
> > 0005:test_fe.accept(0004)=001f from [:::192.168.0.72:46766]
> > ALPN=
> > 0001:test_fe.clihdr[001c:]: content-type: application/json
> > 0007:test_fe.accept(0004)=0025 from [:::192.168.0.72:46776]
> > ALPN=
> > 0003:test_fe.clireq[0022:]: GET /haproxy-load HTTP/1.1
> > 0008:test_fe.accept(0004)=001d from [:::192.168.0.72:46756]
> > ALPN=
> > 0004:test_fe.clireq[0024:]: GET /haproxy-load HTTP/1.1
> > 0003:test_fe.clihdr[0022:]: host: 192.168.0.206:8080
> > 0004:test_fe.clihdr[0024:]: host: 192.168.0.206:8080
> >
> > Those do not look like errors but in any case I tried also with 'emerg'
> log
> > level instead of 'err'
> >  and this didn't change anything.
>
> This is haproxy debug output, available when you start with haproxy -d.
>

Thanks, Jerome!
This was the problem !

Martin


>
> >
> > Do I configure it in a wrong way ?
> > I want HAProxy to log only when there is a problem. Because now it logs
> few
> > GBs of those when I load it and this affects the performance.
> > https://medium.com/@martin.grigorov/hi-willy-476dee6439d3
>
> How do you start haproxy ?
>
> --
> Jérôme
>


Re: Log levels when logging to stdout

2020-07-16 Thread Jerome Magnin
Hi Martin,

On Thu, Jul 16, 2020 at 10:05:40AM +0300, Martin Grigorov wrote:
> 
> I am using such logging configuration (HAProxy built from master branch):
> 
> global
>   log stdout format raw local0 err
>   ...
> defaults
>   log global
>   option dontlog-normal
>   option httplog
>   option dontlognull
>   ...
> 
> But HAProxy still logs entries like the following:
> 
> 0001:test_fe.clireq[001c:]: GET /haproxy-load HTTP/1.1
> 0002:test_fe.clihdr[001e:]: host: 192.168.0.206:8080
> 0006:test_fe.accept(0004)=0020 from [:::192.168.0.72:46768]
> ALPN=
> 0001:test_fe.clihdr[001c:]: host: 192.168.0.206:8080
> 0002:test_fe.clihdr[001e:]: content-type: application/json
> 0004:test_fe.accept(0004)=0024 from [:::192.168.0.72:46754]
> ALPN=
> 0005:test_fe.accept(0004)=001f from [:::192.168.0.72:46766]
> ALPN=
> 0001:test_fe.clihdr[001c:]: content-type: application/json
> 0007:test_fe.accept(0004)=0025 from [:::192.168.0.72:46776]
> ALPN=
> 0003:test_fe.clireq[0022:]: GET /haproxy-load HTTP/1.1
> 0008:test_fe.accept(0004)=001d from [:::192.168.0.72:46756]
> ALPN=
> 0004:test_fe.clireq[0024:]: GET /haproxy-load HTTP/1.1
> 0003:test_fe.clihdr[0022:]: host: 192.168.0.206:8080
> 0004:test_fe.clihdr[0024:]: host: 192.168.0.206:8080
> 
> Those do not look like errors but in any case I tried also with 'emerg' log
> level instead of 'err'
>  and this didn't change anything.

This is haproxy debug output, available when you start with haproxy -d.

> 
> Do I configure it in a wrong way ?
> I want HAProxy to log only when there is a problem. Because now it logs few
> GBs of those when I load it and this affects the performance.
> https://medium.com/@martin.grigorov/hi-willy-476dee6439d3

How do you start haproxy ?

-- 
Jérôme