Re: [ANNOUNCE] haproxy-2.2.0

2020-07-16 Thread Ryan O'Hara
On Fri, Jul 10, 2020 at 3:26 PM Илья Шипицин  wrote:

> instead of disabling Lua support, is it possible to build against Lua-5.3 ?
> I recall there's Lua-5.3 on Fedora-33
>

Right. I saw the same message, but it does not work. I sent a message to
the Lua maintainer for Fedora last Friday and he sent a patch that I will
pass along in a new thread. I feel bad for hijacking this 2.2.0
announcement thread! Stay tuned.

Ryan


let's work together

2020-07-16 Thread Glenn Scofield
Hi, Glenn from Jooble again. I shot you an brief email, we are sure the
collaboration with haproxy.com is going to be fruitful. Can I send you the
details?

Kind regards,

  

  
[Unsubscribe](http://pylinktrade.jooble.center/api/2/-4057956350631488597/unsubscribe)
  
  
\ Forwarded message   
  
Subject:  | Inquiry from Jooble  
Date:  | Tue, 14 Jul 2020 17:38:20 +0300  
From:  |  [](mailto:gsk@jooble.center)  
To:  | [haproxy@formilux.org](mailto:haproxy@formilux.org)  
  
  

Hi, we analysed your website and we think it's going to be useful for our
users. So we want to add a banner to our webpages.

I'm Glenn with a big Jobs website, Jooble.

Who can I talk to about this?



Storing src + backend or frontend name in stick-table

2020-07-16 Thread Christian Ruppert

Hi List,

is it possible to store both, IP (src) and the frontend and/or backend 
name in a stick table? We use the IP in some frontends, the 
frontend/backend name is only for visibility/informational purpose.
We have pretty huge configs with several hundred frontends/backends and 
we'd like to know like where a bot triggered some action and stuff like 
that.


--
Regards,
Christian Ruppert



Segfault on 2.2.0 and UUID fetch regression

2020-07-16 Thread Luke Seelenbinder
Hi List,

I just installed 2.2.0 (as packaged on haproxy.debian.net), and I'm 
experiencing almost instant segfaults on all canary machines (seems to be on 
the first handled request). I captured a core for debug purposes, but had to 
roll back as these machines serve production traffic. I can send the cores to 
someone over a more secure channel.

After installing debug symbols, I got this traceback in gdb:

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p 
/run/haproxy.pid -x /run/h'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x55b0131bce27 in si_cs_send (cs=cs@entry=0x55b015974530) at 
include/haproxy/channel.h:128
128 include/haproxy/channel.h: No such file or directory.
(gdb) bt
#0  0x55b0131bce27 in si_cs_send (cs=cs@entry=0x55b015974530) at 
include/haproxy/channel.h:128
#1  0x55b0131be7a9 in si_cs_io_cb (t=, ctx=0x55b015972ef0, 
state=) at src/stream_interface.c:789
#2  0x55b01321fd0c in run_tasks_from_lists 
(budgets=budgets@entry=0x7ffc8770b9cc) at src/task.c:448
#3  0x55b0132204e8 in process_runnable_tasks () at src/task.c:674
#4  0x55b0131d9bd7 in run_poll_loop () at src/haproxy.c:2905
#5  0x55b0131d9f79 in run_thread_poll_loop (data=) at 
src/haproxy.c:3070
#6  0x55b0130aa8a4 in main (argc=, argv=) at 
src/haproxy.c:3772

I also had to adjust a fetch of `uuid()` to `uuid(4)` for the configuration to 
validate, even though the docs still state that `uuid()` means `uuid(4)` in 2.2.

Best,
Luke

—
Luke Seelenbinder
Stadia Maps | Founder
stadiamaps.com


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



Log levels when logging to stdout

2020-07-16 Thread Martin Grigorov
Hello HAProxy community,

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.

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

Regards,
Martin