Errors in the winperf log:
2014-02-18 05:05:31,397 WARNING zen.winperf.PerfRpc: Bad counter for device 172.20.75.201: \LogicalDisk(\\?\Volume{f4f1740e-c7c4-11df-9dbf-806e6f6e6963})\% Disk Write Time 2014-02-18 05:05:31,397 WARNING zen.winperf.PerfRpc: Bad counter for device 172.20.75.201: \LogicalDisk(\\?\Volume{f4f1740e-c7c4-11df-9dbf-806e6f6e6963})\Free Megabytes 2014-02-18 05:05:31,413 ERROR zen.zenwinperf: No event service: None 2014-02-18 05:05:32,768 WARNING zen.winperf.PerfRpc: Bad counter for device 172.20.75.167: \Messages in Queue 2014-02-18 05:05:33,843 ERROR zen.CollectorCmdBase: Unable to scan device 172.20.75.196: NT_STATUS_IO_TIMEOUT 2014-02-18 10:45:42,574 INFO zen.zenwinperf: Connecting to localhost:8789 2014-02-18 10:45:42,597 INFO zen.zenwinperf: Connected to ZenHub 2014-02-18 10:45:42,613 INFO zen.maintenance: Performing periodic maintenance 2014-02-18 10:45:42,613 INFO zen.zenwinperf: Counter discardedEvents, value 22236 2014-02-18 10:45:42,626 INFO zen.zenwinperf: Counter eventCount, value 2513935 2014-02-18 10:45:42,632 INFO zen.zenwinperf: 0 devices processed (0 datapoints) 2014-02-18 10:45:42,632 INFO zen.collector.scheduler: Tasks: 1 Successful_Runs: 0 Failed_Runs: 0 Missed_Runs: 0 Queued_Tasks: 0 Running_Tasks: 0 2014-02-18 11:00:14,786 ERROR zen.collector.config: Task configLoader configure failed: Traceback (most recent call last): File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner return callable(*args, **kw) File "/opt/zenoss/Products/ZenHub/zenhubworker.py", line 203, in remote_execute return runOnce() File "/opt/zenoss/Products/ZenHub/zenhubworker.py", line 190, in runOnce res = m(*args, **kw) File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 83, in inner traceback.format_exc()) RemoteException: Remote exception: <type 'exceptions.Exception'>: Could not publish message. Connection may be downTraceback (most recent call last): File "/opt/zenoss/Products/ZenHub/PBDaemon.py", line 75, in inner return callable(*args, **kw) File "/opt/zenoss/Products/ZenCollector/services/config.py", line 216, in remote_getDeviceConfigs proxies = self._wrapFunction(self._createDeviceProxies, device) File "/opt/zenoss/Products/ZenCollector/services/config.py", line 126, in _wrapFunction self.sendEvent(evt) File "/opt/zenoss/Products/ZenHub/HubService.py", line 79, in sendEvent self.zem.sendEvent(event) File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 60, in sendEvent event = self._publishEvent(event) File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 82, in _publishEvent publisher.publish(event) File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 283, in publish self._publish("$RawZenEvents", routing_key, event, mandatory=mandatory, immediate=immediate) File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 292, in _publish publisher.publish(exchange, routing_key, proto, mandatory=mandatory, immediate=immediate) File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 376, in publish headers=headers, declareExchange=declareExchange) File "/opt/zenoss/lib/python/zenoss/protocols/amqp.py", line 138, in publish raise Exception("Could not publish message. Connection may be down") Exception: Could not publish message. Connection may be down 2014-02-18 11:03:11,101 INFO zen.maintenance: Performing periodic maintenance 2014-02-18 11:03:11,105 INFO zen.zenwinperf: Counter discardedEvents, value 22236 2014-02-18 11:03:11,111 INFO zen.zenwinperf: Counter eventCount, value 2513935 2014-02-18 11:03:11,141 INFO zen.zenwinperf: 0 devices processed (0 datapoints) 2014-02-18 11:03:11,144 INFO zen.collector.scheduler: Tasks: 1 Successful_Runs: 0 Failed_Runs: 0 Missed_Runs: 0 Queued_Tasks: 0 Running_Tasks: 0 2014-02-18 11:08:11,187 INFO zen.maintenance: Performing periodic maintenance 2014-02-18 11:08:11,188 INFO zen.zenwinperf: Counter discardedEvents, value 22236 2014-02-18 11:08:11,190 INFO zen.zenwinperf: Counter eventCount, value 2513935 2014-02-18 11:08:11,193 INFO zen.zenwinperf: 0 devices processed (0 datapoints) 2014-02-18 11:08:11,194 INFO zen.collector.scheduler: Tasks: 1 Successful_Runs: 0 Failed_Runs: 0 Missed_Runs: 0 Queued_Tasks: 0 Running_Tasks: 0 2014-02-18 11:13:11,226 INFO zen.maintenance: Performing periodic maintenance 2014-02-18 11:13:11,226 INFO zen.zenwinperf: Counter discardedEvents, value 22236 2014-02-18 11:13:11,227 INFO zen.zenwinperf: Counter eventCount, value 2513935 2014-02-18 11:13:11,229 INFO zen.zenwinperf: 0 devices processed (0 datapoints) 2014-02-18 11:13:11,229 INFO zen.collector.scheduler: Tasks: 1 Successful_Runs: 0 Failed_Runs: 0 Missed_Runs: 0 Queued_Tasks: 0 Running_Tasks: 0
Errors in the zeneventd log:
2013-04-03 09:45:55,132 INFO zen.maintenance: Performing periodic maintenance 2013-04-03 09:46:27,242 INFO zen.eventd: Shutting down... 2014-02-12 13:58:04,776 ERROR zen.eventd: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion. ] Traceback (most recent call last): File "/opt/zenoss/Products/ZenEvents/zeneventd.py", line 194, in processMessage yield self.queueConsumer.acknowledge(message) Closed: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion. ] 2014-02-14 10:38:37,505 ERROR zen.eventd: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion. ] Traceback (most recent call last): File "/opt/zenoss/Products/ZenEvents/zeneventd.py", line 194, in processMessage yield self.queueConsumer.acknowledge(message) Closed: [Failure instance: Traceback (failure with no frames): <class 'twisted.internet.error.ConnectionLost'>: Connection to the other side was lost in a non-clean fashion. ] 2014-02-14 10:38:50,015 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down 2014-02-14 10:39:50,271 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down 2014-02-14 10:41:25,516 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down