That 'is not an rrd file' is a dead give-away that rrd doesn't recognize the
format of the file.  You might TRY dumping the data first via rrdtool dump,
but I doubt it will work. AFAIK, the only thing you can do is to delete the
file.

I've really got no clue what is corrupting them - you might ask on the rrd
lists if there are any known problems with Windows (I haven't seen any
messages about that, but you never know).

The actual 'cause of death' is the gzflush error just below - that's
generated in compressAndSendData() in http.c.  The fix in the cvs seems to
have solved that in Unix, no clue what version you're running, so I don't
know if you have the fix - and something else is wrong - or not.  I could
also be related to the rrd problems we know about, or not - it's hard to
tell.

-----Burton

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Thomas Pagel
Sent: Monday, September 08, 2003 10:06 AM
To: [EMAIL PROTECTED]
Subject: [Ntop] Another Win32/RRD problem


Hi,

I had ntop running for a while and I got the other situation (see my mail
from some hours ago) that ntop still responds to the web but doesn't collect
any data anymore.

On the server I found an error (see attachment).

Maybe my RRDs got corrupted?! What's the best solution? Delete them?


Thanks,



Thomas Pagel
Senior Consultant Business Intelligence

Software4You Planungssysteme GmbH
Niederlassung Paderborn
Hauptstra�e 35
33178 Borchen (Germany)

tel.: +49 (5251) 54009-11
mob.:   +49 (172) 8423035
fax.: +49 (5251) 54009-99
home:   http://www.software4you.com <http://www.software4you.com/>

4PLAN� - The Art of Budgeting.

Disclaimer:
This email may contain confidential and proprietary material for the sole
use of the intended recipient.
Any review or distribution by others is prohibited.
If you are not the intended recipient please contact the sender and delete
all copies.



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

Reply via email to