The FreeBSD issue is well known - because FreeBSD has userland threads,
libpcap is converted to polling. This means that all *available* cpu
time goes to the poll. It's not 'wasted', it's just cycles that on
another OS would be idle.
Cheap nics definitly give worse results under load.
the sched_yield() calls might be important for responsiveness when ntop
isn't the only app on the box (that's never really been proven).
-----Burton
Rivalino Matias Jr. wrote:
Hello,
In the last years I have worked with ntop and I’m looking its stability gain
day after day. In the majority of my ntop installations I have used Linux OS.
In one experience using FreeBSD ntop showed a major CPU consumption than when
running in a Linux box, but it not meant more or less instability.
Also, I have verified that in many situations when I experienced ntop instability it was caused due to hardware problems such as NIC or ram memory. For those cases where the motherboard has onboard NICs, I learnt to disable it to use dedicated cards. In addition, I have verified that the “--disable-schedyield” has been much useful to improve the stability of my ntop installations.
Recently, I had a very good surprise with ntop stability, running ntop in a HP
laptop with less than 256 megabytes of RAM under fedora core 4 with RRD plugin
enabled and monitoring a link with 24x7 traffic activity. One important point
is that this traffic is basically constant (w/o oscillation or variability)
during all time. Yesterday this installation has completed one week and due to
the small quantity of available memory and the constant traffic activity, I’m
really happy with the behavior of ntop in this case.
Normally we send messages to report problems with ntop and now I would like to
say congratulations for the ntop development team, and also for the ntop users,
that have done a brilliant job.
Rivalino
-----Mensagem original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] nome de Mike
Lambert
Enviada em: sexta-feira, 1 de dezembro de 2006 20:08
Para: [email protected]
Assunto: [Ntop] best OS for ntop? (freebsd problems)
I am having several problems running ntop 3.2.3 (2 Nov) on generic, unmodified FreeBSD
6.2-PRERELEASE. Attempts to build from current cvs fails with several gcc "linker
input file unused because linking not done" errors. Is there a best OS to build and
run ntop on? Any/all suggestions appreciated.
Problem details:
Problem #1
Ntop will run for several days, then crash (sig 11). Ntop then only runs for a few
minutes before crashing. Deleting /var/run/dnsCache.db will allow ntop to run
"normally".
Problem #2
Ntop will consume 100% CPU and not answer web requests. Restarting shows
strange traffic graphs indicating one or more traffic rrDBs became corupt.
Deleteing /var/ntop/rrd/interfaces/xl0/* returns normal behavior.
Problem #3 (may be same as #2)
Ntop consumes 100% CPU. The following error was printed to the shell that
started ntop...
"Assertion failed: (lu->lu_myreq->lr_watcher == ((void *)0)), function
_lock_acquire, file /usr/src/lib/libpthread/sys/lock.c, line 170."
Problem #4
Ntop hostsInfo, sortDataProtos, sortDataIP attribute wrong hosts to bandwidth
usage. No errors on console or logs. CPU usage normal. Re-starting ntop solves
problem.
Regards,
Mike Lambert
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
