Le 14/10/2013 16:57, Mitja Mihelič a écrit :
> Hi!
>
> I am trying to setup noVNC. As I try to open a console I get a red bar
> at the top of the page saying "Server disconnected (code: 1006)".
> I have followed the instructions here:
>
http://www.ovirt.org/Features/noVNC_console (Setup Websocket Proxy on
> the Enging Post Install).
> I have imported the
https://server.example.com/ca.crt into my browser
> (Firefox and Chrome).
>
> The only thing that gets logged to server.log when I try to open the
> noVNC console is:
> 2013-10-14 16:39:51,803 INFO
> [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-3)
> Running command: SetVmTicketCommand internal: false. Entities affected
> : ID: 43efe22e-67c2-4bb2-a089-05dc8770efd6 Type: VM
> 2013-10-14 16:39:51,807 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
> (ajp--127.0.0.1-8702-3) START, SetVmTicketVDSCommand(HostName =
>
server.example.com, HostId = bf21cb8f-9a63-40b9-9f18-4f6fc74f74f1,
> vmId=43efe22e-67c2-4bb2-a089-05dc8770efd6, ticket=aicJH+Rf0F/C,
> validTime=120,m userName=myuser,
> userId=fa4c5381-04d8-11e3-9045-b4f33f63d7d4), log id: 3504f642
> 2013-10-14 16:39:51,848 INFO
> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand]
> (ajp--127.0.0.1-8702-3) FINISH, SetVmTicketVDSCommand, log id: 3504f642
>
> We are running a fresh oVirt 3.3 on CentOS 6.4 with the following
> versions of packages:
> ovirt-engine-3.3.0-4.el6.noarch
> ovirt-engine-backend-3.3.0-4.el6.noarch
> ovirt-engine-cli-3.3.0.4-1.el6.noarch
> ovirt-engine-dbscripts-3.3.0-4.el6.noarch
> ovirt-engine-lib-3.3.0-4.el6.noarch
> ovirt-engine-restapi-3.3.0-4.el6.noarch
> ovirt-engine-sdk-python-3.3.0.6-1.el6.noarch
> ovirt-engine-setup-3.3.0-4.el6.noarch
> ovirt-engine-setup-plugin-allinone-3.3.0-4.el6.noarch
> ovirt-engine-tools-3.3.0-4.el6.noarch
> ovirt-engine-userportal-3.3.0-4.el6.noarch
> ovirt-engine-webadmin-portal-3.3.0-4.el6.noarch
> ovirt-engine-websocket-proxy-3.3.0-4.el6.noarch
> ovirt-host-deploy-1.1.1-1.el6.noarch
> ovirt-host-deploy-java-1.1.1-1.el6.noarch
> ovirt-host-deploy-offline-1.1.1-1.el6.noarch
> ovirt-image-uploader-3.3.0-1.el6.noarch
> ovirt-iso-uploader-3.3.0-1.el6.noarch
> ovirt-log-collector-3.3.0-1.el6.noarch
> ovirt-release-el6-8-1.noarch
> novnc-0.4-2.el6.noarch
>
> Kind regards,
> Mitja
>
Don't know if it could help, but I restarted engine-setup on the
manager and let it manage the websocketproxy settings.
Restarted it, and has to accept the certificate on my browser, and it
worked. (
https://fqdn:port_number)
Thank you Nicolas. After following your advice noVNC console connection
works.
The steps required to make it work still seem a bit confusing for the
users. Go to the fqdn:port, accept certificate, go back to the user
portal, start console.
Regards,
Mitja