Hi Timur, On Thu, May 02, 2013 at 05:06:27PM +0500, Timur Irmatov wrote:
> No, links are stable. There is no link down/up events in kernel log. > Both processes just hang. I tried attaching to them via strace, one of > them was stuck in futex call, another one shows up as in > restart_syscall. OK, so instead of a strace you can try attaching the processes (most important is the one labelled 'Core process') with gdb and then do a backtrace. It should ideally return the line of the code where pmacct is sitting at. I'm afraid, from what you say above, that this will not be much of help as it will just say it's sitting waiting for next pkt to come. But let's get confirmed this is the case - return output(s) privately since is quite a bit of data and not of general interest. The config you posted looks allright. At some stage i will propose to upgrade to a later version and self-compiled to properly support you. > pmacctd[30646]: INFO ( default/core ): short IPv4 packet read > (37/38/frags). Snaplen issue ? > > I suppose this is not a problem, just a fragment of IPv4 packet is > received and pmacct is not able to see at higher level protocol fields > except IP. When pmacct hangs, logging stops, so there's no clue what's > wrong. Correct, no harm there. The fact logging stops can be because nothing happens, ie. no packet input. Cheers, Paolo _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
