[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [xymon] Repeat: Issues with DOWNTIME, purple status, and sslcert test
- To: xymon (at) xymon.com
- Subject: Re: [xymon] Repeat: Issues with DOWNTIME, purple status, and sslcert test
- From: Ryan Novosielski <novosirj (at) umdnj.edu>
- Date: Wed, 05 Jan 2011 11:26:44 -0500
- Organization: UMDNJ-IST/CST
- References: <4D249183.408 (at) umdnj.edu> <0C197C4E-BB7C-4836-BAB3-EF01286447F3 (at) skurfer.com>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/05/2011 10:59 AM, Rob McBroom wrote:
> On Jan 5, 2011, at 10:42 AM, Ryan Novosielski wrote:
>
>> The downtime is picked up fine, and correctly, in the "info" test on the
>> hosts
>
> I've run into issues with this in the past. The code that parses the DOWNTIME for the info page seems to be different from the code that actually implements it. Things that show up correctly in the web view won't necessarily work. I forget what's different about the syntax, but I know I've mentioned it on the list before. If you search for posts from me on DOWNTIME, hopefully it'll explain.
I've located the thread. Can any developer (Henrik?) comment on whether
this issue has been fixed in later versions, either the documentation or
the behavior or both?
http://www.xymon.com/archive/2009/04/msg00301.html
This is a detailed explanation of the issue by Dominic Frise from 2009,
but apparently there's a mention of it in that message from 2008.
- --
- ---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer
|$&| |__| | | |__/ | \| _| |novosirj (at) umdnj.edu - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0km8QACgkQmb+gadEcsb7ZOwCg1W6pXdF1iL7jNhqKWfnCyXIR
x24AoILp1tdu9Vensu259xB8ZM41F9uT
=qJCp
-----END PGP SIGNATURE-----