As very early this morning it is telling me...
Latest errormessages: Bad timespec (missing colon or wrong weekdays): W Bad timespec (missing colon or wrong weekdays): 0830:2359:OffSaturday
On Fri, May 2, 2008 at 3:53 PM, Josh Luthman <josh at imaginenetworksllc.com> wrote:
Very weird..
The device in question went down/up for 12 minutes outside of the time frame specified by the DOWNTIME statement. After it went down hobbitd complained with the following error, minutes afterward the device did come back up. The error still stands.
Latest errormessages: Bad timespec (missing colon or no starttime): W Bad timespec (missing colon or wrong weekdays): 0830:2359:OffSaturday Bad timespec (missing colon or no starttime): W Bad timespec (missing colon or wrong weekdays): 0830:2359:OffSaturday
Bad timespec (missing colon or no starttime): W Bad timespec (missing colon or wrong weekdays): 0830:2359:OffSaturday Bad timespec (missing colon or no starttime): W Bad timespec (missing colon or wrong weekdays): 0830:2359:OffSaturday
Bad timespec (missing colon or no starttime): W Bad timespec (missing colon or wrong weekdays): 0830:2359:OffSaturday Bad timespec (missing colon or no starttime): W Bad timespec (missing colon or wrong weekdays): 0830:2359:OffSaturday
I'm very confused now =)
On Fri, May 2, 2008 at 10:23 AM, Josh Luthman <josh at imaginenetworksllc.com> wrote:
Strange...I am going to try out:
DOWNTIME=0:0000:2359:OffSunday,W:1930:0730:nightlyoff,6:0830:2359:OffSaturday
tonight as Henrik suggested (which to my understand is just a shorter version). The host in question is definitely down between those times and was down this morning at 2AM when I was watching it. Thing still wouldn't go blue, hmm...
Thanks for the help guys, I'll let you know what happens probably on Sunday.
On Fri, May 2, 2008 at 9:29 AM, Dugan, Darin D [EIT] < dddugan at iastate.edu> wrote:
If memory serves, when I was configuring DOWNTIME I found that if you specify the optional reason you must also specify the optional service. Could be mistaken, of course…this is what works for me:
DOWNTIME=*:6:0125:0225:"reason goes here"
Cheers.
*From:* Josh Luthman [mailto:josh at imaginenetworksllc.com] *Sent:* Friday, May 02, 2008 1:42 AM *To:* hobbit at hswn.dk *Subject:* Re: [hobbit] Disabling alert nightly
Neither of these two complained:
DOWNTIME=0:0000:2359:OffSunday,6:0830:2359:OffSaturday
DOWNTIME=0:0000:2359:OffSunday,1:1930:0730:nightlyoff,2:1930:0730:nightlyoff,3:1930:0730:nightlyoff,4:1930:0730:nightlyoff,5:1930:0730:nightlyoff,6:0830:2359:OffSaturday
However that second one didn't disable the host, should it be as it is obviously within that time frame?
Does anyone have a working example by chance?
Thanks for the suggestion, Allan!
Josh
On Fri, May 2, 2008 at 1:38 AM, Allan Spencer <allan at zandahar.net> wrote:
The only thing I can think is the * overides/conflicts with the individual day entries and it doesnt like this ?
What if you leave it with just the Saturday and Sunday Entries ?
Allan
Josh Luthman wrote:
I am having some issues with this one...
DOWNTIME=*:1930:0730:nightlyoff,6:0830:2359:OffSaturday,0:0000:2359:OffSunday
Info page says: All days:1930:0730:nightlyoff, Sat:0830:2359:OffSaturday, Sun:0000:2359:OffSunday
But hobbitd is complaining: Latest errormessages: Bad timespec (missing colon or wrong weekdays): 1930:0730:nightlyoff Is there something wrong with the *?
On Thu, May 1, 2008 at 11:11 AM, Josh Luthman < josh at imaginenetworksllc.com <mailto:josh at imaginenetworksllc.com>> wrote:
Thanks again!
DOWNTIME=*:1930:0730:nightlyoff,5:0000:2359:OffSaturday,6:0000:2359:OffSunday
6:0000:2359:OffSunday <--that is my only question before I try it
- shouldn't it be 6 for Sunday and 5 for Saturday?
Josh
On Thu, May 1, 2008 at 10:44 AM, L.M.J <linuxmasterjedi at free.fr
<mailto:linuxmasterjedi at free.fr>> wrote:
Hi again, Le Thu, 1 May 2008 09:27:19 -0400, "Josh Luthman" <josh at imaginenetworksllc.com <mailto:josh at imaginenetworksllc.com>> a écrit : > LMJ, > > Excellent! That answers half my question - but now I need to disable it all > day on the weekends; can you have two time frames in one downtime statement? > > Josh > > On Thu, May 1, 2008 at 4:49 AM, L.M.J <linuxmasterjedi at free.fr <mailto:linuxmasterjedi at free.fr>>wrote: > > > Hi Josh > > > > Le Thu, 1 May 2008 00:44:04 -0400, > > "Josh Luthman" <josh at imaginenetworksllc.com
<mailto:josh at imaginenetworksllc.com>> a écrit : > > > > > I have a device that shuts down at 7:30pm and comes back up at 7:30am. What > > > is the best way to disable this host every single night? > > > I would like it to be marked as disabled during this time, but I definitely > > > do not want the bb.html, bb2.html and bb.wml showing up red - red is bad! I > > > also need it to stop sending email alerts. > > > > > > Would DOWNTIME= be what am I looking for? If so can someone explain how the > > > day:starttime:endtime:cause[,day:starttime:endtime:cause] gets filled it? > > > > > > I need it to be every weekday in the evenings and nights as well as every weekend. > > > > I had almost the same issue : do not display databases connection errors during the night backup, here we > > go : > > > > ip.ip.ip.ip name # conn foo bar NAME:"Nice Name" DOWNTIME=*:1930:0730:MyReason > > > > That's it ;) Test this :DOWNTIME=*:1930:0730:MyReason,5:0000:2359:OffSaturday,5:0000:2359:OffSunday
What do you think about this one ? ;)-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer
-- Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer