Surprise... but I'm seeing the same thing. However, in my case, it was 2 processes sharing 100% - sflow being one and the dns address resolution thread being the 2nd (address.c starting around 408).
Configuring a port for sflow didn't fix the 2nd - I'm still pegged at 100% cpu usage... Bad ntop, bad dog. I guess that's #7 on my list of must fix for 2.1... -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Klinkert Sent: Thursday, April 04, 2002 3:57 AM To: [EMAIL PROTECTED] Subject: [Ntop] 02-04-03: problem with 100% CPU utilization (due to sFlow) Hi all, I just noticed a problem with the snapshot of 02-04-03. When ntop is started, ntop wants a load of 1 (100% CPU utilization). The problem is related to the sFlow plugin, since the load drops to normal proportions when the sFlow plugin is configured. When the incoming flow direction is set to a port (6343), instead of port 0 on startup, the problems goes away. Note that it doesn't matter if the plugin is active or inactive on startup of ntop (I tried both, both same problem). I observed this problem on several machines on which I installed ntop (all 02-04-03 snapshot). BTW: I start ntop with these parameters: /usr/bin/ntop -a /var/log/ntop.access.log -c -d -i eth0 -u daemon -w <IP>:<PORT> -D <DOMAIN> -E -L -P /var/lib/ntop -S 1 Does anyone else have this problem? -- Mike. _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listmanager.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listmanager.unipi.it/mailman/listinfo/ntop
