After having spent some time debugging what happens, I found that the problem was in a maintenance-window created for a System which had a runtime of 99 days. I don't know if it was just the problem with the 99 days or if the maintenance window had been re-configured and that had caused an issue.

I just edited the maintenance-window setting "Start date" to "today" and during to 30 days instead. Then all the maintenance-windows were suddenly launched.

The debug was in $ZENHOME/Products/ZenEvents/Schedule.py where I added a info log so I could see which maintenance-window was next to be changed. This was done in function "runEvents" around line 140:

    138         # fire events that should be done now
    139         for next, mw in work:
    140             nextTime = time.localtime(next)
    141             nowTime = time.localtime(now)
    142             stopTime = (next + mw.duration * 60) - 1
    143             cnow = time.asctime(nowTime)
    144             cnext = time.asctime(nextTime)
    145             cstop = time.asctime(time.localtime(stopTime))
    146             self.log.info("MWList-Next: name: \"%s\" now: %s, next: %s, stop: %s" %(mw.id, cnow, cnext, cstop))

With this change and a restart of zenactiond, I was now able to see the name of the maintenance-window.

------------------------------
Thomas Luther
Senior Consultant
Netic A/S
------------------------------