I think more than that, conductor may not be running. If you look at the original error messages, we can see that it's able to connect to the rabbit server:
2015-07-08 01:21:20.501 49721 INFO oslo.messaging._drivers.impl_rabbit [req-6f67f40a-53cc-4c95-a431-f98ab296c0c5 ] Connecting to AMQP server on controller.example.com:5672 <http://controller.example.com:5672/> 2015-07-08 01:21:20.516 49721 INFO oslo.messaging._drivers.impl_rabbit [req-6f67f40a-53cc-4c95-a431-f98ab296c0c5 ] Connected to AMQP server oncontroller.example.com:5672 <http://controller.example.com:5672/> But then it times out waiting for conductor. 2015-07-08 01:21:30.538 49721 WARNING nova.conductor.api [req-6f67f40a-53cc-4c95-a431-f98ab296c0c5 None] Timed out waiting for nova-conductor. Is it running? Or did this service start before nova-conductor? Reattempting establishment of nova-conductor connection... I'd look on your controller node and make sure the nova-conductor service is running, and also make sure *it* is able to connect to the message bus. On 7/8/15, 8:07 AM, "MailingLists - EWS" <mailingli...@expresswebsystems.com> wrote: >Anwar, > >It looks like your RabbitMQ isn¹t running or isn¹t reachable. > >There were some issues that we ran into when doing this. Make sure >RabbitMQ is running. Double check your IPtables rules to make sure the >ports are open. I > also seem to recall some problem with a certain version of RabbitMQ that >was installed that was just broken and we had to roll back to a previous >version but that was several months ago and my recollection is a bit hazy >as to the details. > >Tom Walsh >Express Web Systems, Inc. > > > > > _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators