Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

nova-manage service list status XXX

  1. I am having havana multi node setup. when i am doing nova-manage service list I amm getting output like below

Binary Host Zone Status State Updated_At nova-cert controller internal enabled XXX 2014-11-18 07:09:40 nova-conductor controller internal enabled XXX 2014-11-18 07:09:39 nova-consoleauth controller internal enabled XXX 2014-11-18 07:09:40 nova-scheduler controller internal enabled XXX 2014-11-18 07:09:40 nova-compute compute nova enabled XXX 2014-11-18 07:09:38

  1. I have checked logs file /var/logs/neutrons

2014-11-18 16:35:11.536 17258 ERROR neutron.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 30 seconds. 2014-11-18 16:35:44.567 17258 ERROR neutron.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 30 seconds. 2014-11-18 16:36:17.579 17258 ERROR neutron.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 30 seconds. 2014-11-18 16:36:50.607 17258 ERROR neutron.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 30 seconds. 2014-11-18 16:37:23.644 17258 ERROR neutron.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 30 seconds. 2014-11-18 16:37:56.660 17258 ERROR neutron.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: Socket closed. Trying again in 30 seconds. 2014-11-18 16:38:29.697 17258 ERROR neutron.openstack.common.rpc.common [-] AMQP server on localhost:5672 iGs unreachable: Socket closed. Trying again in 30 seconds. -- INSERT --

  1. I am not able to login into dashboard.

This is the error message what I am getting

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log. Apache/2.2.22 (Ubuntu) Server at 192.168.1.5 Port 80

BEFORE CONTROLLER'S IP IS 192.168.1.13 NOW CHANGED TO 192.168.1.5