<html><head></head><body>Thanks for quick response!<br>
<br>
ps reveals that xymond_history is indeed running.<br>
<br>
There was no crash dump. History log shows:<br>
<br>
=> /var/log/xymon/history.log <==<br>
2015-03-25 13:58:29 Peer at 0.0.0.0:0 failed: Broken pipe<br>
2015-03-25 13:59:49 Peer not up, flushing message queue<br>
2015-03-25 14:04:56 Tried to down BOARDBUSY: Invalid argument<br>
2015-03-25 14:05:11 Peer not up, flushing message queue<br>
2015-03-25 14:16:55 Tried to down BOARDBUSY: Invalid argument<br>
2015-03-25 14:17:10 Peer not up, flushing message queue<br>
2015-03-25 14:33:02 Tried to down BOARDBUSY: Invalid argument<br>
2015-03-25 14:33:24 Peer not up, flushing message queue<br>
2015-03-25 14:57:19 Will not update /home/xymon/data/hist/arrow35,ix,arrowtel,net.xymond_history - color unchanged (purple)<br>
2015-03-25 18:04:47 Peer not up, flushing message queue<br>
<br>
I think everything’s in order.<br>
<br>
Cheers,<br>
<br>
-paul<br>
<br>
<br>
On Mar 26, 2015, at 3:10 PM, J.C. Cleaver <cleaver@terabithia.org> wrote:<br>
<br>
<br>
<br>
On Thu, March 26, 2015 1:05 pm, Paul Grondahl wrote:<br>
Hi,<br>
<br>
First post. Thanks for supporting this fantastic app!<br>
<br>
In order to reclaim some disk space I ran:<br>
<br>
"su xymon -c '/home/xymon/server/bin/trimhistory --drop --cutoff=`date +%s<br>
--date="1 Oct 2013"` —droplogs’"<br>
<br>
Afterwards xymond_history went purple, with the message "program crashed -<br>
fatal errorâ€<br>
<br>
I then ran "xymon localhost "drop <hostname> xymond_history†and now<br>
xymond_history has disappeared.<br>
<br>
I should add that the first time I ran trimhistory as root which messed up<br>
permissions on the allevents file. chmod xymon:xymon appears to have fixed<br>
it.<br>
<br>
How to get xymond_history working again?<br>
<br>
Also, for some long-running hosts, the hostdata directory remains at over<br>
2GB. Is there a way to prune the hostdata directory?<br>
<br>
Can I safely delete hostdata with "rm <hostfile>" for hosts that are no<br>
longer monitored?<br>
<br>
<br>
Welcome! We're glad you like it! :)<br>
<br>
<br>
In this case, it seems like xymond_history crashed for some reason while<br>
the trimhistory script was running; possibly a bug with how we handle<br>
cases where files disappear underneath us. If a backtrace or core dump<br>
file was left by the process when it happened, or anything unusual in the<br>
history.log, it would be very help for us to be able to track things down.<br>
<br>
<br>
In terms of "getting xymond_history working again", it should have been<br>
re-launched right away by xymonlaunch -- you should see it now in your<br>
'ps' listing. The current model of sending crashes like this as a dot<br>
requiring a manual drop more or less ensures a conscious action will be<br>
taken to acknowledge the issue. xymond_history in its normal operations<br>
doesn't send any status in, which is why the status you saw eventually<br>
turned purple in color.<br>
<br>
<br>
You may safely delete unneeded files out of the /hostdata/ directory<br>
without operational impact. (This is probably something that trimhistory<br>
should take care of, actually.) The only impact would be to someone<br>
actually trying to read the file from the web pages at that moment, since<br>
xymond_hostdata doesn't write out to that timestamp after initially saving<br>
it.<br>
<br>
<br>
<br>
Regards,<br>
<br>
-jc<br>
<br>
<br>
<img src="http://t.signaleuna.com/e1t/o/5/f18dQhb0S7ks8dDMPbW2n0x6l2B9gXrN7sKj6v4LR2lW5v0Dkd1qg6y0W3MhxYF3LvrVvW54s08m1k1H6H0?si=6599060455161856&pi=35ACED3E-04B7-4515-95A8-243CD580D0E5" width="1" height="1" style="display:none!important"></body></html>