On Tue, Nov 11, 2008 at 11:57:55AM +0100, Anders Nordby wrote:
> Hi,
>
> On Tue, Nov 11, 2008 at 09:45:01AM +0100, Willy Tarreau wrote:
> >> /usr/local/sbin/haproxy -p /var/run/haproxy.pid -f /usr/local/etc/haprox
> >> y.conf -sf `cat /var/run/haproxy.pid`
> >> Haproxy core-dumps on signal 6 (SIGABRT):
> >> (..)
> > No idea right now, this is pretty unexpected. What version is this ?
> > From the line number, it looks like it is version 1.2.
>
> This is version 1.2.18.
OK.
> > If you can confirm your version, I can work on a patch which I will ask
> > you to try.
>
> Cool, I'll check it out when you have something.
Fine, let's try the attached patch.
> >> This is in FreeBSD.
> > I'm not surprised, because when doing a shutdown() on a listen socket,
> > we have 3 different behaviours: linux, bsd and solaris. Hence, having
> > one of those trigger a bug not seen on others has nothing surprising.
>
> It seems the problem does not exist after upgrading from FreeBSD 6.2 to
> 7.0. I just recently did that, and now haproxy does not core-dump when
> reloading. Hmm. It could be you still want to fix something related to
> my problem however? I assume you want it to work on several platforms,
> given your reply. :)
Of course I want it fixed. At worst, I'd prefer to disable the feature for some platforms than letting the process randomly crash.
Cheers,
Willy
This archive was generated by hypermail 2.2.0 : 2008/11/11 12:16 CET