Archived community.zenoss.org | full text search
Skip navigation
Up to Discussions in zenoss-users
508 Views 1 Reply Latest reply: Feb 18, 2014 6:52 AM by Robert Light RSS
Robert Light Rank: White Belt
Robert Light
11 posts since
Oct 9, 2012
Currently Being Moderated

Feb 3, 2014 8:53 AM

Infrastructure in tact however no events appearing

Hi All!


I would like to believe that our infrastructure is that stable but i know that isnt the case!

 

We are using Zenoss 4.2.0

 

Scenario:

Nothing has appeared to of changed in the environment but all of a sudden we are not getting any events for any of our devices and we have noticed that on the odd occasion one or two of the demons would stop and would need restarting (not unusual for us though).


I am a windows admin so please be gentle!

 

Looking at the demons and their associated logs i can see that we have problems but need a starting piont. Some errors:

 

zenactiond

2014-02-03 12:58:12,678 INFO zen.maintenance: Performing periodic maintenance

2014-02-03 12:58:12,679 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused

2014-02-03 12:58:12,680 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused

2014-02-03 12:58:12,682 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down

2014-02-03 12:59:12,683 INFO zen.maintenance: Performing periodic maintenance

2014-02-03 12:59:12,684 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused

2014-02-03 12:59:12,684 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused

2014-02-03 12:59:12,685 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down

 

zeneventd

2014-02-03 12:57:41,361 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down

2014-02-03 12:58:41,368 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down

2014-02-03 12:59:41,377 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down

2014-02-03 13:00:41,387 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down

2014-02-03 13:01:41,394 ERROR zen.maintenance: Maintenance failed. Message from hub: Could not publish message. Connection may be down

 

zeneventlog

2014-02-03 13:01:49,939 INFO zen.maintenance: Performing periodic maintenance

2014-02-03 13:01:49,940 INFO zen.zeneventlog: Counter discardedEvents, value 148146279

2014-02-03 13:01:49,940 INFO zen.zeneventlog: Counter eventCount, value 177093947

2014-02-03 13:01:49,941 INFO zen.zeneventlog: 30 devices processed (0 datapoints)

2014-02-03 13:01:49,943 INFO zen.collector.scheduler: Tasks: 31 Successful_Runs: 4257 Failed_Runs: 0 Missed_Runs: 15 Queued_Tasks: 0 Running_Tasks: 1 

2014-02-03 13:01:50,067 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

2014-02-03 13:01:50,130 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

2014-02-03 13:02:07,906 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

2014-02-03 13:02:07,969 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

2014-02-03 13:02:08,140 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

2014-02-03 13:02:08,289 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

2014-02-03 13:02:08,486 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

2014-02-03 13:02:08,543 ERROR zen.zeneventlog: Discarding oldest 51 events because maxqueuelen was exceeded: 5051/5000

 

zenhub

2014-02-03 13:07:06,463 INFO zen.ZenHub: Worker (19051) reports

2014-02-03 13:07:06,462 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused

2014-02-03 13:07:06,463 INFO zen.ZenHub: Worker (19051) reports

2014-02-03 13:07:06,463 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused

2014-02-03 13:07:06,463 INFO zen.ZenHub: Worker (19051) reports

2014-02-03 13:07:06,463 ERROR zen.Events: Could not publish message. Connection may be down Traceback (most recent call last): File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 42, in sendEvents self._publishEvent(event, publisher) 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 302, in _publish mandatory, 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

 

zenjobs

Traceback (most recent call last): File "/opt/zenoss/lib/python/celery/worker/consumer.py", line 349, in start self.reset_connection() File "/opt/zenoss/lib/python/celery/worker/consumer.py", line 592, in reset_connection self.connection = self._open_connection() File "/opt/zenoss/lib/python/celery/worker/consumer.py", line 657, in _open_connection self.app.conf.BROKER_CONNECTION_MAX_RETRIES) File "/opt/zenoss/lib/python/kombu/connection.py", line 223, in ensure_connection interval_start, interval_step, interval_max) File "/opt/zenoss/lib/python/kombu/utils/__init__.py", line 158, in retry_over_time return fun(*args, **kwargs) File "/opt/zenoss/lib/python/kombu/connection.py", line 146, in connect return self.connection File "/opt/zenoss/lib/python/kombu/connection.py", line 574, in connection self._connection = self._establish_connection() File "/opt/zenoss/lib/python/kombu/connection.py", line 533, in _establish_connection conn = self.transport.establish_connection() File "/opt/zenoss/lib/python/kombu/transport/amqplib.py", line 278, in establish_connection connect_timeout=conninfo.connect_timeout) File "/opt/zenoss/lib/python/kombu/transport/amqplib.py", line 88, in __init__ super(Connection, self).__init__(*args, **kwargs) File "/opt/zenoss/lib/python/amqplib/client_0_8/connection.py", line 129, in __init__ self.transport = create_transport(host, connect_timeout, ssl) File "/opt/zenoss/lib/python/amqplib/client_0_8/transport.py", line 281, in create_transport return TCPTransport(host, connect_timeout) File "/opt/zenoss/lib/python/amqplib/client_0_8/transport.py", line 85, in __init__ raise socket.error, msg error: [Errno 111] Connection refused

2014-02-03 13:08:25,216 ERROR celery.worker.consumer: Consumer: Connection Error: [Errno 111] Connection refused. Trying again in 2 seconds...

2014-02-03 13:08:27,219 ERROR celery.worker.consumer: Consumer: Connection Error: [Errno 111] Connection refused. Trying again in 4 seconds...

2014-02-03 13:08:31,224 ERROR celery.worker.consumer: Consumer: Connection Error: [Errno 111] Connection refused. Trying again in 6 seconds...

2014-02-03 13:08:37,231 ERROR celery.worker.consumer: Consumer: Connection Error: [Errno 111] Connection refused. Trying again in 8 seconds...

2014-02-03 13:08:45,240 ERROR celery.worker.consumer: Consumer: Connection Error: [Errno 111] Connection refused. Trying again in 10 seconds...

2014-02-03 13:08:55,251 ERROR celery.worker.consumer: Consumer: Connection Error: [Errno 111] Connection refused. Trying again in 12 seconds...

2014-02-03 13:09:07,264 ERROR celery.worker.consumer: Consumer: Connection Error: [Errno 111] Connection refused. Trying again in 14 seconds...

 

All other logs seem to report error free except zopectl which just tells me there is a problem and to forward to zenoss, here is the error details:

 

Type: <type 'exceptions.ValueError'>
Value: 'event' is not a valid daemon name 

Traceback (most recent call last): File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 126, in publish request, bind=1) File "/opt/zenoss/lib/python/ZPublisher/mapply.py", line 77, in mapply if debug is not None: return debug(object,args,context) File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 46, in call_object result=apply(object,args) # Type s<cr> to step into published object. File "/opt/zenoss/lib/python/Products/Five/browser/metaconfigure.py", line 476, in __call__ return self.index(*args, **kw) File "/opt/zenoss/lib/python/Products/Five/browser/pagetemplatefile.py", line 125, in __call__ return self.im_func(im_self, *args, **kw) File "/opt/zenoss/Products/ZenWidgets/FileGzipper.py", line 82, in __call__ return original(self, __instance, *args, **keywords) File "/opt/zenoss/lib/python/Products/Five/browser/pagetemplatefile.py", line 59, in __call__ sourceAnnotations=getattr(debug_flags, 'sourceAnnotations', 0), File "/opt/zenoss/lib/python/zope/pagetemplate/pagetemplate.py", line 132, in pt_render strictinsert=0, sourceAnnotations=sourceAnnotations File "/opt/zenoss/lib/python/zope/pagetemplate/pagetemplate.py", line 240, in __call__ interpreter() File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 266, in __call__ self.interpret(self.program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 883, in do_useMacro self.interpret(macro) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 883, in do_useMacro self.interpret(macro) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 883, in do_useMacro self.interpret(macro) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 941, in do_defineSlot self.interpret(slot) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 941, in do_defineSlot self.interpret(slot) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 941, in do_defineSlot self.interpret(slot) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 883, in do_useMacro self.interpret(macro) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 941, in do_defineSlot self.interpret(slot) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 528, in do_optTag_tal self.do_optTag(stuff) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 513, in do_optTag return self.no_tag(start, program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 508, in no_tag self.interpret(program) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 338, in interpret handlers[opcode](self, args) File "/opt/zenoss/lib/python/zope/tal/talinterpreter.py", line 615, in do_insertText_tal text = self.engine.evaluateText(stuff[0]) File "/opt/zenoss/lib/python/Products/PageTemplates/Expressions.py", line 225, in evaluateText text = self.evaluate(expr) File "/opt/zenoss/lib/python/zope/tales/tales.py", line 696, in evaluate return expression(self) File "/opt/zenoss/lib/python/zope/tales/pythonexpr.py", line 59, in __call__ return eval(self._code, vars) File "<string>", line 1, in <module> File "/opt/zenoss/Products/ZenModel/ZenossInfo.py", line 526, in getLogData filename = self._getLogPath(daemon) File "/opt/zenoss/Products/ZenModel/ZenossInfo.py", line 502, in _getLogPath raise ValueError("%r is not a valid daemon name" % daemon) ValueError: 'event' is not a valid daemon name

 

I am hoping that with the above information someone can give me a starting point. I appologise in advance if this is not in the correct forum.

 

Many thanks

Rob

Tags: mysql, events, issues, zopectl, event_view, events_console, 4.2.0, event_detail, events_mapping
  • Robert Light Rank: White Belt
    Robert Light
    11 posts since
    Oct 9, 2012
    Currently Being Moderated
    1. Feb 18, 2014 6:52 AM (in response to Robert Light)
    Re: Infrastructure in tact however no events appearing

    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

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points