0graham0
2011-11-17 15:35:54 UTC
0graham0 [http://community.zenoss.org/people/0graham0] created the discussion
"Device Class Organizer Shows Critical Status - Devices are clear"
To view the discussion, visit: http://community.zenoss.org/message/62675#62675
--------------------------------------------------------------
Hello all,
There are 3 servers in our esxtop category which are all clear. The esxtop organizer (and it's parents) are all showing a critical status. We are running Zenoss 3.2.0 on a centos 5 machine.
I have:
- Made sure there are no hidden devices in the category (all filters are clear and all 5 production states are checked).
- Made sure critical events are shown in event console, none exist.
- Deleted and recreated/remodeled all 3 servers. Even when every server was deleted the organizer showed a critical status.
- Ran ./ZenDeleteHistory.py to clear the event history
- Cleared all heartbearts and cleared event cache from the Event Manager page.
Any other ideas? Let me know if there are any relevant logs that I can post to provide further details. Thanks.
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62675#62675]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Device Class Organizer Shows Critical Status - Devices are clear"
To view the discussion, visit: http://community.zenoss.org/message/62675#62675
--------------------------------------------------------------
Hello all,
There are 3 servers in our esxtop category which are all clear. The esxtop organizer (and it's parents) are all showing a critical status. We are running Zenoss 3.2.0 on a centos 5 machine.
I have:
- Made sure there are no hidden devices in the category (all filters are clear and all 5 production states are checked).
- Made sure critical events are shown in event console, none exist.
- Deleted and recreated/remodeled all 3 servers. Even when every server was deleted the organizer showed a critical status.
- Ran ./ZenDeleteHistory.py to clear the event history
- Cleared all heartbearts and cleared event cache from the Event Manager page.
   print "Removing IP addresses linked to invalid devices."
   fixCount = 0
               unused = i.getDeviceLink()
               self.exitGracefully()
               print " - removing %s" % i.id
               n.ipaddresses._delObject(i.id)
               fixCount += 1
   commit()
   if fixCount > 0: print
- Opened zenoss in a browser on another machine to make sure this wasn't a cache issue.   fixCount = 0
               unused = i.getDeviceLink()
               self.exitGracefully()
               print " - removing %s" % i.id
               n.ipaddresses._delObject(i.id)
               fixCount += 1
   commit()
   if fixCount > 0: print
Any other ideas? Let me know if there are any relevant logs that I can post to provide further details. Thanks.
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62675#62675]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]