-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

And I've found that the first part of my line even works -- it did provide for downtime from 5:30 to 5:35 and it provided the BANRECT-related reason. Maybe I need the http: for the second one also? Guess it couldn't hurt, but the manual does not mention using a column on the second one.

See, what your example also lacks is use of a column, which is something that's missing in the example, and a cause.

=R

Josh Luthman wrote:

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.

On Tue, Mar 23, 2010 at 12:48 AM, Ryan Novosielski <novosirj at umdnj.edu> wrote: 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?).

...

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

...

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

---- _ _ _ _ ___ _ _ _ |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

iEYEARECAAYFAkuomzcACgkQmb+gadEcsb74aQCfQIZBqAciO/4+p9nV/FWTlnmV drIAoKFpQdskYUxsUjtNuYVO7hXG+CzF =rXNC -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Thank you!

I would never have figured that out (without reading the source code). The documentation would lead you to believe, though it is an unlikely situation, that you can NOT use columns in more than one of the comma separated downtime events and I don't think the documentation says at all that one is dependent on the other.

I suppose that I have it working now -- I suppose we shall see.

Dugan, Darin D [EIT] wrote:

If you want to use a column or a cause you must use both. Three or five parameters is deterministic, but presently the code doesn't try to figure out which you're supplying (column or cause) if you provide only four parameters. The old documentation was wrong.

So just use * for column if you want to provide a cause, or provide some kind of cause if you want to provide a column. I think it's good practice to always provide a cause...

I submitted a patch to clarify the documentation a while back that I believe was committed, but there hasn't been a release since then.

Cheers.

-----Original Message----- From: Ryan Novosielski [mailto:novosirj at umdnj.edu] Sent: Monday, March 22, 2010 11:48 PM To: hobbit at hswn.dk Subject: [hobbit] Can't get DOWNTIME= to work

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?).

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

---- _ _ _ _ ___ _ _ _ |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

iEYEARECAAYFAkuozRsACgkQmb+gadEcsb59iwCcDkqwb23j7k1NT0GYtFPZaMH0 fNoAnR8fcBu/I90ZXdWQd2ZmO/dzzzqq =PRUI -----END PGP SIGNATURE-----