Followup: Without the -p option it simply took longer before the 100% CPU load appeared. So .. -p parameter is irrelevant; the problem shows up after anything between 5 minutes and 2 hours.

/Eirik

Eirik Oeverby wrote:
Hi all,

For some time now I have struggled with ntop on some (not all) of our
FreeBSD machines. In particular, a FreeBSD 5.2.1 machine is giving me
headaches:

When running ntop (3.0) with the -p <protocol list file> parameter,
after a short while its CPU load skyrockets and stays at 100% (actually,
100% of one of the CPUs in the server). Removing the -p parameter
normalizes the situation.
Note that while the CPU load is high, ntop seems to be behaving as it
should, i.e. it collects traffic data and respons to webserver requests.
There's no obvious slowdown, though this is a dual opteron server so I
don't usually notice slowdowns anyway.

Also note that the --set-pcap-nonblocking option makes no difference; it probably has no significant effect on FreeBSD 5.x.

On another server (FreeBSD 4.10), I have no problems with the -p
parameter whatsoever.

Anyone got any clue what's up with this?

Best regards,
Eirik �verby
Unicore AS
Oslo, Norway


_______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev



_______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev

Reply via email to