Zenoss ZenTech Community

I doubt it's related, but I cloned my zenoss VM and as soon as I did that, the CPU on my original VM went through the roof and it is just hanging there. Here is what I am seeing in my zenhub.log. Can anybody help with this



14-04-30 10:05:49,221 INFO zen.ZenHub: Worker (3140) reports 2014-04-30 10:05:49,220 CRITICAL zen.zenoss.protocols.amqp: Could not use exchange $RawZenEvents: [Errno 104] Connection reset by peer

2014-04-30 10:05:49,221 CRITICAL zen.Events: Unable to publish event to : [Errno 104] Connection reset by peer

2014-04-30 10:05:51,969 INFO zen.ZenHub: Worker (3139) reports 2014-04-30 10:05:51,968 CRITICAL zen.zenoss.protocols.amqp: Could not use exchange $RawZenEvents: [Errno 104] Connection reset by peer

2014-04-30 10:05:51,968 CRITICAL zen.Events: Unable to publish event to : [Errno 104] Connection reset by peer

2014-04-30 10:05:51,970 INFO zen.ZenHub: Worker (3139) reports Exception

2014-04-30 10:05:51,970 INFO zen.ZenHub: Worker (3139) reports socket

2014-04-30 10:05:51,971 INFO zen.ZenHub: Worker (3139) reports .

2014-04-30 10:05:51,971 INFO zen.ZenHub: Worker (3139) reports error

2014-04-30 10:05:51,971 INFO zen.ZenHub: Worker (3139) reports :

2014-04-30 10:05:51,971 INFO zen.ZenHub: Worker (3139) reports (

2014-04-30 10:05:51,971 INFO zen.ZenHub: Worker (3139) reports 107

2014-04-30 10:05:51,972 INFO zen.ZenHub: Worker (3139) reports ,

2014-04-30 10:05:51,972 INFO zen.ZenHub: Worker (3139) reports '

2014-04-30 10:05:51,972 INFO zen.ZenHub: Worker (3139) reports T

2014-04-30 10:05:51,972 INFO zen.ZenHub: Worker (3139) reports r

2014-04-30 10:05:51,972 INFO zen.ZenHub: Worker (3139) reports a

2014-04-30 10:05:51,973 INFO zen.ZenHub: Worker (3139) reports n

2014-04-30 10:05:51,973 INFO zen.ZenHub: Worker (3139) reports s

2014-04-30 10:05:51,973 INFO zen.ZenHub: Worker (3139) reports p

2014-04-30 10:05:51,973 INFO zen.ZenHub: Worker (3139) reports o

2014-04-30 10:05:51,973 INFO zen.ZenHub: Worker (3139) reports r

2014-04-30 10:05:51,973 INFO zen.ZenHub: Worker (3139) reports t

2014-04-30 10:05:51,974 INFO zen.ZenHub: Worker (3139) reports

2014-04-30 10:05:51,976 INFO zen.ZenHub: Worker (3139) reports endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

Exception socket.error: (107, 'Transport endpoint is not connected') in > ignored

2014-04-30 10:05:52,227 INFO zen.ZenHub: Worker (3140) reports 2014-04-30 10:05:52,226 INFO zen.zenoss.protocols.amqp: RabbitMQ connection was closed: [Errno 104] Connection reset by peer

2014-04-30 10:05:54,979 INFO zen.ZenHub: Worker (3139) reports 2014-04-30 10:05:54,978 INFO zen.zenoss.protocols.amqp: RabbitMQ connection was closed: [Errno 104] Connection reset by peer

2014-04-30 10:05:55,230 INFO zen.ZenHub: Worker (3140) reports 2014-04-30 10:05:55,229 INFO zen.zenoss.protocols.amqp: RabbitMQ connection was closed: [Errno 104] Connection reset by peer

2014-04-30 10:05:55,229 ERROR zen.Events: Unable to publish event to 

Traceback (most recent call last):

File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 43, in sendEvents

self._publishEvent(event, publisher)

File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 92, in _publishEvent

publisher.publish(event)

File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 319, in publish

self._publish("$RawZenEvents", routing_key, event, mandatory=mandatory)

File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 346, in _publish

mandatory=mandatory, createQueues=createQueues)

File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 416, in publish

headers=headers, declareExchange=declareExchange)

File "/opt/zenoss/lib/python/zenoss/protocols/amqp.py", line 176, in publish

raise Exception("Could not publish message to RabbitMQ: %s" % lastexc)

Exception: Could not publish message to RabbitMQ: [Errno 104] Connection reset by peer

Subject:	I went ahead and restored
Author:	[Not Specified]
Posted:	2014-04-30 10:49

I went ahead and restored from backup since I wasn't collecting data anymore.

Subject:	Did both the virtual machines
Author:	[Not Specified]
Posted:	2014-04-30 11:09

Did both the virtual machines have the same IP

Hydruid

Subject:	It's certainly possible that
Author:	[Not Specified]
Posted:	2014-04-30 11:58

It's certainly possible that they were conflicting in some way.....time to test it again to see if the same thing happens!

Hydruid

Subject:	Yeah, that's not going to
Author:	[Not Specified]
Posted:	2014-04-30 13:17

Yeah, that's not going to happen anytime soon! Thanks for helping!

Subject:	High CPU
Author:	[Not Specified]
Posted:	2014-04-30 10:11

High CPU