Real VNC server fails to start, Xvnc-core: client 1 rejected from local host
 

I set up 3 nodes in a cluster to work fine, but I messed up the VNC install/setup on one of them somehow, I am stumped for now.

On the server (RHEL 6.4) I start vncserver (5.1) I get no errors to stdout:

[root@abc vnc]# vncserver
VNC(R) Server 5.1.0 (r115125)
Built on Dec 6 2013 14:44:55
Copyright (C) 2002-2013 RealVNC Ltd.
VNC is a registered trademark of RealVNC Ltd. in the U.S. and in other
countries.
...
Log file is /root/.vnc/abc:1.log
New desktop is abc:1 (10.67.2.84:1)

But vncserver fails to start. ps -ef shows no vnc anything running.

The log shows:

VNC(R) Server 5.1.0 (r115125)
Built on Dec 6 2013 14:47:40
Copyright (C) 2002-2013 RealVNC Ltd.
...
AUDIT: Wed Jan 29 08:45:06 2014: 17398 Xvnc-core: client 1 rejected from local host
No protocol specified
VNC(R) Server 5.1.0 (r115125)
Built on Dec 6 2013 14:44:51
Copyright (C) 2002-2013 RealVNC Ltd.
VNC is a registered trademark of RealVNC Ltd. in the U.S. and in other
countries.
<11> 2014-01-29T16:45:06.990Z abc
vncserverui-virtual[17399]: vncserverui: unable to open display ":1"
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
No protocol specified
xsetroot: unable to open display ':1'
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
AUDIT: Wed Jan 29 08:45:07 2014: 17398 Xvnc-core: client 1 rejected from local host
...
<13> 2014-01-29T16:45:08.022Z abc
Xvnc[17398]: ServerManager: Server stopped

Once I delete ~/.Xauthority I can run Xvnc directly:

[root@abc vnc]# /usr/bin/Xvnc-core :1 -auth /root/.Xauthority -pn

This works, but I get no window manager to speak of. I can stop and start that repeatedly and connect to it with VNC viewer that is OK. But vncserver still fails. Once I run vncserver I have to delete ~/.Xauthority before I can run Xnvc-core. It is like vncserver is corrupting the .Xauthority file. Xvnc-core is not. I can stop and start Xvnc-core repeatedly without deleting .Xauthority The error I get from Xvnc-core after running vncserver without deleting .Xauthority is:

<11> 2014-01-29T16:40:10.152Z abc vncserverui-virtual[16453]: vncserverui: unable to open display ":1"

That is all I can come up with for now. Any suggestions?

This probably related to your xauth.

1. Release any stale locks to your Xauthority
% xauth -b list

2. Check if your entries has the same key for "hostname:port" and "hostname/unix:port"
% xauth list
abc:1 MIT-MAGIC-COOKIE-1 xxxxxxxxxxxxxxxxxxxxx
abc/unix:1 MIT-MAGIC-COOKIE-1 xxxxxxxxxxxxxxxxxxxxx
abc.fdqn/unix:1 MIT-MAGIC-COOKIE-1 xxxxxxxxxxxxxxxxxxxxx

3. Insert any missing entries
% xauth add abc/unix:1 MIT-MAGIC-COOKIE-1 xxxxxxxxxxxxxxxxxxxxx

4. Restart your vncserver
% vncserver -kill :1
% vncserver :1

Thanks for the tip
 

I've been struggling with VNC Enterprise Edition for the last day or so. I'm using vncserver-virtuald which basically listens for new VNC connections on a port, and when a new VNC request is sent, it spawns a vnc server for the user requesting it and transfer the connection there.

Youy tip lead me to figure out that the process isn't adding the FQDN/unix:<display> to the xauth list.

Of course, now I have to figure out why that's not happening but at least I'm getting somewhere!

Thanks again!

And in case anyone else comes across this, here's the solution, though I think it's ugly.

http://kb.realvnc.com/questions/298/...n+Virtual+Mode