Bug 869415

Summary: init script does not work as rabbitmqctl status returns 0 for a nodedown
Product: [Fedora] Fedora EPEL Reporter: Julian C. Dunn <jdunn>
Component: rabbitmq-serverAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: hubert.plociniczak, lemenkov
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-17 10:31:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Julian C. Dunn 2012-10-23 19:59:15 UTC 
Description of problem:

The init script that comes with rabbitmq-server does not work properly to start RabbitMQ.


Version-Release number of selected component (if applicable):

2.6.1-1.el6

How reproducible:

Always

Steps to Reproduce:
1. Install rabbitmq-server.
2. Try to start it.
3.
  
Actual results:

Does not start with:

[root@foo ec2-user]$ /etc/init.d/rabbitmq-server start
Starting rabbitmq-server: RabbitMQ is currently running
rabbitmq-server.


Expected results:

Can start rabbitmq normally.


Additional info:

The problem is that the init script contains a fragment like:

     status_rabbitmq quiet
     if [ $RETVAL = 0 ] ; then
         echo RabbitMQ is currently running
     else

The status_rabbitmq function calls "rabbitmqctl status", which returns 0 even if there is no node running:

[root@foo rabbitmq]$ /etc/init.d/rabbitmq-server start
Starting rabbitmq-server: Status of node rabbit@chef1 ...
Error: unable to connect to node rabbit@foo: nodedown
diagnostics:
- nodes and their ports on chef1: [{rabbitmqctl10423,50219}]
- current node: rabbitmqctl10423@foo
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: emi4ETUoBL1ALyHizJ1BIg==
[root@foo rabbitmq]$ echo $?
0


So a non-zero return value of "rabbitmqctl status" is not a good canonical test for whether RabbitMQ is actually running.
Comment 1 Peter Lemenkov 2014-11-17 10:31:42 UTC 
Erlang was abandonded in EPEL6 and removed along with all dependent packages.