With Daylight Saving Time coming up this weekend in the United States, we figured it might be worth posting this tip:
The versions of Zenoss listed in the Applies To section below suffer from a bug that causes all schedules to be shifted forward or backward anytime a DST (daylight saving time) shift occurs on your primary Zenoss server. Zenoss uses schedules on alerting rules to allow them to only be active at certain times of day, and on maintenance windows.
A permanent solution for this issue will be included in Zenoss 2.4. Until that time there are two workarounds that can be used.
Option #1: Run a script to adjust all schedules
We have developed a script that will interrogate your system and find any schedules that have been shifted due to a DST change. The major caveat with this approach is that you must run the script AFTER the DST change occurs. We recommend as soon after as possible so your schedules will remain accurate.
Please follow these instructions to download and run the
adjustSchedulesForDST.py script. Bear in mind that this script can be run at any time, and repeatedly without causing harm. However, it is only effective the first time it is run after a DST change occurs.
su - zenoss
chmod 755 adjustSchedulesForDST.py
If your primary Zenoss server doesn’t have outbound access to the Internet you will need to download the script from the referenced URL and copy it into the
$ZENHOME/bin directory on your primary Zenoss server through some other mechanism.
Option #2: Set your Zenoss server to UTC
This option will completely solve the issue with no further interaction required by you. The downside is that all times within the Zenoss web interface, and in alerts that are sent out will be shown in UTC time. This could be confusing for users who are used to working in local time only.
#3996: Daylight Savings (Time Changes) Shifts Maint Window and Alerting Schedules