I used the following stacks in my configuration file stack=ct1:NFCT,ip2str1:IP2STR,print1:PRINTFLOW,emu1:LOGEMU stack=ct1:NFCT,ip2str1:IP2STR,nacct1:NACCT [ct1] netlink_socket_buffer_size=217088 netlink_socket_buffer_maxsize=1085440 #netlink_resync_timeout=60 # seconds to wait to perform resynchronization pollinterval=30 # use poll-based logging instead of event-driven hash_enable=1 This morning, I tried out commenting stack=ct1:NFCT,ip2str1:IP2STR,print1:PRINTFLOW,emu1:LOGEMU, and launched ulogd(polling mode + NACCT) only. It successfully works. It seems I cannot use the same input plugin in polling mode for two different stacks. Thanks & Regards, On Wed, Jul 18, 2012 at 11:52 AM, Eric Leblond <eric@xxxxxxxxx> wrote: > Hello, > > Le mercredi 18 juillet 2012 à 08:21 -0700, Gomathivinayagam > Muthuvinayagam a écrit : >> Hi, >> >> I try to use ulogd with NFCT polling mode and NACCT output. Ulogd > > Can you send us information about your configuration like the stack used > for logging. > > Other questions: do conntrack -L work ? > >> crashes with this options, and stacktrace is given as below >> Could someone help me the reason for this failure? >> >> == Stacktrace ================================= >> #0 0x00007fe46c334445 in raise () from /lib/x86_64-linux-gnu/libc.so.6 >> No symbol table info available. >> #1 0x00007fe46c337bab in abort () from /lib/x86_64-linux-gnu/libc.so.6 >> No symbol table info available. >> #2 0x00007fe46c32d10e in ?? () from /lib/x86_64-linux-gnu/libc.so.6 >> No symbol table info available. >> #3 0x00007fe46c32d1b2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 >> No symbol table info available. >> #4 0x00007fe46b8d6274 in nfct_query (h=0x0, qt=<optimized out>, > > If we have a NULL handle that explain the crash. Question is how we > manage to get this. > > BR, > -- > Eric Leblond > Blog: http://home.regit.org/ - Portfolio: http://regit.500px.com/ -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
