The DOWNTIME tag causes grief for a lot of people. Not sure why.
Here is my working example:
DOWNTIME=0:0000:2359,W:1830:0730,6:0830:2359
Expect it to be down over the weekends and after hours. This is
because the customer shuts the device off with a circuit breaker
"switch" when they're done for the day.
Josh Luthman
Office: XXX-XXX-XXXX
Direct: XXX-XXX-XXXX
XXXX Wayne St
Suite XXXX
Troy, OH XXXXX
“Success is not final, failure is not fatal: it is the courage to
continue that counts.”
--- Winston Churchill
On Tue, Mar 23, 2010 at 12:48 AM, Ryan Novosielski <user-ae4522577e16@xymon.invalid> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I'm using Xymon 4.2.3.
Unfortunately, the examples in the documentation don't actually cover
the most complicated case, where you define columns, have more than one
time period, and define a reason for the downtime.
Here's what I have:
"DOWNTIME=http:*:0530:0535:BANRECT Scheduled Instance
Restart,*:2030:2035:WFWSAPP Scheduled Instance Restart"
Looks good to me, according to these rules:
DOWNTIME=[columns:]day:starttime:endtime:cause[,day:starttime:endtime:cause]
Can someone tell me what I'm doing wrong? I get this error in the
"hobbitd" test on my display machine:
Invalid timespec - expected 4 digits, got: 'WFWSAPP Scheduled I'
Any help would be most appreciated. Looks like there might be a mistake
in the manual (or is there a typo there that I don't see?).
- --
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II
|$&| |__| | | |__/ | \| _| |user-ae4522577e16@xymon.invalid - 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
iEYEARECAAYFAkuoSAgACgkQmb+gadEcsb5zoQCghXsWBEPQJI4Yq/sbry0m1YIS
W3IAoMwBQkW4IoKVuArmRmirapWBsyql
=Xo07
-----END PGP SIGNATURE-----