Openstack services cannot talk to RabbitMQ: Connection refused but log says unreachable?
I've got single-node Openstack Folsom deployment on a Debian 7.1 server. I've followed the Folsom guide so far and have got everything set up, but when I try to log in through the dashboard, I get the following message:
ConnectionError at /admin/
[Errno 111] Connection refused
Request Method: GET
Request URL: https://172.23.18.174/admin/
Django Version: 1.4.5
Exception Type: ConnectionError
Exception Value:
[Errno 111] Connection refused
Exception Location: /usr/lib/python2.7/dist-packages/requests/adapters.py in send, line 243
Python Executable: /usr/bin/python
Python Version: 2.7.3
Python Path:
['/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../..',
'/usr/lib/python2.7',
'/usr/lib/python2.7/plat-linux2',
'/usr/lib/python2.7/lib-tk',
'/usr/lib/python2.7/lib-old',
'/usr/lib/python2.7/lib-dynload',
'/usr/local/lib/python2.7/dist-packages',
'/usr/lib/python2.7/dist-packages',
'/usr/lib/pymodules/python2.7',
'/usr/share/openstack-dashboard/',
'/usr/share/openstack-dashboard/openstack_dashboard']
Server time: Fri, 12 Jul 2013 16:04:49 +0000
Now I've researched this issue somewhat and have found that connection refused stems from a misconfigured quantum.conf. So I double checked, and my quantum.conf is the following (relevant settings only):
# Address to bind the API server
bind_host = 0.0.0.0
# Port the (sic) bind the API server to
bind_port = 9696
...
# IP address of the RabbitMQ server
rabbit_password = password
# Port where RabbitMQ server is running/listening
rabbit_port = 5672
...
# User ID used for RabbitMQ connections
rabbit_userid = guest
... (everything else is unchanged)
So the login credentials should be OK (nova.conf credentials match too). Other credentials are, of course, sourced upon login.
However, my quantum-server.log shows the following:
2013-07-12 12:00:42 ERROR [quantum.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 29 seconds.
Anyone know what exactly is going on here? One thing that I noticed was that I lack a /etc/rabbitmq/rabbitmq.conf file, although I saw it mentioned somewhere. Might this have anything to do with this?
Upon further inspection, it would seem that the nova services I have installed so far cannot talk to RabbitMQ at all (as nova-scheduler, nova-consoleauth, nova-cert and nova-conductor all show XXX as their state), as I've found the same error message from quantum logs in the nova-cert.log:
2013-07-12 12:26:47.526 ERROR nova.openstack.common.rpc.common [req-705a947d-28b8-4c1e-8475-2afb19ad96a6 None None] AMQP server on 172.23.18.174:5672 is unreachable: Socket closed. Trying again in 30 seconds.
It should be noted that the machine running all these services is 172.23.18.174. However, I've tried setting both IPs in quantum.conf and nova.conf to either one or the other, but this did not alleviate the issue. Anyone know what is going on here?
what does 'netstat -an | grep 5672' give?
@filpano have you found an answer to this question?