New Question

FreeRDP Webconnect and Openstack Train

asked 2020-02-03 16:39:05 +0300

hbonath gravatar image

Hello - I have upgraded from Stein to Train and am now running into an issue when attempting to connect to the console of any of my VMs. From the Horizon dashboard, I simply get the spinning wheel seemingly forever.

If I attempt to get the console URL via the openstack CLI, It times out with a 504 error, which I believe is being served by HAProxy in my case.

I believe I have tracked the issue to RabbitMQ - as I get in the RabbitMQ logs the following over and over until the 504 occurs:

[error] <0.4650.12> Channel error on connection <0.30933.11> ( ->, vhost: '/nova', user: 'nova'), channel 1:operation basic.publish caused a channel exception not_found: no exchange 'reply_7d8954179ba64f9795ba80aaae2bd5d9' in vhost '/nova'

I am curious if this is something I should troubleshoot further from a FreeRDP/Cloudbase perspective, or if this is an issue with my RabbitMQ configuration.

Any tips would be appreciated!

edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted

answered 2020-02-08 08:23:03 +0300

hbonath gravatar image

Fixed by upgrading my Hyper-V agent to the Stein 19.0.3 agent as I had been using the Rocky 18.0.3 agent up until this point.

edit flag offensive delete link more

answered 2020-02-03 17:04:59 +0300

lpetrut gravatar image


I suggest enabling debug logging and follow the request id. You should be able to see the following in your nova compute log:

For what is worth, there is one bug to keep an eye on, although I don't think that's the case here since you can't even get the rdp connection url:

By the way, is "" your Hyper-V host by any chance?

Regards, Lucian Petrut

edit flag offensive delete link more


Thanks for the suggestion. When you suggested enabling debug logging, to clarify - are you asking about the API log on the controller nodes, or on the Hyper-V agent itself? I enabled Debug on the Controllers and was not able to see any information as shown in the link. is the Host.

hbonath gravatar imagehbonath ( 2020-02-04 07:07:37 +0300 )edit

I also wanted to add a paste of some of the example outputs from the various logs:

hbonath gravatar imagehbonath ( 2020-02-04 07:09:50 +0300 )edit

It's useful to have both API and hypervisor side logs so that we can correlate them. I'd be interested to see when the request was issued, when the timeout occurred and what happened on the compute node side in the meantime.

lpetrut gravatar imagelpetrut ( 2020-02-04 09:31:16 +0300 )edit

I did some more testing on this, and ultimately figured out that the issue was probably because I had been using the Rocky 18.0.3 Agent - upgrading to the Stein 19.0.3 Hyper-V agent seems to have fixed my issue. Thank you for taking the time to help with this!

hbonath gravatar imagehbonath ( 2020-02-08 08:21:42 +0300 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2020-02-03 16:39:05 +0300

Seen: 383 times

Last updated: Feb 08 '20