ERR: Could not start Service[rabbitmq-server]

Bug #1334172 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
High
Fuel Library (Deprecated)

Bug Description

"build_id": "2014-06-24_14-57-29",
"mirantis": "yes",
"build_number": "269",
"ostf_sha": "4d2efa822344b6ca022ec4086b6f083c07d90e14",
"nailgun_sha": "b8713a4026239e7b1769e64239e54950ef7c739b",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "b8c33af2da36f81828e68b77da4025e59aee3283",
"astute_sha": "694b5a55695e01e1c42185bfac9cc7a641a9bd48",
"release": "5.1",
"fuellib_sha": "8ec900a2bc96a463a72405a674e41f52fc0d3e14"

1. Create new environment (CentOS, HA mode)
2. Choose VLAN segmentation
3. Choose both Ceph
4. Add 3 controllers, 2 computes, 2 ceph
5. Start deployment. It has failed
6. There are errors on third controller (node-3):

2014-06-24 17:57:59 ERR

 (/Stage[main]/Rabbitmq::Service/Service[rabbitmq-server]/ensure) change from stopped to running failed: Could not start Service[rabbitmq-server]: Execution of '/sbin/service rabbitmq-server start' returned 2:

Revision history for this message
Anastasia Palkina (apalkina) wrote :
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

RCA for rabbitmq failed start at node-3 is:
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: =CRASH REPORT==== 24-Jun-2014::16:57:44 ===
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: crasher:
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: initial call: application_master:init/4
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: pid: <0.70.0>
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: registered_name: []
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: exception exit: {bad_return,
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: {{rabbit,start,[normal,[]]},
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: {'EXIT',
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: {rabbit,failure_during_boot,
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: {badmatch,
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: {error,
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: {cannot_discover_cluster,
./rabbitmq-sasl.log:2014-06-24T17:57:48.733217+01:00 notice: "The nodes provided are either offline or not running"}}}}}}}

Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Here is a full list of rabbitmq config and start up events
http://pastebin.com/gzdhCXmw
Node-1 have rmq configured and started up OK, but for some reasons, node-2 and node-3 wasn't be able to 'see' cluster_nodes specified in its configs while starting up

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.