Hi,

Whilst messing about with my Zenoss 4 test server (CentOS 6 x64, Zenoss 4.1.70-1554) I switched from DHCP to a static IP (the same IP for both), turned on nic bonding and put a proper hostname entry in /etc/hosts. Unfortunately this combination has stopped zenhub working, and I think it may be rabbitmq related. I've followed the steps in the relase notes about what to do on a hostname change (below) but no joy:

export VHOST="/zenoss"
export USER="zenoss"
export PASS="zenoss"
rabbitmqctl stop_app
rabbitmqctl reset
rabbitmqctl start_app
rabbitmqctl add_vhost "$VHOST"
rabbitmqctl add_user "$USER" "$PASS"
rabbitmqctl set_permissions -p "$VHOST" "$USER" '.*' '.*' '.*'

So I tuned on debugging for zenhub, and that says:

2012-06-28 10:09:11,430 INFO zen.HubService.RenderConfig: Starting graph retrieval listener on port 8090
2012-06-28 10:09:11,437 DEBUG zen.Events: ===============  incoming event  ===============
2012-06-28 10:09:11,441 DEBUG zen.queuepublisher: About to publish this event to the raw event queue:uuid: "ecc5ec52-c100-11e1-b75d-005056810132"
created_time: 1340874551437
event_class: "/App/Start"
actor {
  element_type_id: DEVICE
  element_identifier: "localhost"
  element_sub_type_id: COMPONENT
  element_sub_identifier: "zenhub"
}
summary: "zenhub started"
severity: SEVERITY_CLEAR
event_key: ""
, with this routing key: zenoss.zenevent.app.start
2012-06-28 10:09:11,443 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused
2012-06-28 10:09:11,444 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused
2012-06-28 10:09:11,444 ERROR zen.ZenHub: Unable to send an event
Traceback (most recent call last):
  File "/opt/zenoss/Products/ZenHub/zenhub.py", line 488, in sendEvent
    self.zem.sendEvent(Event(**kw))
  File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 63, in sendEvent
    event = self._publishEvent(event)
  File "/opt/zenoss/Products/ZenEvents/MySqlSendEvent.py", line 85, in _publishEvent
    publisher.publish(event)
  File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 285, in publish
    self._publish("$RawZenEvents", routing_key, event, mandatory=mandatory, immediate=immediate)
  File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 304, in _publish
    mandatory, immediate)
  File "/opt/zenoss/Products/ZenMessaging/queuemessaging/publisher.py", line 378, in publish
    headers=headers, declareExchange=declareExchange)
  File "/opt/zenoss/lib/python/zenoss/protocols/amqp.py", line 140, in publish
    raise Exception("Could not publish message. Connection may be down")
Exception: Could not publish message. Connection may be down
2012-06-28 10:09:15,388 DEBUG zen.ZenHub: Registered 2 invalidation filters.
2012-06-28 10:09:15,460 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost collector', ''))
2012-06-28 10:09:15,461 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost collector', ''))
2012-06-28 10:09:15,466 DEBUG zen.ZenHub: Starting /opt/zenoss/bin/zenhubworker run -C /opt/zenoss/var/zenhub/localhost_worker.conf
2012-06-28 10:09:15,469 DEBUG zen.ZenHub: Starting /opt/zenoss/bin/zenhubworker run -C /opt/zenoss/var/zenhub/localhost_worker.conf
2012-06-28 10:09:15,671 DEBUG zen.Events: ===============  incoming event  ===============
2012-06-28 10:09:15,672 DEBUG zen.Events: Got a localhost zenhub heartbeat event (timeout 90 sec).
2012-06-28 10:09:15,674 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused
2012-06-28 10:09:15,675 INFO zen.zenoss.protocols.amqp: amqp connection was closed [Errno 111] Connection refused

I think the rabbitmq setup maybe a bit unhappy at the change. Does anyone have an idea of how to sort this out? Thanks in advance!

Cheers,

J