Blank VNC Console

mcit

Renowned Member
May 16, 2010
35
1
73
I have recently started to experience a blank screen when trying to use the console. I am not aware of any changes to the system prior to this problem.

proxmox3:~# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55
pve-kernel-2.6.18-2-pve: 2.6.18-5
pve-kernel-2.6.32-6-pve: 2.6.32-55
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

I click on Open VNC Console, I get the popup window, and it appears to begin loading, then nothing happens. I have tried it from 4 different machines so I do not believe it is a java issue. How do I troubleshoot this?


Matthew
 
Last edited:
Seems to me that you are missing, on the client (your PC) side, java or the browser plugin. I use only GNU and not Windows, and I need to install for instance "icedtea6-plugin"
like:
# aptitude install openjdk-6-jre icedtea6-plugin
Is really strange that is the same on 4 machines, but is the only thing that comes to my mind (or maybe some firewall issue preventing traffic on port 9000 used by vnc?)
Sorry, no more ideas on the subject
 
This was my original thought, however, from the same machine, I can use the console on my other proxmox servers without a problem, so I think it must be something on the server itself. I am not sure how to troubleshoot this though.
 
do you have the problem on all VM´s or just on one. create a new one and lets see it this console is here. test KVM and container console.
 
It occurs with all the VMs on this server. I have just created a new KVM and a VZ Container, and the problem is the same for these also. Blank screen. I have attached a screenshot also.
 

Attachments

  • ss1.jpg
    ss1.jpg
    40.3 KB · Views: 34
I have discovered the root cause of this problem. For the sake of the thread the issue was caused by the installation of the Adaptec Storage Manager software.

Whilst installing, I was unable to connect to the service remotely. I made the following change to the hosts file [as advised by adaptec]
---
- If you cannot connect to a local or remote Adaptec Storage Manager
installed on a Linux system, verify that the TCP/IP hosts file
is configured properly.
1. Open the /etc/hosts file.
NOTE: The following is an example:
127.0.0.1 localhost.localdomain localhost matrix
2. If the hostname of the system is identified on the line
with 127.0.0.1, you must create a new host line.
3. Remove the hostname from the 127.0.0.1 line.
NOTE: The following is an example:
127.0.0.1 localhost.localdomain localhost
4. On a new line, type the IP address of the system.
5. Using the Tab key, tab to the second column and enter the
fully qualified hostname.
6. Using the Tab key, tab to the third column and enter the
nickname for the system.
NOTE: The following is an example of a completed line:
1.1.1.1 matrix.localdomain matrix
where 1.1.1.1 is the IP address of the server and
matrix is the hostname of the server.
7. Restart the server for changes to take effect.
---
This appears to have been the cause. After I returned the hosts file to its original settings, the problem is no longer occurring. Interestingly, I can also still connect remotely via the adaptec storage manager software also.

I made this change months ago, however, the problem did not occurr at that time.
 
Yes, I followed that guide initially, however, I was unable to connect to the asm service until I made the changes above. After that, everything worked fine.