[Xymon] Cleaning up history logs

[Novosielski, Ryan]

See the "trimhistory" command. And there's nothing that says Xymon can't write after 5%, just the OS may have a certain amount of reserve space that is tunable, depending on the FS type and OS. 

Bear in mind Xymon must be restarted after a trimhistory command otherwise the "X changes in the last 240 minutes" list will remain blank. Also make sure you run the command as the Xymon user, not root. 



----- Original Message -----
From: Michael Beatty [mailto:Michael.Beatty at sherwin.com]
Sent: Tuesday, December 04, 2012 12:11 PM
To: xymon at xymon.com <xymon at xymon.com>
Subject: [Xymon] Cleaning up history logs

What does Xymon check to determine if my history logs directory is full?

After several months of not paying any attention to Xymon, I dove back 
in.  I found that I was getting "Historical Status Log Not Avaialable".  
Some browsing around showed that if the log directory has less than 5% 
disk space available, the logs will not be written.  I "df -i 
/home/xymon/data/histlog" directory and it was (and still) is showing 4% 
used.  Unsure what to get rid of, I deleted everything I could find in 
the data directory that related to old hosts that do not exist.  After 
doing so, log files were now available.

Obviously, there was a disk space problem, but where was it?  This is 
just a demo system so I wasn't too worried about doing such a 
destructive deletion of everything, however, if this were a production 
system I'd want to be a lot more careful as to what it is that I 
delete.  Would I just delete everything in the histlog directory that is 
 >  X days old?


-- 
Michael Beatty
Sherwin-Williams
IT Analyst/Developer
michael.beatty at sherwin.com
216-515-7374

_______________________________________________
Xymon mailing list
Xymon at xymon.com
http://lists.xymon.com/mailman/listinfo/xymon