Hi Guys, reviewing quickly the code, seems like there is something not working properly on the nfacctd side - while on the sfacctd everything is reported to be working well. I'll fix that in the next release and actually pleas ignore it. Just to manually double check for any packet loss, when using NetFlow v5, you should expect that "but received x" value increasing by some 30 units.
Regarding the "null", don't worry, everything is ok: it should just be more polite and show you a 0.0.0.0, that's all it. Cheers, Paolo On Thu, Nov 16, 2006 at 01:06:38AM +0200, Peter Nixon wrote: > On Wed 15 Nov 2006 23:27, Peter Nixon wrote: > > Hi Guys > > > > I am currently getting the following ALOT in my logs. > > > > nfacctd[10115]: WARN: expecting flow '38601682' but received '38601711' > > collector=(null):2100 agent=x.x.x.x:0 > > > > Is it one of my ciscos playing up or a problem with nfacctd?? > > Interestingly when I "nfacctd -L y.y.y.y" on the primary ip on the interface > instead of an alias ip (and change the ciscos to send to that ip obviously) > collector no longer shows as "null": > > WARN: expecting flow '35253' but received '35282' collector=y.y.y.y:2100 > agent=x.x.x.x:0 > > It appears to be unrelated to the actual problem though as the error still > occurs.. I have also rebooted the ciscos so it doesnt appear to be that.. > > Any ideas? I am running pmacct-0.11.1-3.1 _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
