vncserver startup error messages in log

keimdf · 08-22-2007, 09:29 AM

I have been trying to get vncserver running smoothly. It seems that it works to start it and I can attach to it from vnc client, but if I try to connect again it doesn't work. What I end up doing is killing the process, removing the logs and then starting it up again.

I checked the logs twice to see if there were some problems and came up with this.

first I tried to start the vncserver as a privileged user and got this log file.

Code:

_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

Xvnc version 4.0b4 - built Jan  8 2007 11:56:46
Underlying X server release 40300000, The XFree86 Project, Inc


Wed Aug 22 08:21:49 2007
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5901
 vncext:      Listening for HTTP connections on port 5801
 vncext:      created VNC server for screen 0
error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
SESSION_MANAGER=local/ANAKIN:/tmp/.ICE-unix/28172

next I started as root and got this.

Code:

Xvnc version 4.0b4 - built Jan  8 2007 11:56:46
Underlying X server release 40300000, The XFree86 Project, Inc


Wed Aug 22 08:26:59 2007
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on port 5901
 vncext:      Listening for HTTP connections on port 5801
 vncext:      created VNC server for screen 0
error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!

now I don't know if this has anything to do with the problem, but if it does, then how do I correct it?

I am running Red Hat 3.1 ES

{BBI}Nexus{BBI} · 08-22-2007, 12:02 PM

I'm not sure why you're running vncserver as root, that's not a very secure thing to do. See this thread for help on running a vncserver and how to connect to it: http://www.linuxquestions.org/questi...00#post2862900

keimdf · 08-22-2007, 01:51 PM

here is my xstartup.

Code:

#!/bin/sh

# Uncomment the following two lines for normal desktop:
 unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc
 exec gnome-session &

#[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
#xsetroot -solid grey
#vncconfig -iconic &
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#twm &

I modfied this so that I could vnc from a Windows Client into a xwindows (gui) session on the Linux box.

besides the errors that I got, when I log off of the session, it clears the screen, leaves the background picture up and then just hangs there.

After a while I simply use the "X" box on the upper right corner to delete the session. Then I have to go the Linux OS and kill the vnc session there before I can come back in again.

{BBI}Nexus{BBI} · 08-22-2007, 05:03 PM

This is how your xstartup should look:

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
exec gnome-session &

Backup your current xstartup and try the above as it is instead.

keimdf · 08-22-2007, 05:26 PM

This did not work. It brought me into a gui windows as planned, but when I did a "Log Off", it close all of the icons and then left the VNC desktop hanging. I waited for a while and then "closed the connection". I waited a while longer and then went back into the client VNC from the windows and it brought up just the GUI background with no icons.

If I kill the vncserver, it seems to clear everything, but that means that I have to run the vncserver command again to go into the GUI console.

{BBI}Nexus{BBI} · 08-22-2007, 06:26 PM

Log off? There's no need to do that. Just close the window (like you would for any app that you no longer need). The session will remain active until you shutdown the remote machine or kill the Xvnc session on the remote machine. With the session still active you only need to log in using the same details you started the initial session with, and the desktop should be as you left it when you closed the window.

keimdf · 08-22-2007, 08:35 PM

I guess, I misunderstood how vncserver worked. if I start something on it, it must stay running on the Linux box as long as the box is running or the pid for vncserver session is running (not killed).

if this is the case, then how do I set up my boot up to include starting a vnc session for a particular user???

{BBI}Nexus{BBI} · 08-22-2007, 08:56 PM

What you're looking for can be found here: http://linuxreviews.org/howtos/xvnc/ go to section 6 - Create a file called /etc/xinetd.d/xvncserver. There's also this page that explains how to autostart a session for a particular user: http://www.linuxforums.org/forum/lin...re-5-boot.html