Setting the interval too low is probably silly. I should probably limit the
minimum interval to 30 or 60s.
There's a minimum 1 second interval on rrds, so there's a slight risk of
losing an update because it's viewed as the same 'second'.
The size of 1s databases are huge. 72hours of 1s data is 259,200 items, vs
the normal 72h of 5m data which is 864 items.
With a busy system, it may take longer than 1s to finish running through the
hosts, so you'll lose ticks or possibly deadlock ntop (which is what I
suspect is happening).
The log is useless. If you're interested in perusing this, run ntop under
gdb, capture the failure and file a problem report.
-----Burton
US-based commercial support for ntop:
http://www.ntopsupport.com
mailto:[EMAIL PROTECTED]
Search the ntop mailing lists at gmane:
http://search.gmane.org
HowTo Ask for Help at
http://snapshot.ntop.org/faq.php#83
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Giacomo Sergio
Sent: Thursday, July 24, 2003 9:14 AM
To: [EMAIL PROTECTED]
Subject: [Ntop] ntop problem with rrdtool dump interval
Hi,
I'm using ntop (version 2.2) with rrdtool (version 1.0.45) and I have
the following problem: when I set the dump interval at 1 second from the
rrdplugin web interface, after few minutes I get a segmentation fault
(see log attatched). Using older version of ntop (version 2.1.55), I
had not this problem.
Do you have any suggestion?
Thank you,
Giacomo
_______________________________________________
Ntop mailing list
[EMAIL PROTECTED]
http://listgateway.unipi.it/mailman/listinfo/ntop
