Cheshire Cat Computing

So everything was working wonderfully for a while, and tocay I noticed that my hosts have a scheduled downtime for this weekend:

This shows our configuration.

downtime-setup.png [ 9.43 KiB | Viewed 18884 times ]


This shows scheduled downtime.

downtime-listed.png [ 11.2 KiB | Viewed 18886 times ]


Why do we have downtime on these hosts on 02/27/2011?

so I saw there was a 3.2 update that I thought may address my issue. I installed the update and when the pl script runs, I get this msg:

Reading in configuration
Reading in status log to get list of services
Reading in list of already scheduled downtime
Checking for downtime due in next 10080 minutes
ERROR: Invalid host [host_name]!

Where host name is the name of the host. Interestingly enough, the message only occures for host [foo]. I have host [bar] setup without errors.

Nevermind on the 3.2 comment. I had a path issue.

Will 3.2 fix my originally reported problem?

It may well do; there were calendar problems with 3.0 and 3.1 (there was an off-by-one on identifying months with 30 days)

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

I just noticed today that I am still getting unwanted results when scheduling downtime. I want my hosts to be down every 3rd weekend of the month, and it looks like my hosts are getting weekends I don't have scheduled.
Here is my setup:

downtime-setup.png [ 8.44 KiB | Viewed 18793 times ]


This is the result I get:

downtime-listed.png [ 8.28 KiB | Viewed 18790 times ]


As you can see, downtime is scheduled for 03/27 which isn't a matching pattern in my configuration.

I am running downtime 3.2. everything was working with downtime 3.1, but I had a different date issue that 3.2 was supposed to address, so I upgraded.

Certainly looks like something is amiss.

There is problem reported a while back (and fixed) where the scheduler can occasionally get confused when it is a day-of-the-week rule, and skip 1 week or 1 day further forward than required.

Ive been a bit busy recently to fully test the recent changes, and am now off for 1 month Will look into it when I have time

Remind me if you havent heard anything in a month

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

i have the same problem.

issue :

But i can't understand it.

There is a bug fixed in 3.3 which would sometimes schedule a downtime for 1 week further into the future than it should This seems to be what's going on here (scheduling 27th where it should have set 20th)

Try installing v3.3

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11