jpifer
2012-10-02 20:49:48 UTC
jpifer [http://community.zenoss.org/people/jpifer] created the discussion
"zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer"
To view the discussion, visit: http://community.zenoss.org/message/68828#68828
--------------------------------------------------------------
At first I was having a problem with zenhub not running, and found some things to try in the forum about the environment and re-running $ZENHOME/bin/zenoss_upgrade_pre. After going through these steps, zenhub is running, but zentrap can't connect to zenhub. As far as I can see zenhub is running, but it's not listening on the configured port, which is the default.
I'm hoping someone can help me here as I'm trying to evaluate Zenoss as a possible replacement for our current IBM Netcool and Nagios setups.
Thanks,
James
Here's some more information:
zenhub log:
2012-10-02 16:02:32,233 INFO zen.HubService.RenderConfig: Starting graph retrieval listener on port 8090
2012-10-02 16:02:35,255 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
2012-10-02 16:02:38,266 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
2012-10-02 16:02:38,266 ERROR zen.ZenHub: Unable to send an event
Traceback (most recent call last):
 File "/opt/zenoss/Products/ZenHub/zenhub.py", line 576, in sendEvent
   self.zem.sendEvent(Event(**kw))
 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 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
2012-10-02 16:02:44,596 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
2012-10-02 16:02:47,604 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
[***@zenoss var]# /usr/sbin/rabbitmqctl list_queues -p /zenoss
Listing queues ...
celery 0
zenoss.queues.zep.migrated.summary     0
zenoss.queues.zep.migrated.archive     0
zenoss.queues.zep.rawevents    0
zenoss.queues.zep.heartbeats   0
zenoss.queues.zep.zenevents    0
zenoss.domain.com.celeryd.pidbox    0
zenoss.queues.zep.modelchange  0
zenoss.queues.zep.signal       0
...done.
[***@zenoss var]# netstat -ano | grep 5672
tcp       0     0 127.0.0.1:43703            127.0.0.1:5672             ESTABLISHED off (0.00/0/0)
tcp       0     0 127.0.0.1:43709            127.0.0.1:5672             ESTABLISHED keepalive (6102.64/0/0)
tcp       0     0 127.0.0.1:43704            127.0.0.1:5672             ESTABLISHED keepalive (6086.15/0/0)
tcp       0     0 127.0.0.1:43686            127.0.0.1:5672             ESTABLISHED keepalive (6054.77/0/0)
tcp       0     0 127.0.0.1:43687            127.0.0.1:5672             ESTABLISHED keepalive (6057.13/0/0)
tcp       0     0 127.0.0.1:43692            127.0.0.1:5672             ESTABLISHED keepalive (6062.50/0/0)
tcp       0     0 127.0.0.1:43691            127.0.0.1:5672             ESTABLISHED off (0.00/0/0)
tcp       0     0 :::5672                    :::*                       LISTEN     off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:43678     ::ffff:127.0.0.1:5672      ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43678     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43703     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43709     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43704     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43686     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43687     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43692     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43691     ESTABLISHED off (0.00/0/0)
[***@zenoss var]# rabbitmqctl list_users
Listing users ...
zenoss []
guest  [administrator]
...done.
[***@zenoss var]# cat /opt/zenoss/etc/global.conf | grep amqp
amqphost localhost
amqpport 5672
amqpvhost /zenoss
amqpuser zenoss
amqppassword zenoss
amqpusessl 0
amqpadminport 55672
amqpadminusessl 0
[***@zenoss var]#Â Â Â Â amqp_user=`cat /opt/zenoss/etc/global.conf | grep amqpuser | gawk '{print $2}'` rabbitmqctl list_user_permissions -p /zenoss $amqp_user
Listing permissions for user "zenoss" ...
/zenoss .*Â Â Â Â Â .*Â Â Â Â Â .*
...done.
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68828#68828]
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]
"zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer"
To view the discussion, visit: http://community.zenoss.org/message/68828#68828
--------------------------------------------------------------
At first I was having a problem with zenhub not running, and found some things to try in the forum about the environment and re-running $ZENHOME/bin/zenoss_upgrade_pre. After going through these steps, zenhub is running, but zentrap can't connect to zenhub. As far as I can see zenhub is running, but it's not listening on the configured port, which is the default.
I'm hoping someone can help me here as I'm trying to evaluate Zenoss as a possible replacement for our current IBM Netcool and Nagios setups.
Thanks,
James
Here's some more information:
zenhub log:
2012-10-02 16:02:32,233 INFO zen.HubService.RenderConfig: Starting graph retrieval listener on port 8090
2012-10-02 16:02:35,255 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
2012-10-02 16:02:38,266 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
2012-10-02 16:02:38,266 ERROR zen.ZenHub: Unable to send an event
Traceback (most recent call last):
 File "/opt/zenoss/Products/ZenHub/zenhub.py", line 576, in sendEvent
   self.zem.sendEvent(Event(**kw))
 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 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
2012-10-02 16:02:44,596 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
2012-10-02 16:02:47,604 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 104] Connection reset by peer
[***@zenoss var]# /usr/sbin/rabbitmqctl list_queues -p /zenoss
Listing queues ...
celery 0
zenoss.queues.zep.migrated.summary     0
zenoss.queues.zep.migrated.archive     0
zenoss.queues.zep.rawevents    0
zenoss.queues.zep.heartbeats   0
zenoss.queues.zep.zenevents    0
zenoss.domain.com.celeryd.pidbox    0
zenoss.queues.zep.modelchange  0
zenoss.queues.zep.signal       0
...done.
[***@zenoss var]# netstat -ano | grep 5672
tcp       0     0 127.0.0.1:43703            127.0.0.1:5672             ESTABLISHED off (0.00/0/0)
tcp       0     0 127.0.0.1:43709            127.0.0.1:5672             ESTABLISHED keepalive (6102.64/0/0)
tcp       0     0 127.0.0.1:43704            127.0.0.1:5672             ESTABLISHED keepalive (6086.15/0/0)
tcp       0     0 127.0.0.1:43686            127.0.0.1:5672             ESTABLISHED keepalive (6054.77/0/0)
tcp       0     0 127.0.0.1:43687            127.0.0.1:5672             ESTABLISHED keepalive (6057.13/0/0)
tcp       0     0 127.0.0.1:43692            127.0.0.1:5672             ESTABLISHED keepalive (6062.50/0/0)
tcp       0     0 127.0.0.1:43691            127.0.0.1:5672             ESTABLISHED off (0.00/0/0)
tcp       0     0 :::5672                    :::*                       LISTEN     off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:43678     ::ffff:127.0.0.1:5672      ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43678     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43703     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43709     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43704     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43686     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43687     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43692     ESTABLISHED off (0.00/0/0)
tcp       0     0 ::ffff:127.0.0.1:5672      ::ffff:127.0.0.1:43691     ESTABLISHED off (0.00/0/0)
[***@zenoss var]# rabbitmqctl list_users
Listing users ...
zenoss []
guest  [administrator]
...done.
[***@zenoss var]# cat /opt/zenoss/etc/global.conf | grep amqp
amqphost localhost
amqpport 5672
amqpvhost /zenoss
amqpuser zenoss
amqppassword zenoss
amqpusessl 0
amqpadminport 55672
amqpadminusessl 0
[***@zenoss var]#Â Â Â Â amqp_user=`cat /opt/zenoss/etc/global.conf | grep amqpuser | gawk '{print $2}'` rabbitmqctl list_user_permissions -p /zenoss $amqp_user
Listing permissions for user "zenoss" ...
/zenoss .*Â Â Â Â Â .*Â Â Â Â Â .*
...done.
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/68828#68828]
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]