Problem with rabbitmqctl and epmd on RHEL 7 and bugzilla 1104843

294 views
Skip to first unread message

jmcm...@us.ibm.com

unread,
Feb 11, 2015, 12:13:59 PM2/11/15
to rabbitm...@googlegroups.com
I've been battling a problem trying configure rabbitmq in an HA environment on RHEL 7 using chef.  I've been looking at https://bugzilla.redhat.com/show_bug.cgi?id=1104843 which suggests adding "Requires=ep...@0.0.0.0.socket" to the rabbitmq-server.service file. That seems to work for me.

Can anyone tell me if that is likely to be to solution for that bug?

If rabbitmq-server is the only user of epmd, is there a more preferred solution with respect to the epmd process?

Background:

The rabbitmqctl command fails after restarting the rabbitmq-server service with an error like:

Stopping node rabbit@vs181 ...
Error: unable to connect to node rabbit@vs181: nodedown

    DIAGNOSTICS
    ===========

    attempted to contact: [rabbit@vs181]

    rabbit@vs181:
      * connected to epmd (port 4369) on vs181
      * epmd reports: node 'rabbit' not running at all
                      no other nodes on vs181
      * suggestion: start the node

I can work around this in part by running "rabbitmqctl status" before starting rabbitmq-server.

That appears to be https://bugzilla.redhat.com/show_bug.cgi?id=1104843

The comments there led me to try updating rabbitmq-server.service as follows:

[Unit]
Description=RabbitMQ broker
After=syslog.target network.target epmd.socket
Requires=ep...@0.0.0.0.socket

That seems to work, though it leaves an "epmd -systemd" process running even after shutting down rabbitmq.  "systemctl stop ep...@0.0.0.0.socket" appears to take care of that.

Thanks.

Jean-Sébastien Pédron

unread,
Feb 11, 2015, 1:01:53 PM2/11/15
to rabbitm...@googlegroups.com
On 11.02.2015 18:13, jmcm...@us.ibm.com wrote:
> I've been battling a problem trying configure rabbitmq in an HA
> environment on RHEL 7 using chef. I've been looking at
> https://bugzilla.redhat.com/show_bug.cgi?id=1104843 which suggests
> adding "Requires=ep...@0.0.0.0.socket" to the rabbitmq-server.service
> file. That seems to work for me.

Hi!

I never used systemd, but the analysis in the bug report you cited seems
sensible. Red Hat people are better equipped to answer that kind of
question, I would follow their advice.

--
Jean-Sébastien Pédron
Pivotal / RabbitMQ
Reply all
Reply to author
Forward
0 new messages