Ask Your Question
1

Can't access to VM (already worked fine for 5 months)

asked 2015-01-04 01:16:16 -0500

dwyaneini gravatar image

updated 2015-01-04 03:58:21 -0500

Our OpenStack system has already worked fine at least 5 months. We deploy openstack icehouse version with three-node architecture (controller node, network node, and compute node1) on Debian wheezy.I use ml2 plugin and gre type driver.

I didn''t do any tiny configuration changes. When I attempt to login system through dashboard, it prompts me the following errors.

ConnectionError at /project/
HTTPConnectionPool(host='hostIp', port=8774): Max retries exceeded with url: /v2/554ca2c2830943819cb85ba45e059974/extensions (Caused by <class 'socket.error'>: [Errno 111] Connection refused)
Exception Location: /usr/lib/python2.7/dist-packages/requests/adapters.py in send, line 378

Then through Google and OpenStack Ask, got two useful references: https://ask.openstack.org/en/question... & https://ask.openstack.org/en/question... . I've provided sufficient resources for VM, but found that the nova-api service on Controller Node didn't work. By analyzing the relevant log files and upgrading oslo.rootwrap, I could successfully enter into console by dashboard.

But when I start existing VMs, system prompts "failed to start instance". All Volumes turns to error state. The log of nova-compute service on Compute Node provides some errors:

2015-01-04 14:47:32.461 16753 TRACE nova.compute.manager [instance: 2246dc26-5b9e-4883-be57-aac37c8b5eb9]
2015-01-04 14:47:32.774 16753 ERROR oslo.messaging.rpc.dispatcher [-] Exception during message handling: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-5a36c7ac-780a-4989-8539-161151a07241)
2015-01-04 14:47:32.774 16753 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):
2015-01-04 14:47:32.774 16753 TRACE oslo.messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", 
...
2015-01-04 14:47:32.774 16753 TRACE oslo.messaging.rpc.dispatcher     raise exceptions.from_response(resp, body)
2015-01-04 14:47:32.774 16753 TRACE oslo.messaging.rpc.dispatcher ClientException: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-5a36c7ac-780a-4989-8539-161151a07241)
2015-01-04 14:47:32.774 16753 TRACE oslo.messaging.rpc.dispatcher
2015-01-04 14:47:32.778 16753 ERROR oslo.messaging._drivers.common [-] Returning exception The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-5a36c7ac-780a-4989-8539-161151a07241) to caller
2015-01-04 14:47:32.779 16753 ERROR oslo.messaging._drivers.common [-] ['Traceback (most recent call last):\n', '  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 133, in _dispatch_and_reply\n    incoming.message))\n', '  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 176, in _dispatch\n    return self._do_dispatch(endpoint, method, ctxt, args)\n', '  File "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py", line 122, in _do_dispatch\n    result = getattr(endpoint, method)(ctxt, **new_args)\n', '  File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 393, in decorated_function\n    return function(self, context, *args, **kwargs)\n', '  File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 88, in wrapped\n    payload)\n', '  File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68, in __exit__\n    six.reraise(self.type_, self.value, self ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-01-04 19:23:35 -0500

What is the status of the following:

nova service-list neutron agent-list

If everything looks good there, what happens if you reboot the instance?

edit flag offensive delete link more

Comments

Nova service-list and neutron agent-list both return all services or agents, working fine.

dwyaneini gravatar imagedwyaneini ( 2015-01-04 19:49:28 -0500 )edit

Existing instances mounted with volumes keep "shutoff" status. When I attempt to start instance, it turns to be "Error" status. But When I try to click "Soft Reboot Instances" button, It shows error: "You are not allowed to soft reboot the instance."

dwyaneini gravatar imagedwyaneini ( 2015-01-04 19:50:05 -0500 )edit

What does openstack-service status show on your nodes?

Also, what is ovs-vsctl show showing?

Did you try restarting openvswitch on each node?

schmaustech gravatar imageschmaustech ( 2015-01-04 20:29:28 -0500 )edit

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

2 followers

Stats

Asked: 2015-01-04 01:16:16 -0500

Seen: 277 times

Last updated: Jan 04 '15