Re: Segfault on basic auth?
Ahh, yes okay I saw the thread but didn't imagine it was related. I'll be able to test the newest tomorrow, and I'll close the loop here. Thanks for all you do, Phillip On Wed, Sep 23, 2015 at 3:40 AM, Willy Tarreauwrote: > Hi Phillip, > > On Wed, Sep 23, 2015 at 12:59:05PM +0930, Phillip Decker wrote: > > Hi guys, > > > > Not to pile on, but when running with 1.6-dev4, I've noticed a segfault > > that doesn't happen if you substitute 1.5.9 back in. I can post more > here > > later in the day, but I have a meeting to run to shortly- > > (...) > > I introduced a bug with the http-reuse which causes statuses 401 and 407 > on http-server-close connections to dereference a NULL. It was fixed in > dev5. I'm pretty sure that's what you're seeing. Just update do dev5 or > better, latest snapshot, to confirm you don't see it anymore. > > thanks, > Willy > >
Re: Segfault on basic auth?
Hi Phillip, On Wed, Sep 23, 2015 at 12:59:05PM +0930, Phillip Decker wrote: > Hi guys, > > Not to pile on, but when running with 1.6-dev4, I've noticed a segfault > that doesn't happen if you substitute 1.5.9 back in. I can post more here > later in the day, but I have a meeting to run to shortly- (...) I introduced a bug with the http-reuse which causes statuses 401 and 407 on http-server-close connections to dereference a NULL. It was fixed in dev5. I'm pretty sure that's what you're seeing. Just update do dev5 or better, latest snapshot, to confirm you don't see it anymore. thanks, Willy
Segfault on basic auth?
Hi guys, Not to pile on, but when running with 1.6-dev4, I've noticed a segfault that doesn't happen if you substitute 1.5.9 back in. I can post more here later in the day, but I have a meeting to run to shortly- In short, here are the conditions: - haproxy as an SSL enpoint in front of Nagios , which is itself expecting https. - haproxy listening to browsers on the regular 443, with "ssl verify required" - haproxy connecting to Nagios with "ssl verify none" Everything starts normally, and the main nagios page opens normally with HTTPS enabled. When you click a link to hosts or any of the links for server statuses, it pops up what looks like a basic authentication on the browser, and haproxy 1.6-dev4 segfaults. Changing nothing about the setup except the symlink to haproxy to 1.5.9, everything works as it should. Current options 1.6 d4 was built with: TARGET=linux2628 USE_ZLIB=1 USE_OPENSSL=1, USE_PCRE=1. Is this happening to anyone else? If not, I'll try and put together a test case I can post up here. Thanks! Phillip