Description of problem: if the answer file has this line CONFIG_AMQP_ENABLE_SSL=n set to yes rabbitmq will fail to start Version-Release number of selected component (if applicable): How reproducible: every _SINGLE_ time Steps to Reproduce: 1.see above 2. 3. Actual results: fail Expected results: should work Additional info:
During setup, packstack creates two files in /etc/rabbitmq: - rabbitmq-env.conf - rabbitmq.config rabbitmq-env.conf contains only one line, like that: RABBITMQ_NODE_PORT=5671 In /var/log/rabbitmq/rabbit@<hostname>.log, the issue seems due to rabbitmq-server which tries to start a second instance of rabbitmq on the same port 5671, already in use so it reports a failure: =INFO REPORT==== 25-Jan-2015::02:05:34 === stopped TCP Listener on [::]:5671 =INFO REPORT==== 25-Jan-2015::02:05:34 === Error description: {could_not_start,rabbit, {bad_return, {{rabbit,start,[normal,[]]}, {'EXIT', {rabbit,failure_during_boot, {case_clause,{error,{already_started,<0.195.0>}}}}}}}} Set the value of "RABBITMQ_NODE_PORT" in rabbitmq-env.conf to another value like, for example, "5672" (non-SSL listener) or (better) simply delete the file "rabbitmq-env.conf" or delete/comment the line with "RABBITMQ_NODE_PORT" (leaving it empty) avoid the issue and rabbitmq-server can be started with SSL and no errors: [root@openstack etc]# grep -i SSL /var/log/rabbitmq/* /var/log/rabbitmq/rabbit:started SSL Listener on [::]:5671 The issue occurs on Red Hat/CentOS 7 with juno as with icehouse.
Created attachment 983869 [details] rabbitmq-server log with erorr
Created attachment 983870 [details] rabbitmq-server log after deleting rabbitmq-env.conf
The value of the setting in "rabbitmq-env.conf" is managed by this line in the default answer file: "CONFIG_AMQP_SSL_PORT=5671" Unfortunately, comment out this line in the answer file while CONFIG_AMQP_ENABLE_SSL=y does not do the trick (the rabbitmq-env.conf is still created with the default value 5671) and leave it empty is not an option because "NULL" is a value not allowed for this line by packstack. So seems that there are no quick workaround and a patch is needed to address the issue... The bug seems related to "Bug 1147224 - Packstack install AMQP with SSL, fails to start rabbitmq service" but is it abandoned?
This issue was fixed between the Icehouse and Juno releases. Closing now.