Mar 17, 2009 8:57 PM
Mount free space is negative
-
Like (0)
zenmodeler run --force --device=xxx.yyy.gov.au
I have the same issue. I think the oids are getting reordered somehow as this seems to be triggered by deleting a volume off my netapp or windows file cluster; I have the issue on both. This just started after the upgrade to 2.4.5.
UPDATE: I just upgraded to 2.5 and no luck. Same issue.
We get this issue from time to time in Ver 2.4.1. Generally I am seeing this on our disk volumes that are greater than 500GB, but not always. When it happens, I disalbe monitoring for the file system, lock it from updates, remodel, and then unlock it and model again. I dont know why, but that usually fixes the problem for me.
If it happens again soon, I will login to the device and see if Net-SNMP has gone insane in a new and unusual way.
JesseWagner wrote:
I have the same issue. I think the oids are getting reordered somehow as this seems to be triggered by deleting a volume off my netapp or windows file cluster; I have the issue on both. This just started after the upgrade to 2.4.5.
UPDATE: I just upgraded to 2.5 and no luck. Same issue.
Are you restarting the SNMP daemon after deleting the volumes?
I've never had it happen on a Linux system. Only on a Windows 2008 cluster with STK luns and a Netapp. It never happened once before 2.4.5 in the entire time I've used zenoss which is over a year.
It's almost like the oids used for the volume size are getting mixed up after a volume delete; zenoss is losing track of which volumes are which and applying the wrong volume size to the wrong used blocks value. Infact I checked once after deleting a volume and all of the oids were off by one in the OS view vs doing a snmpwalk. Something to note is that we have not changed the OnTAP version on the netapp for quite a while.
Just to provide an update as to where I am with this I shall post what I did to resolve my issues.
I replaced the netapp snmp and windows FileSystem templates; Augmented is more accurate. For windows I used WMI to get disk space and for Netapp I used ssh. I can walk anyone who cares through creating their own versions of these but to share the plugins themselves would probably requires an OK from my company's legal dept.
This is just one more step in removing snmp totally from my monitoring. Snmp or atleast how zenoss implements it is very fragile thing. Long ago I repaced the process monitoring with templates. To this end I would suggest that zenoss abandon the fancy built in monitoring, or replace all of it with templates so it can be more easily replaced/removed/fixed by end users. It's hard to test this stuff properly unless you are actually running the monitoring yourself and who has every version of snmp lib/netapp/sun/EMC/windows/switch version/brand around anyways? So to this end I would suggest a more modular system removing any built in monitoring/calls and adding hooks for templates for things like Status,more OS page parts like services or processes, hardware/software. The impressive parts of zenoss for me has been the great interface, object oriented device tree, and the multi graph reporting. Most of the built in monitoring bits have not worked so well.
Jesse
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||