recv fails with ENOBUFS (was: Cannot destroy queue, ...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 14/Jun/10 01:21, Pablo Neira Ayuso wrote:
Alessandro Vesely wrote:
 it has happened again (previous time was 5 May 2010).
 This time I used gdb rather than strace, but still don't know what's wrong:

 Calling recv on the nfq_fd had returned -512. (why?)
 At that point my daemon calls nfq_destroy_queue(), which does not return:

 (gdb) bt
 #0  0x00007ff3b6e50450 in recvfrom () from /lib/libc.so.6
 #1  0x00007ff3b696105c in nfnl_talk () from /usr/lib/libnfnetlink.so.0
 #2  0x00007ff3b79a429f in __build_send_cfg_msg (h=0x6073a0, command=2 '\002', queuenum=<value optimized out>, pf=0)
     at libnetfilter_queue.c:112
 #3  0x00007ff3b79a430d in nfq_destroy_queue (qh=0x607410) at libnetfilter_queue.c:258
 #4  0x00000000004021f7 in daemon_loop (h=0x6073a0, db=0x606570) at ibd-judge.c:477
 #5  0x0000000000402a75 in main (argc=<value optimized out>, argv=<value optimized out>) at ibd-judge.c:739

I think that this is fixed in:

http://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_queue.git;a=commit;h=bc56a6becbd4c4edf743ca3bee32eb0329fc5e5a

That fix is included in libnetfilter_queue-0.0.17. You seem to be using
an older version since you point to nfnl_talk() which is not used
anymore in the library.

Upgrade and let us know if that fixes your problem.

Now I have found a log entry about recv returning -1. I believe this was causing the previous issue, as on recv failures my program cleans up as if exiting, including destroying the queues, but then re-initializes everything and continues. This time it has succeeded doing so, hence upgrading has fixed that.

Apparently, recv fails once every few weeks. On March 15 I changed something and restarted the daemon. Changes consisted mainly in having multiple queues (2) an filtering each packet rather than just sync ones. On May 5 it crashed, and on June 12 again. This last log entry is of June 28, so it would seem that the time roughly halves...

The log line only says "No buffer space available". What does that mean? I presume the packet(s) had been dropped. I have a buffer of 8192 and pass 20 as NFQNL_COPY_PACKET, for both queues, so I think it's probably some other buffer. The host is usually plenty of memory, though.

Ideas?

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


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux