Try installing v3.3
Statistics: Posted by stevesh — Thu May 05, 2011 6:09 pm
]]>
issue :
But i can't understand it.
Statistics: Posted by flughamster — Fri Apr 01, 2011 2:39 am
]]>
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 timeRemind me if you havent heard anything in a month
Statistics: Posted by stevesh — Mon Mar 28, 2011 2:43 pm
]]>
downtime-setup.png
This is the result I get:
downtime-listed.png
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.
Statistics: Posted by Iokepa — Sat Mar 26, 2011 1:56 am
]]>
]]>
Will 3.2 fix my originally reported problem?
Statistics: Posted by Iokepa — Sat Feb 26, 2011 7:59 am
]]>
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.
Statistics: Posted by Iokepa — Sat Feb 26, 2011 7:47 am
]]>
This shows our configuration.
downtime-setup.png
This shows scheduled downtime.
downtime-listed.png
Why do we have downtime on these hosts on 02/27/2011?
Statistics: Posted by Iokepa — Sat Feb 26, 2011 4:15 am
]]>