Re: Error in `haproxy': munmap_chunk(): invalid pointer:

2017-11-09 Thread Tim Düsterhus
Andrew, Am 09.11.2017 um 02:00 schrieb Andrew Smalley: > The above is a guess, can you supply the build commands and clarify > this line in the config " bind :::80 v4v6" ? Dont you want to "bind > *:80" and use IPv4 only While Willy already replied that the bug is fixed (and no matter how wrong

Re: Error in `haproxy': munmap_chunk(): invalid pointer:

2017-11-09 Thread Tim Düsterhus
Willy, Am 09.11.2017 um 05:33 schrieb Willy Tarreau: > It is harmless (despite annoying for your tests) since it dies when freeing > everything on exit. If you want to get rid of it, it's fixed in the latest > daily snapshot. > I ran across it while creating an early pull request to add support

Re: Error in `haproxy': munmap_chunk(): invalid pointer:

2017-11-08 Thread Willy Tarreau
file or directory > [WARNING] 312/004845 (31835) : Can't open server state file > '/etc/haproxy/state/global': No such file or directory > > and then killing the master process using a SIGHUP: > > > *** Error in `./haproxy': munmap_chunk(): invalid pointer: > > 0x

Re: Error in `haproxy': munmap_chunk(): invalid pointer:

2017-11-08 Thread Andrew Smalley
No such file or directory > > and then killing the master process using a SIGHUP: > >> *** Error in `./haproxy': munmap_chunk(): invalid pointer: >> 0x00515028 *** >> === Backtrace: = >> /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7fda72bbc

Error in `haproxy': munmap_chunk(): invalid pointer:

2017-11-08 Thread Tim Düsterhus
illing the master process using a SIGHUP: > *** Error in `./haproxy': munmap_chunk(): invalid pointer: 0x00515028 > *** > === Backtrace: = > /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7fda72bbc7e5] > /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1a8)[0x7fda72bc9698]