Ask Your Question
0

Networking issues: Errno 113 EHOSTUNREACH

asked 2014-06-16 11:53:06 -0500

bcumber12 gravatar image

updated 2014-06-16 18:21:19 -0500

Hello everyone,

I've set up openstack on 3 virtual machines running CentOS by following this guide http://docs.openstack.org/icehouse/install-guide/install/yum/content/basics-queue.html (http://docs.openstack.org/icehouse/in...) . I currently have keystone, glance, nova, and neutron installed on the necessary nodes. Currently the services running on the network and compute nodes are filling their logs with

(From /var/log/nova/compute.log on the compute node)

2014-06-16 09:17:28.105 2309 ERROR oslo.messaging._drivers.impl_qpid [-] Unable to connect to AMQP server: [Errno 113] EHOSTUNREACH. Sleeping 5 seconds

(From /var/log/neutron/openvswitch-agent.log on the network node. The message is the same in the other neutron logs as well)

2014-06-16 09:20:52.311 2108 ERROR neutron.openstack.common.rpc.impl_qpid [req-4cc745ab-ee17-4a61-aed8-b2abc83d60d9 None] Unable to connect to AMQP server: [Errno 113] EHOSTUNREACH. Sleeping 5 seconds

When I try to execute a nova command on the compute node I get:

[root@compute1 compute1-node]# nova list
ERROR: [Errno 113] No route to host

and on the network node with neutron:

[root@network network-node]# neutron net-list
Connection to neutron failed:

I have checked to ensure the AMQP service is running on the controller node

[root@controller controller-node]# service qpidd status
qpidd (pid  3566) is running...

Qpid authentication is disabled in the qpidd.conf file and the values relating to qpid in the neutron.conf and nova.conf on their respective nodes are set to the specified values in the guide:

(from nova.conf)

rpc_backend = qpid
qpid_hostname = controller

(from neutron.conf)

rpc_backend = neutron.openstack.common.rpc.impl_qpid
qpid_hostname = controller

I don't think there is a problem resolving "controller" because I can ping controller from both nodes with no problem.

[root@network network-node]# ping -c 4 controller
PING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.229 ms
64 bytes from controller (10.0.0.11): icmp_seq=2 ttl=64 time=0.394 ms
64 bytes from controller (10.0.0.11): icmp_seq=3 ttl=64 time=0.261 ms
64 bytes from controller (10.0.0.11): icmp_seq=4 ttl=64 time=0.264 ms

--- controller ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 0.229/0.287/0.394/0.063 ms

[root@compute1 compute1-node]# ping -c 4 controller
PING controller (10.0.0.11) 56(84) bytes of data.
64 bytes from controller (10.0.0.11): icmp_seq=1 ttl=64 time=0.733 ms
64 bytes from controller (10.0.0.11): icmp_seq=2 ttl=64 time=0.271 ms
64 bytes from controller (10.0.0.11): icmp_seq=3 ttl=64 time=0.291 ms
64 bytes from controller (10.0.0.11): icmp_seq=4 ttl=64 time=0.221 ms

--- controller ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.221/0.379/0.733/0 ...
(more)
edit retag flag offensive close merge delete

Comments

Could anyone who has implemented openstack on CentOS in a three node architecture at least post their iptables as an example? That may help me debug the problem. I'd be very grateful.

bcumber12 gravatar imagebcumber12 ( 2014-06-17 10:23:19 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2014-08-29 09:26:30 -0500

Disable iptables, or open the ports on the controller node.

edit flag offensive delete link more

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

1 follower

Stats

Asked: 2014-06-16 11:53:06 -0500

Seen: 7,144 times

Last updated: Jun 16 '14