Error (Systemd start for rabbitmq-server failed) while installing Packstack on new CentOS?

asked 2017-06-10 01:54:36 -0500

zetret12 gravatar image

updated 2017-06-10 01:58:28 -0500

This is the error:

ERROR : Error appeared during Puppet run: 192.168.0.201_controller.pp
Error: Systemd start for rabbitmq-server failed!
You will find full trace in log /var/tmp/packstack/20170610-021122-_QyFqg/manifests/192.168.0.201_controller.pp.log

I am not able to see why the rabbitmq-server can't start. I think my issue maybe related to the fact that I am using my wireless port as the primary interface to setup RDO. But I may be wrong.

Here is the log in more detail. Please help:

Jun 10 02:12:44 tryopenstack.xyz.com systemd[1]: Starting RabbitMQ broker...
Jun 10 02:12:44 tryopenstack.xyz.com rabbitmq-server[6235]: ERROR: epmd error for host tryopenstack: address (cannot connect to host/port)
Jun 10 02:12:44 tryopenstack.xyz.com systemd[1]: rabbitmq-server.service: main process exited, code=exited, status=1/FAILURE
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: Stopping and halting node rabbit@tryopenstack ...
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: Error: unable to connect to node rabbit@tryopenstack: nodedown
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: DIAGNOSTICS
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: ===========
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: attempted to contact: [rabbit@tryopenstack]
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: rabbit@tryopenstack:
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: * unable to connect to epmd (port 4369) on tryopenstack: address (cannot connect to host/port)
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: current node details:
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: - node name: 'rabbitmq-cli-04@tryopenstack'
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: - home dir: /var/lib/rabbitmq
Jun 10 02:12:45 tryopenstack.xyz.com rabbitmqctl[6336]: - cookie hash: lfdPDB0qOFq1ConYdHDj+w==
Jun 10 02:12:45 tryopenstack.xyz.com systemd[1]: Failed to start RabbitMQ broker.
Jun 10 02:12:45 tryopenstack.xyz.com systemd[1]: Unit rabbitmq-server.service entered failed state.
Jun 10 02:12:45 tryopenstack.xyz.com systemd[1]: rabbitmq-server.service failed.
^[[0m
^[[mNotice: /Stage[main]/Rabbitmq/Anchor[rabbitmq::end]: Dependency Service[rabbitmq-server] has failures: true^[[0m
^[[1;33mWarning: /Stage[main]/Rabbitmq/Anchor[rabbitmq::end]: Skipping because of failed dependencies^[[0m
@                                                                                                                                             
^[[0m
^[[mNotice: /Stage[main]/Rabbitmq/Anchor[rabbitmq::end]: Dependency Service[rabbitmq-server] has failures: true^[[0m
^[[1;33mWarning: /Stage[main]/Rabbitmq/Anchor[rabbitmq::end]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Glance::Api::Authtoken/Keystone::Resource::Authtoken[glance_api_config]/Glance_api_config[keystone_authtoken/password]/value: value changed '[old secret redacted]' to '[new secret redacted]'^[[0m
^[[mNotice: /Stage[main]/Glance::Api::Db/Oslo::Db[glance_api_config]/Glance_api_config[database/connection]/value: value changed '[old secret redacted]' to '[new secret redacted]'^[[0m
^[[1;31mError: Systemd start for rabbitmq-server failed!
journalctl log for rabbitmq-server:
-- Logs begin at Sat 2017-06-10 02:02:16 EDT, end at Sat 2017-06-10 02:12:45 EDT. --
Jun 10 02:12:44 tryopenstack.xyz.com systemd[1]: Starting RabbitMQ broker...
Jun 10 02 ...
(more)
edit retag flag offensive close merge delete

Comments

Recently I had this precise problem because the IP address of my all-in-one server was different from the value in /etc/host. Generally: Try to access the epmd port, for example with nc tryopenstack 4369. If you can't connect, find out why.

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-10 02:16:27 -0500 )edit

nc tryopenstack 4369 says "Connection refused". Also, my /etc/host file's IP and hostname are accurate.

zetret12 gravatar imagezetret12 ( 2017-06-17 19:29:02 -0500 )edit

Well, your problem is that epmd can't be reached. You have to find out why. Perhaps there is a firewall? Or epmd isn't running?

Bernd Bausch gravatar imageBernd Bausch ( 2017-06-18 02:36:36 -0500 )edit