On 08/11/13 21:11, Chris Boot wrote: > On 08/11/13 20:08, Paul Kench wrote: >> Think this is it. > > It is indeed, thanks very much. It looks like something coming from > libnetfilter-log; I'll have to investigate further to see exactly what's > going on.
Paul, Do you have any other instances of ulogd running at all? Or any other utilities that might make use of NFLOG? Basically, the error you are seeing appears to stem from a bug in one of ulogd's error paths. This same path can be called either if libnetfilter-log cannot bind to a particular group number, or if the socket is unable to be made non-blocking via an fcntl() call. Something fails within input/packet/ulogd_inppkt_NFLOG.c in the start() function, which jumps to the out_bind goto label. This then proceeds to close the nflog handle on line 621 and *then* attempt to unbind from a few protocol families on lines 623-5. The unbind causes the crash because the handle was freed just before. To be clear: something on your system is causing this error path to be followed, and a bug in ulogd2 is then causing the crash. I'll fix the bug in ulogd, but that by itself won't make ulogd work on your system. Regards, Chris -- Chris Boot [email protected] GPG: 1DE8 6AB0 1897 A330 D973 D77C 50DD 5A29 FB09 9999 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
