Ask Your Question
1

Unable to start nova-conductor

asked 2017-01-18 14:25:49 -0500

egaona gravatar image

updated 2017-01-18 17:46:48 -0500

Hi,

I'm running into an issue starting the nova-conductor after install and configuration of the controller node. Because of nova-conductor being down, this affects openstack-nova-compute.service not able to start as well. I'm seeing in the nova-conductor.log the error messages, "ERROR oslo_service.service AccessRefused: (0, 0): (403) ACCESS_REFUSED - Login was refused using authentication mechanism AMQPLAIN. For details see the broker logfile". Has anyone seen this before and how do I fix this? Thanks in advance!

Output from nova-conductor.log:

2017-01-18 15:18:06.413 25139 ERROR oslo_service.service
2017-01-18 15:18:07.147 11081 INFO oslo_service.service [req-b39952e9-10b5-4ec5-add3-aa71111de907 - - - - -] Child 25135 exited with status 1
2017-01-18 15:18:07.149 11081 INFO oslo_service.service [req-b39952e9-10b5-4ec5-add3-aa71111de907 - - - - -] Forking too fast, sleeping
2017-01-18 15:18:07.152 25141 INFO nova.service [-] Starting conductor node (version 14.0.2-1.el7)
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service [req-e0dd9fcb-d06d-4862-a91f-1a1e3ffb5a5c - - - - -] Error starting thread.
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service Traceback (most recent call last):
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_service/service.py", line 708, in run_service
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     service.start()
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/nova/service.py", line 153, in start
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     self.rpcserver.start()
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/server.py", line 268, in wrapper
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     log_after, timeout_timer)
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/server.py", line 188, in run_once
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     post_fn = fn()
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/server.py", line 267, in <lambda>
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     states[state].run_once(lambda: fn(self, *args, **kwargs),
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/server.py", line 420, in start
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     self.listener = self._create_listener()
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 121, in _create_listener
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     return self.transport._listen(self._target, 1, None)
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 112, in _listen
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     batch_timeout)
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 471, in listen
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service     conn = self._get_connection(rpc_common.PURPOSE_LISTEN)
2017-01-18 15:18:07.420 25141 ERROR oslo_service.service   File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py ...
(more)
edit retag flag offensive close merge delete

3 answers

Sort by ยป oldest newest most voted
0

answered 2017-01-18 17:50:27 -0500

Login was refused using authentication mechanism AMQPLAIN indicates that you didn't configure message queue credentials correctly. The installation guides show you how it's done.

edit flag offensive delete link more
0

answered 2017-01-19 11:14:52 -0500

egaona gravatar image

Bernd, thanks for formatting my post and for your suggestion. I finally figured out why nova-conductor wasn't starting. I had transport_url=rabbit://openstack:password@controller without a space before and after the equal sign, but once I changed it to transport_url = rabbit://openstack:password@controller the conductor came up.

edit flag offensive delete link more
0

answered 2018-10-01 04:25:17 -0500

novainfinite gravatar image

updated 2018-10-01 04:25:50 -0500

biuld rabbitmq user rabbitmqctl list_users should show openstack user

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-01-18 14:25:49 -0500

Seen: 3,825 times

Last updated: Oct 01 '18