VNC has been configured on this system by Cloudmin, but the VNC server on port 5909 not working

Submitted by Lucian on Tue, 08/16/2011 - 18:18

Hi,

I just did a kernel update (from the cr repo[1] - newer kvm and kernel) on my centos 5 host and rebooted everything, now after fresh reboot I cannot access the graphical console on some of the VPSes. I get an error like: "VNC has been configured on this system by Cloudmin, but the VNC server on port 5909 on host system is not accessible. If it was just enabled, the system will need to be rebooted before VNC is available."

If I issue a reboot from the "System state" section it fixes the problem, but it means that VPS was just rebooted 2 times.

Any ideas how to avoid this in the future?

[1] - http://www.h-online.com/open/news/item/CentOS-to-deliver-advance-updates...

Status: 
Active

Comments

Submitted by JamieCameron on Tue, 08/16/2011 - 18:37

If you see this, try SSHing into the host system and running :

ps auxwwww | grep kvm

and check of the VNC port in the command line is the same as the port in the error. Specifically, look at the number in the -vnc flag and add 5900 to it.

Submitted by Lucian on Tue, 08/16/2011 - 19:14

Hi,

I'll make sure to do so next time it happens. Thanks!

Submitted by JamieCameron on Tue, 08/16/2011 - 20:59

Cool ... I have seen occasional reports of the port cloudmin expects not matching the port KVM is actually using, which can be fixed by restarting the vm. I am still looking into the underlying cause of the bug though...