[rabbitmq-discuss] Rabbitmq up and running but connection_closed_abruptly
Ken Henry
kenhen93 at gmail.com
Thu Sep 5 21:09:34 BST 2013
Hi,
I am hoping you can help me as no one on the Zenoss forum is.
I am learning a lot about RabbitMQ during this troubleshooting process! :-)
I setup a two node veritas cluster running Zenoss which uses rabbitmq. In
my configuration, i believe RabbitMQ does not know it is a cluster.
The cluster consists of a SAN drive this is switches between nodes on
failover. Each node had rabbitmq installed then I move the mnesia database
to the SAN drive and implemented a rabbitmq-env.conf
tail /etc/rabbitmq/rabbitmq-env.conf
RABBITMQ_NODENAME=rabbit at localhost
RABBITMQ_MNESIA_BASE=/opt/zenoss/rabbitmq
RABBITMQ_MNESIA_DIR=/opt/zenoss/rabbitmq/mnesia/rabbit\@localhost
By making the rabbitmq nodename localhost, I did not think it would have a
problem with the failover as both hosts are localhost and it does not seem
like there is a problem.
RabbitMQ runs fine on both hosts and host B gets an error when the Zenoss
servers tries to connect to rabbitmq
=INFO REPORT==== 5-Sep-2013::15:11:36 ===
accepting AMQP connection <0.470.0> (127.0.0.1:44024 -> 127.0.0.1:5672)
=WARNING REPORT==== 5-Sep-2013::15:11:36 ===
closing AMQP connection <0.470.0> (127.0.0.1:44024 -> 127.0.0.1:5672):
connection_closed_abruptly
service rabbitmq-server status
Status of node rabbit at localhost ...
[{pid,9372},
{running_applications,
[{rabbitmq_management,"RabbitMQ Management Console","2.8.7"},
{rabbitmq_management_agent,"RabbitMQ Management Agent","2.8.7"},
{amqp_client,"RabbitMQ AMQP Client","2.8.7"},
{rabbit,"RabbitMQ","2.8.7"},
{os_mon,"CPO CXC 138 46","2.2.7"},
{sasl,"SASL CXC 138 11","2.1.10"},
{rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","2.8.7"},
{webmachine,"webmachine","1.9.1-rmq2.8.7-git52e62bc"},
{mochiweb,"MochiMedia Web Server","2.3.1-rmq2.8.7-gitd541e9a"},
{inets,"INETS CXC 138 49","5.7.1"},
{xmerl,"XML parser","1.2.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,42808712},
{processes,13595840},
{processes_used,13579352},
{system,29212872},
{atom,1538337},
{atom_used,1523802},
{binary,3428320},
{code,17183366},
{ets,3819312}]},
{vm_memory_high_watermark,0.4},
{vm_memory_limit,60839985152},
{disk_free_limit,1000000000},
{disk_free,1029454253056},
{file_descriptors,
[{total_limit,924},
{total_used,20},
{sockets_limit,829},
{sockets_used,10}]},
{processes,[{limit,1048576},{used,303}]},
{run_queue,0},
{uptime,3704}]
...done.
rabbitmqctl list_connections
Listing connections ...
zenoss 127.0.0.1 43982 running
zenoss 127.0.0.1 43981 running
zenoss 127.0.0.1 43979 running
zenoss 127.0.0.1 43989 running
zenoss 127.0.0.1 43994 running
zenoss 127.0.0.1 43980 running
zenoss 127.0.0.1 43969 running
zenoss 127.0.0.1 43988 running
zenoss 127.0.0.1 43985 running
...done.
I am guessing these connections were made originally before the connection
was closed abruptly?
Can anyone please help?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130905/d2a8aad7/attachment.htm>
More information about the rabbitmq-discuss
mailing list