Re: Segfault on 2.2.0 and UUID fetch regression

2020-07-18 Thread Luke Seelenbinder
Good thoughts, Tim.

I've created two Github issue:

- https://github.com/haproxy/haproxy/issues/762 
 (segfault)
- https://github.com/haproxy/haproxy/issues/763 
 (uuid config issue)

Best,
Luke

—
Luke Seelenbinder
Stadia Maps | Founder
stadiamaps.com

> On 17 Jul 2020, at 18:21, Tim Düsterhus  wrote:
> 
> Luke,
> 
> Am 17.07.20 um 17:55 schrieb Luke Seelenbinder:
>> To follow up on this—is it easier if I create this as a GitHub issue?
>> 
> 
> It will certainly not get lost in the depths of the email archive and it
> allows to easily link commits to issues and issues to commits just by
> mentioning the number in the message.
> 
> Personally I create issues for everything, even if I fix them myself a
> few minutes later. In case my patch isn't correct at least the issue
> will still remain in the tracker.
> 
> Best regards
> Tim Düsterhus
> 



Re: Segfault on 2.2.0 and UUID fetch regression

2020-07-17 Thread Tim Düsterhus
Luke,

Am 17.07.20 um 17:55 schrieb Luke Seelenbinder:
> To follow up on this—is it easier if I create this as a GitHub issue?
> 

It will certainly not get lost in the depths of the email archive and it
allows to easily link commits to issues and issues to commits just by
mentioning the number in the message.

Personally I create issues for everything, even if I fix them myself a
few minutes later. In case my patch isn't correct at least the issue
will still remain in the tracker.

Best regards
Tim Düsterhus



Re: Segfault on 2.2.0 and UUID fetch regression

2020-07-17 Thread Luke Seelenbinder
To follow up on this—is it easier if I create this as a GitHub issue?

I'm also not sure if it's related to 
https://github.com/haproxy/haproxy/issues/758 
 or not.

Best,
Luke

—
Luke Seelenbinder
Stadia Maps | Founder
stadiamaps.com

> On 16 Jul 2020, at 20:49, Luke Seelenbinder 
>  wrote:
> 
> 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



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