Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1269255

Summary:

Failed to start RabbitMQ broker.

Product:

[Community] RDO

Reporter:

Phill. Whiteside <phillw>

Component:

openstack-packstack

Assignee:

Ivan Chavero <ichavero>

Status:

CLOSED WORKSFORME

QA Contact:

yeylon <yeylon>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

Kilo

CC:

aortega, derekh, ichavero, srevivo, yeylon

Target Milestone:

---

Target Release:

Kilo

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

openstack-packstack-2015.1-0.11.dev1616.g5526c38.fc23

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-11-09 21:07:52 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:

Attachments:

Description	Flags
setup log	none

Description Phill. Whiteside 2015-10-06 19:43:51 UTC

Created attachment 1080380 [details]
setup log

Description of problem:
When using packstack --answer-file=/root/answerfile.txt 
Installation Errors at setting up rabbit


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


How reproducible:
Each time

Steps to Reproduce:
1. Clean Installation of CentOS v7 
2. Update CentOS v7
3. install packstack and create /boot/answerfile.txt
3. Use work around for bug #1259354
4. packstack --answer-file=answerfile.txt

Actual results:
192.168.1.100_amqp.pp:                            [ ERROR ]         
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.1.100_amqp.pp
Error: Could not start Service[rabbitmq-server]: Execution of '/usr/bin/systemctl start rabbitmq-server' returned 1: Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.


Expected results:
Install to complete

Additional info:
[root@cloud ~]# /sbin/service rabbitmq-server start
Redirecting to /bin/systemctl start  rabbitmq-server.service
Job for rabbitmq-server.service failed. See 'systemctl status rabbitmq-server.service' and 'journalctl -xn' for details.

Output of journalctl -u rabbitmq-server

[root@cloud ~]# journalctl -u rabbitmq-server
-- Logs begin at Sun 2015-10-04 19:53:13 BST, end at Tue 2015-10-06 20:08:51 BST. --
Oct 04 20:41:04 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6693, but reception only p
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6695, but reception only p
Oct 04 20:41:34 cloud.phillw.net rabbitmq-server[6680]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 20:41:34 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 20:41:35 cloud.phillw.net rabbitmqctl[6805]: Stopping and halting node rabbit@cloud ...
Oct 04 20:41:42 cloud.phillw.net rabbitmqctl[6805]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: DIAGNOSTICS
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: ===========
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: attempted to contact: [rabbit@cloud]
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: rabbit@cloud:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: current node details:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - node name: rabbitmqctl6805@cloud
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - home dir: /var/lib/rabbitmq
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 20:42:12 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 04 23:33:57 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8866, but reception only p
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8868, but reception only p
Oct 04 23:34:27 cloud.phillw.net rabbitmq-server[8853]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 23:34:27 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 23:34:27 cloud.phillw.net rabbitmqctl[8973]: Stopping and halting node rabbit@cloud ...
Oct 04 23:34:34 cloud.phillw.net rabbitmqctl[8973]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: DIAGNOSTICS
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: ===========
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: attempted to contact: [rabbit@cloud]
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: rabbit@cloud:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: current node details:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - node name: rabbitmqctl8973@cloud
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - home dir: /var/lib/rabbitmq
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 23:35:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 06 20:07:43 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13162, but reception only 
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13164, but reception only 
Oct 06 20:08:14 cloud.phillw.net rabbitmq-server[13149]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 06 20:08:14 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 06 20:08:14 cloud.phillw.net rabbitmqctl[13185]: Stopping and halting node rabbit@cloud ...
Oct 06 20:08:21 cloud.phillw.net rabbitmqctl[13185]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: DIAGNOSTICS
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: ===========
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: attempted to contact: [rabbit@cloud]
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: rabbit@cloud:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: current node details:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - node name: rabbitmqctl13185@cloud
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - home dir: /var/lib/rabbitmq
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 06 20:08:51 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
[root@cloud ~]# journalctl -u rabbitmq-server
-- Logs begin at Sun 2015-10-04 19:53:13 BST, end at Tue 2015-10-06 20:08:51 BST. --
Oct 04 20:41:04 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6693, but reception only permitted for PID 6680
Oct 04 20:41:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 6695, but reception only permitted for PID 6680
Oct 04 20:41:34 cloud.phillw.net rabbitmq-server[6680]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 20:41:34 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 20:41:35 cloud.phillw.net rabbitmqctl[6805]: Stopping and halting node rabbit@cloud ...
Oct 04 20:41:42 cloud.phillw.net rabbitmqctl[6805]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: DIAGNOSTICS
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: ===========
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: attempted to contact: [rabbit@cloud]
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: rabbit@cloud:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: current node details:
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - node name: rabbitmqctl6805@cloud
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - home dir: /var/lib/rabbitmq
Oct 04 20:42:12 cloud.phillw.net rabbitmqctl[6805]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 20:42:12 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 20:42:12 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 04 23:33:57 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8866, but reception only permitted for PID 8853
Oct 04 23:33:57 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 8868, but reception only permitted for PID 8853
Oct 04 23:34:27 cloud.phillw.net rabbitmq-server[8853]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 04 23:34:27 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 04 23:34:27 cloud.phillw.net rabbitmqctl[8973]: Stopping and halting node rabbit@cloud ...
Oct 04 23:34:34 cloud.phillw.net rabbitmqctl[8973]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: DIAGNOSTICS
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: ===========
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: attempted to contact: [rabbit@cloud]
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: rabbit@cloud:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: current node details:
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - node name: rabbitmqctl8973@cloud
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - home dir: /var/lib/rabbitmq
Oct 04 23:35:04 cloud.phillw.net rabbitmqctl[8973]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 04 23:35:04 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 04 23:35:04 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.
Oct 06 20:07:43 cloud.phillw.net systemd[1]: Starting RabbitMQ broker...
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13162, but reception only permitted for PID 13149
Oct 06 20:07:43 cloud.phillw.net systemd[1]: rabbitmq-server.service: Got notification message from PID 13164, but reception only permitted for PID 13149
Oct 06 20:08:14 cloud.phillw.net rabbitmq-server[13149]: ERROR: epmd error for host cloud: timeout (timed out)
Oct 06 20:08:14 cloud.phillw.net systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Oct 06 20:08:14 cloud.phillw.net rabbitmqctl[13185]: Stopping and halting node rabbit@cloud ...
Oct 06 20:08:21 cloud.phillw.net rabbitmqctl[13185]: Error: unable to connect to node rabbit@cloud: nodedown
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: DIAGNOSTICS
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: ===========
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: attempted to contact: [rabbit@cloud]
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: rabbit@cloud:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: * unable to connect to epmd (port 4369) on cloud: timeout (timed out)
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: current node details:
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - node name: rabbitmqctl13185@cloud
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - home dir: /var/lib/rabbitmq
Oct 06 20:08:51 cloud.phillw.net rabbitmqctl[13185]: - cookie hash: kT43mJmvOoNxBNx/TuSkFQ==
Oct 06 20:08:51 cloud.phillw.net systemd[1]: rabbitmq-server.service: control process exited, code=exited status=2
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Failed to start RabbitMQ broker.
Oct 06 20:08:51 cloud.phillw.net systemd[1]: Unit rabbitmq-server.service entered failed state.


------
I have seen such a similar issue at https://bugzilla.redhat.com/show_bug.cgi?id=1148604

Comment 1 Ivan Chavero 2015-11-09 21:07:52 UTC

Tested with 
openstack-packstack-2015.1-0.11.dev1616.g5526c38.fc23 
CentOS Linux release 7.1.1503 (Core)

On this setup the problem does not appear.