Discussion:
IPServices On Some Entire Devices Not Being Monitored By ZenStatus
James Pearce
2012-01-07 21:03:41 UTC
Permalink
James Pearce [http://community.zenoss.org/people/SirTechnology] created the discussion

"IPServices On Some Entire Devices Not Being Monitored By ZenStatus"

To view the discussion, visit: http://community.zenoss.org/message/63592#63592

--------------------------------------------------------------
Yes, another ipservice issue thread. ZenOSS 3.2.1.

I have an issue where some of my recent devices are having their IP Services detected as expected, but I can't get ZenStatus to monitor them. I know this is a ZenStatus issue, because when I manually run it, I am told that there are no checks to perform. I have checked my configuration against the devices on this installation that do monitor the TCP ports correctly, and there are no differences in anything that relates to the service port monitoring.

I have made sure that the services are set to monitor. I have tried setting this in only the IP Service Class, in only the local copy of the IP Service definition, and in both, with no change in behavior.

I am noticing that when I run the ZenStatus demon, I am presented with the same debug information I get when I execute against a non-existent device. Because of this, all of the debug information I am given is generic, and I don't actually know how to move forward with this.

Below is the specific debug information from ZenStatus when running with the correct device name (although it does not change if I make it incorrect). I have multiple devices doing this and I am sure the devices names I am testing with are correct (they do match the ID in the URL when looking at the device). I was not monitoring the TCP ports previously on these and so did not check to see if it was functioning.

Can anyone give me some guidance as to how to dig deeper to find out what is really stopping ZenStatus from picking up the correct configuration from these devices?
$ zenstatus run -v10 -d HES-Zimbra
2012-01-08 03:45:15,366 DEBUG zen.ZenStatus: Starting PBDaemon initialization
2012-01-08 03:45:15,409 INFO zen.ZenStatus: Connecting to localhost:8789
2012-01-08 03:45:15,410 DEBUG zen.ZenStatus: Logging in as admin
2012-01-08 03:45:15,456 INFO zen.ZenStatus: Connected to ZenHub
2012-01-08 03:45:15,456 DEBUG zen.ZenStatus: Setting up initial services: EventService, StatusConfig
2012-01-08 03:45:15,457 DEBUG zen.ZenStatus: Chaining getInitialServices with d2
2012-01-08 03:45:15,461 DEBUG zen.ZenStatus: Loaded service EventService from zenhub
2012-01-08 03:45:15,461 DEBUG zen.ZenStatus: Loaded service StatusConfig from zenhub
2012-01-08 03:45:15,461 DEBUG zen.ZenStatus: Queueing event {'severity': 0, 'component': 'zenstatus', 'agent': 'zenstatus', 'summary': 'started', 'manager': 'christine.nagashizzar.net.au', 'device': 'localhost', 'eventClass': '/App/Start', 'monitor': 'localhost'}
2012-01-08 03:45:15,462 DEBUG zen.ZenStatus: Total of 1 queued events
2012-01-08 03:45:15,463 DEBUG zen.ZenStatus: Calling connected.
2012-01-08 03:45:15,463 INFO zen.ZenStatus: Fetching property items
2012-01-08 03:45:15,491 DEBUG zen.ZenStatus: Updated statusCycleInterval config to 60
2012-01-08 03:45:15,491 DEBUG zen.ZenStatus: Updated configCycleInterval config to 360
2012-01-08 03:45:15,492 INFO zen.ZenStatus: Fetching default RRDCreateCommand
2012-01-08 03:45:15,493 INFO zen.ZenStatus: Getting threshold classes
2012-01-08 03:45:15,495 DEBUG zen.ZenStatus: Loading classes ['Products.ZenModel.MinMaxThreshold']
2012-01-08 03:45:15,495 INFO zen.ZenStatus: Getting collector thresholds
2012-01-08 03:45:15,527 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost', ''))
2012-01-08 03:45:15,527 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost', ''))
2012-01-08 03:45:15,527 DEBUG zen.thresholds: Updating threshold ('zenperfsnmp cycle time', ('localhost', ''))
2012-01-08 03:45:15,527 DEBUG zen.thresholds: Updating threshold ('zenping cycle time', ('localhost', ''))
2012-01-08 03:45:15,528 DEBUG zen.thresholds: Updating threshold ('zenprocess cycle time', ('localhost', ''))
2012-01-08 03:45:15,528 DEBUG zen.ZenStatus: Getting service status
2012-01-08 03:45:15,532 DEBUG zen.ZenStatus: Getting services for /Devices/Server
2012-01-08 03:45:15,656 DEBUG zen.ZenStatus: ZenStatus configured with 0 checks
2012-01-08 03:45:15,658 DEBUG zen.ZenStatus: Getting down devices
2012-01-08 03:45:15,661 DEBUG zen.ZenStatus: Starting scan
2012-01-08 03:45:15,663 DEBUG zen.ZenStatus: Running jobs
2012-01-08 03:45:15,664 DEBUG zen.ZenStatus: Scan complete
2012-01-08 03:45:15,664 INFO zen.ZenStatus: Finished 0 jobs (0 good, 0 bad) in 0.00 seconds
2012-01-08 03:45:15,664 DEBUG zen.ZenStatus: Sent a 'stop' event
2012-01-08 03:45:15,664 DEBUG zen.ZenStatus: stop() called when not running
2012-01-08 03:45:15,665 DEBUG zen.ZenStatus: stop() called when not running
2012-01-08 03:45:15,665 INFO zen.ZenStatus: Daemon ZenStatus shutting down
2012-01-08 03:45:15,667 DEBUG zen.ZenStatus: Removing service EventService
2012-01-08 03:45:15,667 DEBUG zen.ZenStatus: Removing service StatusConfig
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63592#63592]

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]
James Pearce
2012-01-08 03:34:32 UTC
Permalink
James Pearce [http://community.zenoss.org/people/SirTechnology] created the discussion

"Re: IPServices On Some Entire Devices Not Being Monitored By ZenStatus"

To view the discussion, visit: http://community.zenoss.org/message/63594#63594

--------------------------------------------------------------
I have discovered the cause of this issue but not a good way to fix it.

When I create devices, I tend to use mnemonics for the initial device name, and this becomes the device ID. This isn't usually a problem, as I remap the device IP to be correct, and most queries will use this to check if it is set (including ZenPing). ZenStatus, however, will ONLY recognize a device with an FQDN. I haven't tested if it requres the FQDN to resolve or not; my tests involved resolvable FQDN's. By using a mnemonic for my device ID, ZenStatus simply ignores the device, and behaves as if it has no device to check.

My solution is to re-key the device ID's. I don't like having to do this but I can't interpret the ZenStatus Python code well enough to see exactly how it is obtaining the IP service list (I can see the section, I just don't understand the function calls and cannot find any API references).

I am still be interested in someone pointing out how I can force ZenStatus to use the manageIp property of a device as the host rather than the device ID.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/63594#63594]

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]
Loading...