Open Stack

On Tue, Jul 24, 2012 at 11:12 AM, Thomas Vachon <vachon at sessionm.com> wrote:

> 2012-07-24 11:05:37 ERROR nova.rpc.common
> [req-cbc137cd-99e5-46b9-968d-4d8ab7b6bf59
> 67e970e4b28b4346a077b25d4ab281f6 c61a1d9367254fcea905df473cc5af18]
> Timed out waiting for RPC response: timed out
> 2012-07-24 11:05:37 TRACE nova.rpc.common Traceback (most recent call last):
> 2012-07-24 11:05:37 TRACE nova.rpc.common   File
> "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 490,
> in ensure
> 2012-07-24 11:05:37 TRACE nova.rpc.common     return method(*args, **kwargs)
> 2012-07-24 11:05:37 TRACE nova.rpc.common   File
> "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 567,
> in _consume
> 2012-07-24 11:05:37 TRACE nova.rpc.common     return
> self.connection.drain_events(timeout=timeout)
> 2012-07-24 11:05:37 TRACE nova.rpc.common   File
> "/usr/lib/python2.7/dist-packages/kombu/connection.py", line 175, in
> drain_events

<snip>

This looks like a rabbitmq problem. We've been having a lot of trouble
with rabbitmq stability on precise lately. I haven't run it down to
root cause, but you might try restarting it.
 -nld