neutron

IOError: Socket closed

Asked by Klaudia

Hi,
imstances couldnt spawn.
I get log:

root@grizzly-controller:~# tail /var/log/nova/nova-scheduler.log
2013-05-20 14:39:12.476 1487 TRACE nova.openstack.common.rpc.common File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py", line 202, in _wait_method
2013-05-20 14:39:12.476 1487 TRACE nova.openstack.common.rpc.common self.method_reader.read_method()
2013-05-20 14:39:12.476 1487 TRACE nova.openstack.common.rpc.common File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/method_framing.py", line 221, in read_method
2013-05-20 14:39:12.476 1487 TRACE nova.openstack.common.rpc.common raise m
2013-05-20 14:39:12.476 1487 TRACE nova.openstack.common.rpc.common IOError: Socket closed
2013-05-20 14:39:12.476 1487 TRACE nova.openstack.common.rpc.common
2013-05-20 14:39:12.479 INFO nova.openstack.common.rpc.common [req-e0bd58e8-66db-4275-b38a-7f6c35adf388 e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] Reconnecting to AMQP server on localhost:5672
2013-05-20 14:39:12.483 INFO nova.openstack.common.rpc.common [req-e0bd58e8-66db-4275-b38a-7f6c35adf388 e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] Connected to AMQP server on localhost:5672
2013-05-20 14:39:55.527 ERROR nova.scheduler.filter_scheduler [req-e0bd58e8-66db-4275-b38a-7f6c35adf388 e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] [instance: 3ac23666-d5c4-43e6-854a-d867ef0d922a] Error from last host: grizzly-compute (node grizzly-compute): [u'Traceback (most recent call last):\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 834, in _run_instance\n set_access_ip=set_access_ip)\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1093, in _spawn\n LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u' File "/usr/lib/python2.7/contextlib.py", line 24, in __exit__\n self.gen.next()\n', u' File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1089, in _spawn\n block_device_info)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 1520, in spawn\n block_device_info)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2435, in _create_domain_and_network\n domain = self._create_domain(xml, instance=instance)\n', u' File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2396, in _create_domain\n domain.createWithFlags(launch_flags)\n', u' File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 187, in doit\n result = proxy_call(self._autowrap, f, *args, **kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 147, in proxy_call\n rv = execute(f,*args,**kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/eventlet/tpool.py", line 76, in tworker\n rv = meth(*args,**kwargs)\n', u' File "/usr/lib/python2.7/dist-packages/libvirt.py", line 711, in createWithFlags\n if ret == -1: raise libvirtError (\'virDomainCreateWithFlags() failed\', dom=self)\n', u"libvirtError: Cannot get interface MTU on 'br-int': No such device\n"]
2013-05-20 14:39:55.539 WARNING nova.scheduler.driver [req-e0bd58e8-66db-4275-b38a-7f6c35adf388 e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] [instance: 3ac23666-d5c4-43e6-854a-d867ef0d922a] Setting instance to ERROR state.

Does anybody have idea what can be the reason?

Question information

Language:
English Edit question
Status:
Solved
For:
neutron Edit question
Assignee:
No assignee Edit question
Solved by:
Klaudia
Solved:
Last query:
Last reply:
Revision history for this message
Aaron Rosen (arosen) said : 		#1

The issue is the nova-compute node that this vm is trying to start on does not have a br-int.

See: u"libvirtError: Cannot get interface MTU on 'br-int': No such device\

Revision history for this message
yong sheng gong (gongysh) said : 		#2

try to run 'sudo ovs-vsctrl add-br br-int' first

Revision history for this message
Klaudia (graklaudia) said : 		#3

Ok, thank you. But I understand that i have to add this bridge on compute node? or where? (compute, ntwork, controller)
I added.
I have br-int on compute and I have br-int on network node.
But Vm also dont work. I get Error state. :(

This time log is shorter:

2013-05-21 18:15:13.701 WARNING nova.scheduler.driver [req-00a6241f-305c-40c9-9508-0b766cf24df6 e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] [instance: acfba861-f199-40be-b8fd-c217028f75fa] Setting instance to ERROR state.

well.. what to do?

Revision history for this message
Aaron Rosen (arosen) said : 		#4

You'll need to provide us the nova-compute log for us to help. That's where the relivent error message is.

Revision history for this message
Klaudia (graklaudia) said : 		#5

Ok, this is log from compute node from /var/log/nova/nova-compute.log file:

root@ubuntu:~# tail /var/log/nova/nova-compute.log
2013-05-22 10:51:46 TRACE nova.rpc.common File "/usr/lib/python2.7/dist-packages/kombu/transport/pyamqplib.py", line 52, in __init__
2013-05-22 10:51:46 TRACE nova.rpc.common super(Connection, self).__init__(*args, **kwargs)
2013-05-22 10:51:46 TRACE nova.rpc.common File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/connection.py", line 129, in __init__
2013-05-22 10:51:46 TRACE nova.rpc.common self.transport = create_transport(host, connect_timeout, ssl)
2013-05-22 10:51:46 TRACE nova.rpc.common File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py", line 281, in create_transport
2013-05-22 10:51:46 TRACE nova.rpc.common return TCPTransport(host, connect_timeout)
2013-05-22 10:51:46 TRACE nova.rpc.common File "/usr/lib/python2.7/dist-packages/amqplib/client_0_8/transport.py", line 85, in __init__
2013-05-22 10:51:46 TRACE nova.rpc.common raise socket.error, msg
2013-05-22 10:51:46 TRACE nova.rpc.common error: [Errno 111] ECONNREFUSED
2013-05-22 10:51:46 TRACE nova.rpc.common

Revision history for this message
Klaudia (graklaudia) said : 		#6

logs from nova-api:
root@grizzly-controller:~# tail /var/log/nova/nova-api.log
2013-05-22 19:01:22.640 INFO nova.osapi_compute.wsgi.server [req-4c2a95de-90fb-4663-8531-1391195b0b1e e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] 127.0.0.1 "GET /v2/017d9ac43fb943dcbac74f65255fcd8c/limits?reserved=1 HTTP/1.1" status: 200 len: 1468 time: 0.0056210

2013-05-22 19:01:22.965 24005 INFO nova.osapi_compute.wsgi.server [-] (24005) accepted ('127.0.0.1', 46388)

2013-05-22 19:01:23.262 INFO nova.osapi_compute.wsgi.server [req-618fda69-91ff-4287-b6bd-19320a41cc5b e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] 127.0.0.1 "GET /v2/017d9ac43fb943dcbac74f65255fcd8c/servers/df8039ce-3c50-4979-9b2f-9c470f56ff88 HTTP/1.1" status: 200 len: 1409 time: 0.2961049

2013-05-22 19:01:23.265 24005 INFO nova.osapi_compute.wsgi.server [-] (24005) accepted ('127.0.0.1', 46392)

2013-05-22 19:01:23.279 INFO nova.osapi_compute.wsgi.server [req-fabd82fd-c2b3-431e-a6f7-5cf1663a61ee e693f348f6a74c5ea6f4898b428f10fe 017d9ac43fb943dcbac74f65255fcd8c] 127.0.0.1 "GET /v2/017d9ac43fb943dcbac74f65255fcd8c/flavors/1 HTTP/1.1" status: 200 len: 589 time: 0.0137811

Revision history for this message
Klaudia (graklaudia) said : 		#7

Any hint?

Revision history for this message
Aaron Rosen (arosen) said : 		#8

2013-05-22 10:51:46 TRACE nova.rpc.common error: [Errno 111] ECONNREFUSED

means that the quantum-server can't connect to the message bus.

Revision history for this message
Klaudia (graklaudia) said : 		#9

Ok. Thank you.
And if quantum server can't connect to the message bus, what shoul I check / what shuld I do , to change it and make possible for quantum-server to connect to the message bus?

Revision history for this message
Aaron Rosen (arosen) said : 		#10

/etc/quantum/quantum.conf:
rabbit_host = localhost

Revision history for this message
Klaudia (graklaudia) said : 		#11

i have rabbit_host = 10.10.10.10

10.10.10.10 is controller ip

Someting else... is wrong, any ideas?

Revision history for this message
Aaron Rosen (arosen) said : 		#12

What's the output to telnet 10.10.10.10 5672

Revision history for this message
Klaudia (graklaudia) said : 		#13

Ok, I manage to solve this problem. thank you all

Revision history for this message
Naresh Bishnoi (naresh-bishnoi) said : 		#14

what was the issues? was it some config issue?

T
N