F15 VNC Stopped Working

[mbrad]

Thank you for taking the time to read my question.

I upgraded to F15 a few weeks ago. It all worked well. Then the other day VNC stopped working. I VNC from my Windows XP pc to my F15 server. The only thing I can figure happened is that an update (yum update) has messed up my settings.

I now see that you need to type systemctl to see what services are running. You used to be able to go to a menu item to see that. I wish that was still there. Anyway, this is what I get when I check on the status of the VNC server service:

[root@localhost brad]# systemctl status vncserver.service
vncserver.service - LSB: start|stop|restart|try-restart|status|force-reload vncserver
Loaded: loaded (/etc/rc.d/init.d/vncserver)
Active: failed since Tue, 11 Oct 2011 23:51:06 -0500; 21s ago
Process: 2054 ExecStart=/etc/rc.d/init.d/vncserver start (code=exited, status=2/INVALIDARGUMENT)
CGroup: name=systemd:/system/vncserver.service
[root@localhost brad]#

I have no idea what the error message means.


This is my setting for VNC:

VNCSERVERS="1:brad"
VNCSERVERARGS[1]="-geometry 1280x1024 -depth 24"

On my Windows PC the error I get is

"Unable to resolve host by name: No such host is known. (11001)"

I'm trying to connect to 192.168.0.5:1

I have ports 5900 and 5901 open. They were open before as well. I don't think any of my firewall settings have changed.

I suppose VNC server service is not running, and I don't know how to get it started.

Any help would be great.

Thanks,

Brad


UPDATE: Oct 13, 2011:
I found the logs... or a log anyway. it says this:

Oct 13 19:21:11 localhost systemd[1]: vncserver.service: control process exited, code=exited status=2
Oct 13 19:21:11 localhost systemd[1]: Unit vncserver.service entered failed state.

[navilight]

A bit late to reply to this...

One problem that can cause this is having previous Unix domain sockets sticking around. These are usually in /tmp/.X11-unix. I had exactly the errors you reported above and solved it with:

rm -f /tmp/.X11-unix/*

I was then able to start the vncserver without the above errors.

It's probably too late to help you, but hopefully someone else will find it useful one day if they're unlucky enough to get this error for the same reason I did.