Submitted by ghomem on Wed, 10/11/2017 - 06:01
We have two equal Cloudmin servers. One of them does not provide VNC access:
"VNC has been configured on this system by Cloudmin, but the VNC server on port 5902 on host system vmserver01.XXX.YYYY is not accessible. If it was just enabled, the system will need to be rebooted before VNC is available."
I have checked that:
- iptables is off
- user has direct access at the LAN
- hostname is defined on the hosts file at the server
- telnet vmserver01.XXX.YYYY 5902 works fine both directly at the server and from a pc at the LAN
I don't see a reason for this error. What can we do?
Status:
Closed (won't fix)
Comments
Submitted by ghomem on Wed, 10/11/2017 - 06:02 Comment #1
adding notification checkbox
Submitted by JamieCameron on Wed, 10/11/2017 - 23:24 Comment #2
Are you running Xen VMs, or KVM?
Submitted by ghomem on Thu, 10/12/2017 - 05:21 Comment #3
We are using KVM - we have always used KVM since we started with Cloudmin.
I checked the command line with ps and the vnc param is ":2" for this VM.
Submitted by JamieCameron on Fri, 10/13/2017 - 00:54 Comment #4
Can you telnet to that port (5902) from the master system, on the host?
Submitted by ghomem on Fri, 10/13/2017 - 06:19 Comment #5
Jamie:
The problem is with Cloudmin. Can you help us here?
Submitted by JamieCameron on Fri, 10/13/2017 - 15:54 Comment #6
If you select the host system from the left menu and click on Edit Virtual Server, on the form that appears is the IP address to use to connect to the host set to anything?
Submitted by ghomem on Wed, 10/18/2017 - 09:53 Comment #7
Hi Jamie,
There was a wrong IP at the place.
I would like to understand how it might have made it there. Any idea?
(I didn't install the host myself and our install procedure mandates the interfaces configuration before cloudmin is installed - but who installed it could have made a mistake).
Submitted by JamieCameron on Wed, 10/18/2017 - 22:50 Comment #8
Usually if there is an IP there, it was entered by the admin to force connection to the host on a specific interface.
Submitted by ghomem on Thu, 10/19/2017 - 06:46 Comment #9
OK, so let's assume it was a mistake on our side.
Thank you very much for the support. I'm closing this issue.
Cheers Gustavo