<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 9/26/2016 2:59 AM, Ron Cohen wrote:<br>
</div>
<blockquote
cite="mid:CAK=Ff3VOy4v9O6FOYoZ9fth1_gVwaSC=tnMbqboQai7Jvya3eA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif;font-size:small">Hi<br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif;font-size:small">Someone
with uncontrolled fingers changed the date on one of our HPs
to 2036. since than, all xymon builtin alerts gone purple
(all new stats are from the past :( )<br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif;font-size:small">is
there a way of removing those 2036 entries without deleting
all history?<br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif;font-size:small">thanks<br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif;font-size:small">_rony<br>
<br>
</div>
</div>
</blockquote>
<br>
Hi Ron,<br>
<br>
If you're referring to the history files, it's possible but will
require some manual effort.<br>
<br>
These are actually simple text files in your $XYMONVAR directory and
the offending line can be removed with your favorite text editing
tool. The only sticking point is that these do not have a final
newline at the end, and this is used when backscanning for time
calculations as a marker, so it's important to make sure that this
format is generated properly. You can do a live reload of the
history page (which reads that file in on each CGI hit) to confirm
that no syntax errors are present in a modified version. Usually
this manifests by garbled date calculations or missing event ranges.<br>
<br>
If you're referring to the "current status display" and not a
history log, in theory that should get replaced by the next incoming
message just fine. xymond doesn't really care about the host's
localtime or epochtime; xymond_client only uses it for the "clock
skew" RRD.<br>
<br>
If there are RRD display issues, that will be quite a bit trickier.
IIRC, the process involves exporting data sets and reimporting them
using rrdtool similar to when you need to "de-spike" an erroneous
data value, but I've never actually done it myself.<br>
<br>
<br>
HTH,<br>
-jc<br>
</body>
</html>