ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol

[E R]

Hi All,

I noticed using NFLOG for ulogd 2.0.2, when ulogd starts, in
/var/log/ulogd.log I'm seeing these three messages;

Thu Oct 16 22:05:22 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind
of existing log handler for protocol 2
Thu Oct 16 22:05:22 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind
of existing log handler for protocol 10
Thu Oct 16 22:05:22 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind
of existing log handler for protocol 7

I made a bug report for this;

https://bugzilla.netfilter.org/show_bug.cgi?id=977

Does anyone know anything about this, if it's a bug or end-user error I can fix?

Thanks
Mii
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Eric Leblond]

Hello,

Post by E R
Hi All,
I noticed using NFLOG for ulogd 2.0.2, when ulogd starts, in
/var/log/ulogd.log I'm seeing these three messages;
Thu Oct 16 22:05:22 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind
of existing log handler for protocol 2
Thu Oct 16 22:05:22 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind
of existing log handler for protocol 10
Thu Oct 16 22:05:22 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind
of existing log handler for protocol 7
I made a bug report for this;
https://bugzilla.netfilter.org/show_bug.cgi?id=977
Does anyone know anything about this, if it's a bug or end-user error I can fix?

This is just a normal message. It warns you that ulogd is trying to
remove other software that could have declared log handler for the
protocols.

So this does not explain the issue described in bugzilla.

BR,