-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hunted around on Google and the mailing list archives about this one, but I'm turning nothing up.
I have some downtime statements listed for a few hosts (names and IP's changed to protect probably nothing, but hey):
10.11.12.13 host1.umdnj.edu # "DOWNTIME=ldap,ldaps,sslcert:*:2200:2300:Development/Test Systems Cold Bacukup" 10.11.12.14 host2.umdnj.edu # "DOWNTIME=ldap,ldaps,sslcert:*:2200:2300:Development/Test Systems Cold Bacukup" 0.0.0.0 host3.umdnj.edu # "DOWNTIME=http,sslcert:*:2200:2300:Development/Test Systems Cold Bacukup" 0.0.0.0 host4.umdnj.edu # "DOWNTIME=http,sslcert:*:2200:2300:Development/Test Systems Cold Bacukup"
The downtime is picked up fine, and correctly, in the "info" test on the hosts. What's interesting is what happens when the time rolls around with the sslcert test (I'll pick Friday night out of the air, but there's nuance every day):
host1: blue at 2201, purple at 2241, blue at 22:44, normal at 2301. host2: purple at 2241, normal at 2244. host3: purple at 2236, normal at 2251. host4: blue at 2201, normal at 2301.
All four share the same DOWNTIME definition, aside from the tests involved, so I'm mighty confused. Is there some interplay here that I'm not aware of (either by what triggers an sslcert test, https/ldaps/etc., or by using 0.0.0.0 on some of the hosts, the actual status of the hosts during the DOWNTIME, etc.) that someone might have some hints for teasing out?
---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST - NJMS Medical Science Bldg - C630 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkuw3VoACgkQmb+gadEcsb5PswCgkt3bYR+P29PD/DmmTjL1Y9LP gv8AniAu5TYprlp0io8CitTinbu1E46F =u50m -----END PGP SIGNATURE-----