I used to see that. Not frequently, but enough to be a problem. It was due to a corrupted rrd file causing the rrdMainLoop thread to bomb. Once that bombs, it doesn't restart and poof.
(1) Try enabling debug and - although you'll get a ton of messages - buried in there should be either some errors or you will see the last one that updates. (2) Check the mtime (modification times) of the .rrd files. The one that isn't being updated in a set is the suspect. i.e. if the last update was to /a/b/c/d/xxxx.rrd, anything else in that directory that wasn't updated on that cycle is suspect (but remember, only .rrd files which have data points are updated). $ ls -lt total 828 -rw-r--r-- 1 ntop users 35292 May 27 07:48 totContactedSentPeers.rrd -rw-r--r-- 1 ntop users 35292 May 26 11:03 bytesMulticastSent.rrd -rw-r--r-- 1 ntop users 35292 May 26 11:03 bytesSentRem.rrd -rw-r--r-- 1 ntop users 35292 May 26 11:03 bytesSent.rrd -rw-r--r-- 1 ntop users 35292 May 26 11:03 IGMPSent.rrd -rw-r--r-- 1 ntop users 35292 May 26 11:03 ipBytesSent.rrd -rw-r--r-- 1 ntop users 35292 May 26 11:03 pktMulticastSent.rrd -rw-r--r-- 1 ntop users 35292 May 26 11:03 pktSent.rrd -rw-r--r-- 1 ntop users 35292 Apr 11 07:53 IP_DNSSentBytes.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 16:53 bytesSentLoc.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 16:53 udpSentLoc.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 15:28 IP_DNSRcvdBytes.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 15:28 totContactedRcvdPeers.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 15:23 bytesRcvdLoc.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 15:23 bytesRcvd.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 15:23 ipBytesRcvd.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 15:23 pktRcvd.rrd -rw-r--r-- 1 ntop users 35292 Apr 10 15:23 udpRcvdLoc.rrd -rw-r--r-- 1 ntop users 35292 Mar 28 06:40 IP_DHCP-BOOTPSentBytes.rrd -rw-r--r-- 1 ntop users 35292 Mar 27 20:15 udpSentRem.rrd -rw-r--r-- 1 ntop users 35292 Feb 22 10:03 IP_DHCP-BOOTPRcvdBytes.rrd -rw-r--r-- 1 ntop users 35292 Feb 22 10:03 IP_HTTPSentBytes.rrd -rw-r--r-- 1 ntop users 35292 Feb 21 07:38 tcpSentLoc.rrd It's seems odd that there are currently contacted peers and multicast bytes and bytes send/received but no tcp sent locally. Unless that's normal for the host. I have not had problems w/ the CVS version. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Porter Sent: Thursday, May 26, 2005 11:40 PM To: [email protected] Subject: [Ntop] rrd not updating Using 3.1 on Fedora Core 2. My rrd files (/usr/share/ntop/rrd/interface/eth1/*) stopped updating a few months back. I can't figure out why they don't change. I see the rrd thread starting in the syslog but no errors. With tracing set to 4 I still don't see anything to suggest why they're not getting touched. The ntop user has write access to them. Any suggestions on what else to check? _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
