Hi,
I am having a problem with Zenoss 4.2.4 running on Red Hat Enterprise Linux Server release 6.4 2.6.32-358.el6.x86_64. I have searched the zenoss community and internet pretty extensively.
When I start zenoss zenhub and zope will not start. Everything points to rabbitmq but I am not getting any good information from the logging of rabbitmq.
/var/log/rabbitmq/rabbit@localhost.log
=WARNING REPORT==== 27-Aug-2013::09:04:23 ===
closing AMQP connection <0.278.0> (127.0.0.1:36093 -> 127.0.0.1:5672):
connection_closed_abruptly
This is the message I get whenever I try to start zenhub.
Here are some other logs I have been looking at:
# rabbitmqctl status
Status of node rabbit@localhost ...
[{pid,47180},
{running_applications,[{rabbit,"RabbitMQ","2.8.7"},
{os_mon,"CPO CXC 138 46","2.2.7"},
{sasl,"SASL CXC 138 11","2.1.10"},
{mnesia,"MNESIA CXC 138 12","4.5"},
{stdlib,"ERTS CXC 138 10","1.17.5"},
{kernel,"ERTS CXC 138 10","2.14.5"}]},
{os,{unix,linux}},
{erlang_version,"Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:24:24] [rq:24] [async-threads:30] [kernel-poll:true]\n"},
{memory,[{total,31029512},
{processes,11371088},
{processes_used,11366544},
{system,19658424},
{atom,1139905},
{atom_used,1138863},
{binary,1053232},
{code,11368014},
{ets,2881632}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,60839985152},
{disk_free_limit,1000000000},
{disk_free,1029694262272},
{file_descriptors,[{total_limit,924},
{total_used,18},
{sockets_limit,829},
{sockets_used,8}]},
{processes,[{limit,1048576},{used,236}]},
{run_queue,0},
{uptime,1845}]
...done.
/etc/rabbitmq/rabbitmq-env.conf
RABBITMQ_NODENAME=rabbit@localhost
RABBITMQ_MNESIA_BASE=/opt/zenoss/rabbitmq
RABBITMQ_MNESIA_DIR=/opt/zenoss/rabbitmq/mnesia/rabbit\@localhost
#rabbitmqctl list_vhosts
Listing vhosts ...
/zenoss
/
...done.
# rabbitmqctl list_users
Listing users ...
guest [administrator]
zenoss []
...done.
# rabbitmqctl list_queues -p /zenoss
Listing queues ...
celery 0
zenoss.queues.zep.modelchange 0
zenoss.queues.zep.signal 0
zenoss.queues.zep.migrated.summary 0
zenoss.queues.zep.rawevents 0
zenoss.queues.zep.heartbeats 0
m-prd-zen2.advertising.aol.com.celeryd.pidbox 0
zenoss.queues.zep.zenevents 0
zenoss.queues.zep.migrated.archive 0
...done.
# rabbitmqctl list_user_permissions zenoss
Listing permissions for user "zenoss" ...
/zenoss .* .* .*
...done.
/opt/zenoss/log/zenhub.log
2013-08-26 15:44:18,225 INFO zen.ZenHub: Worker (25825) reports 2013-08-26 15:44:18,224 CRITICAL zen.zenoss.protocols.amqp: Could not use exchange $RawZenEvents: Could not connect to RabbitMQ: [111] Connection refused
2013-08-26 15:44:18,225 INFO zen.ZenHub: Worker (25825) reports 2013-08-26 15:44:18,224 CRITICAL zen.Events: Unable to publish event to <Products.ZenMessaging.queuemessaging.publisher.EventPublisher object at 0x5380c50>: Could not connect to RabbitMQ: [111] Connection refused
2013-08-26 15:44:18,250 INFO zen.ZenHub: Worker (25825) reports 2013-08-26 15:44:18,250 CRITICAL zen.zenoss.protocols.amqp: Could not use exchange $RawZenEvents: Could not connect to RabbitMQ: [111] Connection refused
2013-08-26 15:44:18,251 INFO zen.ZenHub: Worker (25825) reports 2013-08-26 15:44:18,250 CRITICAL zen.Events: Unable to publish event to <Products.ZenMessaging.queuemessaging.publisher.EventPublisher object at 0x5380c50>: Could not connect to RabbitMQ: [111] Connection refused
2013-08-26 15:44:18,271 INFO zen.ZenHub: Worker (25825) reports 2013-08-26 15:44:18,270 CRITICAL zen.zenoss.protocols.amqp: Could not use exchange $RawZenEvents: Could not connect to RabbitMQ: [111] Connection refused
2013-08-26 15:44:18,271 INFO zen.ZenHub: Worker (25825) reports 2013-08-26 15:44:18,271 CRITICAL zen.Events: Unable to publish event to <Products.ZenMessaging.queuemessaging.publisher.EventPublisher object at 0x5380c50>: Could not connect to RabbitMQ: [111] Connection refused
/opt/zenoss/log/event.log
2013-08-27T09:05:40 ERROR ZODB.Connection Couldn't load state for 0x01d101
Traceback (most recent call last):
File "/opt/zenoss/lib/python/ZODB/Connection.py", line 860, in setstate
self._setstate(obj)
File "/opt/zenoss/lib/python/ZODB/Connection.py", line 914, in _setstate
self._reader.setGhostState(obj, p)
File "/opt/zenoss/lib/python/ZODB/serialize.py", line 613, in setGhostState
obj.__setstate__(state)
TypeError: __setstate__() takes exactly 2 arguments (1 given)
/opt/zenoss/log/zenactiond.log
2013-08-27 09:04:49,695 INFO zen.zenoss.protocols.amqp: RabbitMQ connection was closed: [Errno 104] Connection reset by peer
/opt/zenoss/etc/global.conf
amqphost localhost
amqpport 5672
amqpvhost /zenoss
amqpuser zenoss
amqppassword zenoss
amqpusessl 0
amqpadminport 55672
amqpadminusessl 0
This did work initially and i don't believe anything has changed so i don't know why it is not working all of the sudden. Thanks for any help!
Ken