Hi Maurizio, Is it possible the interface used for export of NetFlow packets became unavailable at that time (link down, maintenance, hardware issue, etc.)? Such kind of happening would be the linking pin among the two, otherwise unrelated, messages.
Should the export socket become unavailable for some reason, nfprobe would not currently re-stablish it - even just as a matter of a try, which IMHO is good idea instead and would be matter of a few lines of code. If this rings a bell - do you have a way to reproduce the issue so to test we are shooting right? Cheers, Paolo On Mon, Jan 09, 2012 at 09:21:57AM +0100, Maurizio Molina wrote: > Hi, > I'm experiencing that nfprobe is stopping exporting flows after a while > (a few days) on some of my system. It does not crash, but it stops > exporting flows. > Before it started writing to syslog the message " unable to export > flows" I saw these two lines: > > <1b>Jan 8 01:40:49 santiago zebra[5580]: netlink_interface_addr can't > find interface by index 71 > <1b>Jan 8 01:40:49 santiago zebra[5580]: netlink-listen filter function > error > <1c>Jan 8 01:40:51 santiago pmacctd[21090]: WARN ( 1/nfprobe ): Unable > to export flows. > <1c>Jan 8 01:40:52 santiago pmacctd[21090]: WARN ( 1/nfprobe ): Unable > to export flows. > <1c>Jan 8 01:40:57 santiago pmacctd[21090]: WARN ( 1/nfprobe ): Unable > to export flows. > <1c>Jan 8 01:40:59 santiago pmacctd[21090]: WARN ( 1/nfprobe ): Unable > to export flows. > <1c>Jan 8 01:41:01 santiago pmacctd[21090]: WARN ( 1/nfprobe ): Unable > to export flows. > ...... > > Any idea is these errors are related? > Thanks, > Maurizio > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
