← Back to team overview

openstack team mailing list archive

Re: nova-consoleauth timeout

 

I did more digging and found the following:

2013-05-15 13:56:25.881 AUDIT nova.consoleauth.manager
[req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] Checking Token:
2a276401-9cfd-4dee-a811-3ab9460b76dc, True)
2013-05-15 13:56:25.882 DEBUG nova.openstack.common.rpc.amqp
[req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] Making synchronous
call on conductor ... multicall
/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:583
2013-05-15 13:56:25.883 DEBUG nova.openstack.common.rpc.amqp
[req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] MSG_ID is
c8aea2d693cb4a1c8ac897226ec7c119 multicall
/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:586
2013-05-15 13:56:25.883 DEBUG nova.openstack.common.rpc.amqp
[req-71725790-fe8d-4919-87aa-d5e0ce9870a7 None None] UNIQUE_ID is
a29fff1d3f79418e94320e0c19d86a1b. _add_unique_id
/usr/lib/python2.6/site-packages/nova/openstack/common/rpc/amqp.py:337

It seems like consoleauth is still trying to connect via amqp to a
"conductor" topic?

I already have in my config,
[conductor]
use_local = True
so why is consoleauth still trying to connect to "conductor"?

By the way, I started conductor and the console works. Does that mean that
consoleauth relies on conductor?

Can anyone shed some light on this?

- WP


On Tue, May 14, 2013 at 6:29 PM, YIP Wai Peng <yipwp@xxxxxxxxxxxxxxx> wrote:

> Hi,
>
> I am having some problems with starting a novnc console. When I try to
> connect on the URL generated by "nova get-vnc-console", it is stuck with a
> "Starting VNC handshake" message. After a while, it will show "Failed to
> connect to server (code: 1006)". I am using nova-consoleauth with qpid.
>
> Digging deeper, in consoleauth.log it shows
>
> 2013-05-14 18:24:05.135 AUDIT nova.consoleauth.manager
> [req-0ffce0d5-bb14-4430-b73a-f68090502b6f None None] Checking Token:
> a70eab92-33e3-45b6-9132-ada441933ef7, True)
> 2013-05-14 18:25:05.162 ERROR nova.openstack.common.rpc.amqp
> [req-0ffce0d5-bb14-4430-b73a-f68090502b6f None None] Exception during
> message handling
> <snip>
> 2013-05-14 18:25:05.162 13764 TRACE nova.openstack.common.rpc.amqp
> Timeout: Timeout while waiting on RPC response.
>
> When I debug qpid, it shows the following
>
> 2013-05-14 18:14:27 debug No messages available to dispatch to consumer
> anonymous.891183d7-f7d8-4dd9-9499-103623fca15e:0::0 on queue 'consoleauth'
> 2013-05-14 18:14:27 debug Exception constructed: Exchange not found:
> 191c1daec221467fb6e9aa07979f5205 (qpid/broker/ExchangeRegistry.cpp:97)
>
>
> Can anybody help point me to the source of this error or where to look
> further? Help will be much appreciated.
>
> Regards,
> Wai Peng
>

References