Looks like a networking issue. First stab is to telnet to the port on the host and see if it’s accessible: > telnet localhost 5672 If not, then your issue is not OpenStack specific. — See my availability here: https://www.google.com/calendar/embed?src=parrott@g.harvard.edu&mode=week Robert E. Parrott, Ph.D. Senior Architect Office of the CTO: Innovation and Architecture Harvard University On February 13, 2014 at 7:21:11 PM, Raphael Ribeiro (raphaelpr01 at gmail.com) wrote: > > These are the errors: > > *nova-cert.log* > http://pastebin.ca/2640116 > > *nova-conductor.log* > http://pastebin.ca/2640117 > > > *nova.conf* > > rpc_backend = nova.rpc.impl_kombu > rabbit_host = controller > rabbit_password = rabbit > rabbit_port=5672 > > > *nova manage service-list* > > Binary Host Zone > Status State Updated_At > nova-conductor controller internal > enabled XXX None > nova-consoleauth controller internal > enabled XXX None > nova-scheduler controller internal > enabled XXX None > nova-cert controller internal > enabled XXX None > > *uname -a* > > Linux controller 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 > GNU/Linux > > > Could anyone help me? > > Thanks! > > > Raphael P. Ribeiro > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >