can not view console on noVNC display

Bug #1237750 reported by Tomokazu Hirai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned
OpenStack Dashboard (Horizon)
Invalid
Medium
Unassigned

Bug Description

I can not view console on noVNC display.

there is no error at /var/log/nova-consoleauth.log and I can view noVNC display, but display is all gray...
Gray bar includes such message.

    noVNC ready: native WebSockets, canvas rendering

My environments...

* Ubuntu Cloud Archive Packages (rc1)

    # dpkg -l | grep dashboard
    ii openstack-dashboard 1:2013.2~rc1-0ubuntu2~cloud0 django web interface to Openstack
    ii openstack-dashboard-ubuntu-theme 1:2013.2~rc1-0ubuntu2~cloud0 Ubuntu theme for the Openstack dashboard
    # dpkg -l | grep novnc
    ii nova-novncproxy 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - NoVNC proxy
    ii novnc 1:0.4+dfsg+1+20130425+git4973b9cc80-1~cloud0 HTML5 VNC client - daemon and programs
    ii python-novnc 1:0.4+dfsg+1+20130425+git4973b9cc80-1~cloud0 HTML5 VNC client - libraries
    # dpkg -l | grep nova
    ii nova-api 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - API frontend
    ii nova-cert 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - certificate management
    ii nova-common 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - common files
    ii nova-conductor 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - conductor service
    ii nova-consoleauth 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - Console Authenticator
    ii nova-doc 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - documentation
    ii nova-novncproxy 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - NoVNC proxy
    ii nova-scheduler 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute - virtual machine scheduler
    ii python-nova 1:2013.2~rc1-0ubuntu3~cloud0 OpenStack Compute Python libraries
    ii python-novaclient 1:2.15.0-0ubuntu1~cloud0 client library for OpenStack Compute API

* Host OS is Ubuntu Server 12.04.3 LTS

    # lsb_release -a
    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 12.04.2 LTS
    Release: 12.04
    Codename: precise

* my nova.conf includes these lines.

    vnc_enabled = true
    novncproxy_base_url=http://10.200.10.82:6080/vnc_auto.html
    novncproxy_port=6080
    vncserver_proxyclient_address=10.200.10.82
    vncserver_listen=0.0.0.0

Thanks from Tokyo.

Tags: console
Changed in horizon:
importance: Undecided → Medium
milestone: none → icehouse-1
status: New → Triaged
Revision history for this message
Tomokazu Hirai (tomokazu-hirai) wrote :

I found a zombie process of nova-novncproxy.

nova 24982 0.0 0.7 134340 32328 ? Ss 20:22 0:00 /usr/bin/python /usr/bin/nova-novncproxy --config-file=/etc/nova/nova.conf
nova 25067 0.0 0.0 0 0 ? Z 20:25 0:00 [nova-novncproxy] <defunct>

now I use ubuntu cloud archive package (2013.2-0ubuntu1~cloud0)

# dpkg -l | grep novnc
ii nova-novncproxy 1:2013.2-0ubuntu1~cloud0 OpenStack Compute - NoVNC proxy
ii novnc 1:0.4+dfsg+1+20130425+git4973b9cc80-1ubuntu1~cloud0 HTML5 VNC client - daemon and programs
ii python-novnc 1:0.4+dfsg+1+20130425+git4973b9cc80-1ubuntu1~cloud0 HTML5 VNC client - libraries

David Lyle (david-lyle)
Changed in horizon:
milestone: icehouse-1 → icehouse-2
Revision history for this message
Matthias Runge (mrunge) wrote :

As far as I can see here, this is not a horizon bug. Nova novnc is part of nova.

Changed in horizon:
status: Triaged → Invalid
milestone: icehouse-2 → none
Matt Riedemann (mriedem)
tags: added: console
Revision history for this message
Russell Bryant (russellb) wrote :

Can you replicate this with the latest code?

This could be the fault of the image you were using. What image?

Changed in nova:
status: New → Incomplete
Revision history for this message
Haomeng,Wang (whaom) wrote :

This is not an invalid bug, I encountered same issue, try to debug, fond novaproxy try to connect to '-1' port as the console default port, that should be incorrect port number, I think that should be root cause, but not sure why is it.

Revision history for this message
Julie Pichon (jpichon) wrote :

Horizon gets the URL (including the port) from nova get-vnc-console, which I believe is defined in the nova.conf file

Revision history for this message
Hassaan (hassaan) wrote :

1)Open rfb.js file in the editor of your control node located at : /usr/share/novnc/include/rfb.js
2)Find def_con_timeout variable in the file
3) Increase the timeout interval (i changed it to 200:500)
4)Save and exit
5)Restart the noVNC service by following command:
service openstack-nova-novncproxy restart

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]

Changed in nova:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.