<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We just had a UPS replaced and had to take down our primary Xymon server for more than 8 hours. It was a good chance to test disaster recovery. Our secondary server did really well, although I did find one problem. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We use Ralph Mitchell’s bluesync.sh shell script to keep our two Xymon servers in sync for disable/enabled hosts. It appeared that not all tests were properly disabled on the secondary server. The reason appears to be because the disable time goes past UNIX end time, of January 19th, 2038 03:14:07 GMT. The result is, if you query Xymon for the disable time and disable message, nothing is returned, time defaults to 0, null message. Would it be possible to update the code to not exceed UNIX end of time? What typically happens is someone wants to disable something for a while, and yes I know this is a bad habit, and enters 9999 or 99999 days or something similar. Perhaps it would be best, if disable time is past UNIX end of time, make UNIX end time the disable time?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I should probably add that a side effect is the host/services do not display a disable reason nor do they display on the enable/disable page disabled. Although you will see their status blue on whatever page you have them displayed.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>~David<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>