Apr 28, 2010 12:01 PM
Maintenance window generates thousands of messages
-
Like (0)
We have bee struggling with a disk space problem on our zenoss box. Initially we though it had to do with a broken zeopack script. We fixed that and still we were loosing spac. Yesterday we discovered that our history table had 2M rows. We used the DeleteHistory.py script to remove data. It is reasonably certain that this has come about since our upgrade to version 2.5.2.
Our zenactions log thousands (millions?) of entries like this:
2010-04-27 06:48:00,672 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 300 to 1000
2010-04-27 06:48:00,907 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:00,917 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix05's production state from 1000 to 300
2010-04-27 06:48:00,985 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:01,082 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 1000 to 300
2010-04-27 06:48:01,289 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot ending
2010-04-27 06:48:01,297 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix05's production state from 300 to 1000
2010-04-27 06:48:01,368 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot ending
2010-04-27 06:48:01,374 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 300 to 1000
2010-04-27 06:48:01,520 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:01,528 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix05's production state from 1000 to 300
2010-04-27 06:48:01,559 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:01,568 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 1000 to 300
2010-04-27 06:48:01,858 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot ending
2010-04-27 06:48:01,895 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix05's production state from 300 to 1000
2010-04-27 06:48:01,958 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot ending
2010-04-27 06:48:01,965 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 300 to 1000
2010-04-27 06:48:02,181 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:02,263 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix05's production state from 1000 to 300
2010-04-27 06:48:02,329 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:02,345 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 1000 to 300
2010-04-27 06:48:02,554 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot ending
2010-04-27 06:48:02,563 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix05's production state from 300 to 1000
2010-04-27 06:48:02,632 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot ending
2010-04-27 06:48:02,639 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 300 to 1000
2010-04-27 06:48:02,834 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:02,842 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix05's production state from 1000 to 300
2010-04-27 06:48:02,874 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot starting
2010-04-27 06:48:02,883 INFO zen.MaintenanceWindows: MW Daily Reboot changes citrix06's production state from 1000 to 300
2010-04-27 06:48:03,223 INFO zen.MaintenanceWindows: Mainenance window Daily Reboot ending
AND for some reason these are being captured in the history table for device localhost...
Does anyone know why we get these messages every few milseconds during the maintenance windows? Any ideas about these getting to the history table - is this typical or specific to our SNMP settings on the zenoss box?
are your maitenance window schedules configured pproperly? is your server and zenoss system times configured properly?
The Maintenance Windows are working, and the date/time are correct and are being updated by a time server.
There was a problem with the Maintenance Windows - but I cannot remember the sequence of events. I am assuming that after the most recent DST shift, that we had a problem. I believe that I found a script that was supposed to correct the problem and that it ran without issue. But the Maintenance Windows still failed to be active at the correct time. I deleted all of the MW's and recreated them. I may have upgraded to 2.5.2 at that time to see if it would correct the MW issue.
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||