rabbitmq service not starting

[Mate Lakat]

rabbitmq service is not started, thus stack.sh fails
log:
stack@DevStackOSDomU:~/devstack$ tail -20 ../run.sh.log
...
+ sudo rabbitmqctl change_password guest stg
Changing password for user "guest" ...
Error: unable to connect to node rabbit@DevStackOSDomU: nodedown
diagnostics:
- nodes and their ports on DevStackOSDomU: [{rabbitmqctl2571,39555}]
- current node: rabbitmqctl2571@DevStackOSDomU
- current node home dir: /var/lib/rabbitmq
- current node cookie hash: kdwLtDd8HVILeCKALOzb/A==
++ failed
++ local r=2
++ set +o xtrace

version info:
stack@DevStackOSDomU:~$ cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.10
DISTRIB_CODENAME=oneiric
DISTRIB_DESCRIPTION="Ubuntu 11.10"

[Yaguang Tang (heut2008)]

can you start rabbitmq-server manually?

[John Garbutt (johngarbutt)]

Patch uploaded here:
https://review.openstack.org/#/c/10592/

[John Garbutt (johngarbutt)]

This bug is a bit of a special case when using XenServer.

Repro steps:
 - Create VM with DevStack running (using install-os-domU) - uses Ubuntu 11.10
 - Reboot VM (which re-runs stack.sh)
 - Failure happens because RabbitMQ is not started by default, but it started when first installed
 - Rabbit has to be started before the password change can be called, so the password change fails

[HuaHero (huahero-long)]

I also run into the problem,but a little different.I run the ./stack.sh ar root and after a while,it occurs the error "failed-check /var/log/rabbitmq-server ……" and stopped

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.10
DISTRIB_CODENAME=Quantal Quetzal
DISTRIB_DESCRIPTION="Ubuntu 12.10 server 64amd"

which is earlier with no folsom in it

[Yuki Nishiwaki (uckey-1067)]

Hello everyone.

I have encountered this bug.
The current stack.sh fail with no running rabbitmq-server. So we should start rabbitmq-server , if rabbitmq-server is not start.

I will revise it.

[Yuki Nishiwaki (uckey-1067)]

Please check my patch ( https://review.openstack.org/#/c/168705/ )

[Raseel (raseel)]

Hi, didn't know if I should be commenting directly on gerrit code review, since I'm a noob in openstack development.
But I think there is some code redundancy in the patch.
It should be done in either of the following 2 ways :
1. Check if the OS is either fedora or suse or ubuntu and restart rabbitmq service:

- if is_fedora || is_suse; then
+ if is_fedora || is_suse || is_ubuntu; then
                 # service is not started by default
                 restart_service rabbitmq-server
             fi

2. Don't bother to check for OS, just restart rabbitmq service:
- if is_fedora || is_suse; then
- # service is not started by default
- restart_service rabbitmq-server
- fi
+ # service is not started by default
+ restart_service rabbitmq-server

Either of the above options will reduce inclusion of an additioanl if statement.

[Yuki Nishiwaki (uckey-1067)]

Hello Raseel !
Thanks for your comment.

I see . Your comment is right .
I'm about to apply No.1 your suggestion , because I don't know where this script will run .

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/168705
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=0089035504a97fca58cb2383f62ccbb4e6108820
Submitter: Jenkins
Branch: master

commit 0089035504a97fca58cb2383f62ccbb4e6108820
Author: Yuki Nishiwaki <email address hidden>
Date: Sun Mar 29 23:35:39 2015 +0900

    Assurance status of rabbitmq is running

    I changed it so that rabbitmq always restart.

    Current devstack don't restart rabbitmq in case of ubuntu. Because
    rabbitmq is running at default.
    But this approach have the following bug.
    If rabbitmq is already installed and not running , stack.sh will
    fail.
    So I change it so that rabbitmq always restart.

    Closes-bug: #1030798
    Change-Id: Ie45446d3817b2f15631f03b2af84749fe936c67b