Contrail Platform Developers
Highlighted
Contrail Platform Developers

Problems installing Contrail

[ Edited ]
‎04-03-2014 05:40 AM

Dear people,

 

I've problems installing Contrail direclty from the provided ISO's as part of my learning to work with Contrail and Openstack.

 

This a error log I get on all of the Nova/Cinder etc etc services:

 

Nova/scheduler.log

2014-04-03 14:26:02.954 2497 ERROR nova.openstack.common.rpc.common [-] Failed to consume message from queue: [Errno 104] Connection reset by peer
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common Traceback (most recent call last):
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/impl_kombu.py", line 563, in ensure
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     return method(*args, **kwargs)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/impl_kombu.py", line 643, in _consume
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     return self.connection.drain_events(timeout=timeout)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/kombu/connection.py", line 139, in drain_events
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     return self.transport.drain_events(self.connection, **kwargs)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/kombu/transport/pyamqplib.py", line 223, in drain_events
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     return connection.drain_events(**kwargs)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/kombu/transport/pyamqplib.py", line 56, in drain_events
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     return self.wait_multi(self.channels.values(), timeout=timeout)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/kombu/transport/pyamqplib.py", line 81, in wait_multi
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     return amqp_method(channel, args)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/amqplib/client_0_8/connection.py", line 378, in _close
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     self._x_close_ok()
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/amqplib/client_0_8/connection.py", line 397, in _x_close_ok
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     self._send_method((10, 61))
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/amqplib/client_0_8/abstract_channel.py", line 76, in _send_method
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     method_sig, args, content)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/amqplib/client_0_8/method_framing.py", line 252, in write_method
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     self.dest.write_frame(1, channel, payload)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/amqplib/client_0_8/transport.py", line 165, in write_frame
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     frame_type, channel, size, payload, 0xce))
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/eventlet/greenio.py", line 283, in sendall
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     tail = self.send(data, flags)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common   File "/usr/lib/python2.6/site-packages/eventlet/greenio.py", line 269, in send
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common     total_sent += fd.send(data[total_sent:], flags)
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common error: [Errno 104] Connection reset by peer
2014-04-03 14:26:02.954 2497 TRACE nova.openstack.common.rpc.common 
2014-04-03 14:26:03.030 2497 ERROR nova.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 1 seconds.
2014-04-03 14:26:04.032 2497 ERROR nova.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 3 seconds.
2014-04-03 14:26:07.034 2497 ERROR nova.openstack.common.rpc.common [-] AMQP server on localhost:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in 5 seconds.

 Cinder/scheduler.log

 

2014-04-03 14:24:27    ERROR [cinder.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: client: 0-10, server: 9-1. Sleeping 60 seconds
2014-04-03 14:25:27    ERROR [cinder.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: client: 0-10, server: 9-1. Sleeping 60 seconds
2014-04-03 14:26:27    ERROR [cinder.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: client: 0-10, server: 9-1. Sleeping 60 seconds
2014-04-03 14:27:27    ERROR [cinder.openstack.common.rpc.impl_qpid] Unable to connect to AMQP server: client: 0-10, server: 9-1. Sleeping 60 seconds

 

It seems that there is a problem with the AMQP server. In version 1.03 the used QPID-services was qpidd. and since today I tried 1.04 which has RabbitMQ as a amqp-broker.

 

I can telnet port 5672 on all of the server nodes. so the port is in use and is open for every node.

The RabbitMQ is running now with version 1.04.

 

I followed every step in the " Control getting started guide" but I don't know what i missed.

2 REPLIES 2
Highlighted
Contrail Platform Developers

Re: Problems installing Contrail

‎04-23-2014 10:44 AM

Hi,

Is this a single-node installation ? 

 

Can you check /etc/nova/nova.conf to see the value of rpc_backend ..Can you comment it out and restart nova scheduler and see what happens ? 

 

In /etc/cinder/cinder.conf, can you comment out rpc_backend (so that it uses default rabbitmq)  and restart cinder-api and cinder-scheduler.

Currently it seems to be set to qpid

 

Vedu

Highlighted
Contrail Platform Developers

Re: Problems installing Contrail

[ Edited ]
‎05-01-2014 02:22 AM

It seems that my problem is fixed with your suggestions.

 

I added this to the Cinder.conf:

 

#logdirabbitMQ broker address where a single node is used. (string value)
rabbit_host=localhost

# The RabbitMQ broker port where a single node is used. (integer value)
rabbit_port=5672

# RabbitMQ HA cluster host:port pairs. (list value)
#rabbit_hosts=$rabbit_host:$rabbit_port

# Connect over SSL for RabbitMQ. (boolean value)
#rabbit_use_ssl=false

# The RabbitMQ userid. (string value)
rabbit_userid=guest

# The RabbitMQ password. (string value)
rabbit_password=guest

# the RabbitMQ login method (string value)
#rabbit_login_method=AMQPLAIN

# The RabbitMQ virtual host. (string value)
rabbit_virtual_host=/

# How frequently to retry connecting with RabbitMQ. (integer value)
#rabbit_retry_interval=1

# How long to backoff for between retries when connecting to RabbitMQ. (integer value)
#rabbit_retry_backoff=2

# Maximum number of RabbitMQ connection retries. Default is 0 (infinite retry count). (integer value)
#rabbit_max_retries=0

# Use HA queues in RabbitMQ (x-ha-policy: all). If you change this option, you must wipe the RabbitMQ database. (boolean value)
#rabbit_ha_queues=false

# If passed, use a fake RabbitMQ provider. (boolean value)
#fake_rabbit=false

#rpc_backend = cinder.openstack.common.rpc.impl_qpid

rpc_backend = cinder.openstack.common.rpc.impl_kombu

 I also did thesame for nova. And I don't get any error messages anymore.

 

But for some reason I also don't get a  "Connected" log entry. is it true that Nova or Cinder does not report a connected state? I rembered that I once read it somewhere that there should be some sort of "Connected to...." log entry.

Feedback