Chris Kenward
asked on
No GNOME session just blank screen with large X cursor
Hi there folks
I have a minor problem that I can't seem to find an answer for that makes any sense. I've virtualised one of my Linux servers and everything appears to be working just fine. However, when I log into the box using VNC, I just get a blank screen with the X cursor. Log file says:
Mon Nov 9 23:20:19 2009
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 /SecurityP olicy
Could not init font path element /usr/X11R6/lib/X11/fonts/T TF/, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/C ID/, removing from list!
gnome-session: you're already running a session manager
Mon Nov 9 23:20:29 2009
Connections: accepted: 187.192.213.184::53984
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
Mon Nov 9 23:20:32 2009
VNCSConnST: Server default pixel format depth 16 (16bpp) little-endian rgb565
VNCSConnST: Client pixel format depth 16 (16bpp) little-endian rgb565
Mon Nov 9 23:20:38 2009
Connections: closed: 187.192.213.184::53984 (Clean disconnection)
Any ideas? I've deleted the files from /etc/X11/tmp but hasn't helped. I do have VM-Tools running on the machine but I have now virtualised several of my CentOS servers without this problem occurring.
Hoping for a solution
Chris
I have a minor problem that I can't seem to find an answer for that makes any sense. I've virtualised one of my Linux servers and everything appears to be working just fine. However, when I log into the box using VNC, I just get a blank screen with the X cursor. Log file says:
Mon Nov 9 23:20:19 2009
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
Could not init font path element /usr/X11R6/lib/X11/fonts/T
Could not init font path element /usr/X11R6/lib/X11/fonts/C
gnome-session: you're already running a session manager
Mon Nov 9 23:20:29 2009
Connections: accepted: 187.192.213.184::53984
SConnection: Client needs protocol version 3.8
SConnection: Client requests security type VncAuth(2)
Mon Nov 9 23:20:32 2009
VNCSConnST: Server default pixel format depth 16 (16bpp) little-endian rgb565
VNCSConnST: Client pixel format depth 16 (16bpp) little-endian rgb565
Mon Nov 9 23:20:38 2009
Connections: closed: 187.192.213.184::53984 (Clean disconnection)
Any ideas? I've deleted the files from /etc/X11/tmp but hasn't helped. I do have VM-Tools running on the machine but I have now virtualised several of my CentOS servers without this problem occurring.
Hoping for a solution
Chris
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi there, KeremE
Output from the 1st command is:
local/servername:/tmp/.ICE -unix/5089
The second command gives:
root 4285 1 0 09:36 ? 00:00:00 /usr/bin/gdm-binary -nodaemon
root 4932 4285 0 09:36 ? 00:00:00 /usr/bin/gdm-binary -nodaemon
root 4981 4932 0 09:36 ? 00:00:01 /usr/X11R6/bin/X :0 -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7
root 5089 4932 0 09:36 ? 00:00:00 /usr/bin/gnome-session
root 5108 5089 0 09:36 ? 00:00:00 [Xsession] <defunct>
root 5120 5089 0 09:36 ? 00:00:00 /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "/usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients"
nobody 5151 3788 0 09:36 ? 00:00:00 /usr/sbin/httpd
root 5154 1 0 09:36 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients
root 5155 1 0 09:36 ? 00:00:00 dbus-daemon-1 --fork --print-pid 8 --print-address 6 --session
root 5159 1 0 09:36 ? 00:00:00 /usr/libexec/gconfd-2 5
root 5162 1 0 09:36 ? 00:00:00 /usr/bin/gnome-keyring-dae mon
root 5164 1 0 09:36 ? 00:00:00 /usr/libexec/bonobo-activa tion-serve r --ac-activate --ior-output-fd=19
root 5166 1 0 09:36 ? 00:00:00 /usr/libexec/gnome-setting s-daemon --oaf-activate-iid=OAFIID: GNOME_Sett ingsDaemon --oaf-ior-fd=23
root 5172 1 0 09:36 ? 00:00:00 /usr/libexec/gam_server
root 5260 1 0 09:36 ? 00:00:00 /usr/lib/vmware-tools/bin/ vmware-use r
nobody 5976 3788 0 09:39 ? 00:00:00 /usr/sbin/httpd
nobody 5977 3788 0 09:39 ? 00:00:00 /usr/sbin/httpd
root 6180 1 0 09:44 ? 00:00:00 gnome-terminal
root 6181 6180 0 09:44 ? 00:00:00 gnome-pty-helper
root 6182 6180 0 09:44 pts/1 00:00:00 bash
root 6284 1 0 09:46 pts/1 00:00:00 Xvnc :1 -desktop servername:1 (root)
-httpd /usr/share/vnc/classes -auth /root/.Xauthority -geometry 1024x768 -depth
16 -rfbwait 30000 -rfbauth /root/.vnc/passwd -rfbport 5901 -pn
nobody 6381 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6382 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6383 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6384 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6385 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6386 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6387 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 7066 3788 0 10:03 ? 00:00:00 /usr/sbin/httpd
root 7170 6182 0 10:06 pts/1 00:00:00 ps -aef
(END)
I've changed the host to "servername" in this list for obvious reasons.
I'll have a look in the /tmp folder and see what's in there and then report back.
Thanks so much for the help
Chris
Output from the 1st command is:
local/servername:/tmp/.ICE
The second command gives:
root 4285 1 0 09:36 ? 00:00:00 /usr/bin/gdm-binary -nodaemon
root 4932 4285 0 09:36 ? 00:00:00 /usr/bin/gdm-binary -nodaemon
root 4981 4932 0 09:36 ? 00:00:01 /usr/X11R6/bin/X :0 -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7
root 5089 4932 0 09:36 ? 00:00:00 /usr/bin/gnome-session
root 5108 5089 0 09:36 ? 00:00:00 [Xsession] <defunct>
root 5120 5089 0 09:36 ? 00:00:00 /usr/bin/ssh-agent /bin/sh -c exec -l /bin/bash -c "/usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients"
nobody 5151 3788 0 09:36 ? 00:00:00 /usr/sbin/httpd
root 5154 1 0 09:36 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients
root 5155 1 0 09:36 ? 00:00:00 dbus-daemon-1 --fork --print-pid 8 --print-address 6 --session
root 5159 1 0 09:36 ? 00:00:00 /usr/libexec/gconfd-2 5
root 5162 1 0 09:36 ? 00:00:00 /usr/bin/gnome-keyring-dae
root 5164 1 0 09:36 ? 00:00:00 /usr/libexec/bonobo-activa
root 5166 1 0 09:36 ? 00:00:00 /usr/libexec/gnome-setting
root 5172 1 0 09:36 ? 00:00:00 /usr/libexec/gam_server
root 5260 1 0 09:36 ? 00:00:00 /usr/lib/vmware-tools/bin/
nobody 5976 3788 0 09:39 ? 00:00:00 /usr/sbin/httpd
nobody 5977 3788 0 09:39 ? 00:00:00 /usr/sbin/httpd
root 6180 1 0 09:44 ? 00:00:00 gnome-terminal
root 6181 6180 0 09:44 ? 00:00:00 gnome-pty-helper
root 6182 6180 0 09:44 pts/1 00:00:00 bash
root 6284 1 0 09:46 pts/1 00:00:00 Xvnc :1 -desktop servername:1 (root)
-httpd /usr/share/vnc/classes -auth /root/.Xauthority -geometry 1024x768 -depth
16 -rfbwait 30000 -rfbauth /root/.vnc/passwd -rfbport 5901 -pn
nobody 6381 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6382 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6383 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6384 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6385 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6386 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 6387 3788 0 09:46 ? 00:00:00 /usr/sbin/httpd
nobody 7066 3788 0 10:03 ? 00:00:00 /usr/sbin/httpd
root 7170 6182 0 10:06 pts/1 00:00:00 ps -aef
(END)
I've changed the host to "servername" in this list for obvious reasons.
I'll have a look in the /tmp folder and see what's in there and then report back.
Thanks so much for the help
Chris
ASKER
Hi again
In /tmp
drwx------ 2 root root 4096 Nov 10 09:36 ssh-rZeGRO5089
drwxr-xr-x 2 root root 4096 Nov 9 21:25 vmware-config0
drwxr-xr-x 2 root root 4096 Nov 9 21:50 vmware-config1
drwxrwxrwt 3 root root 4096 Nov 9 21:52 VMwareDnD
drwx------ 2 root root 4096 Nov 9 21:25 vmware-root
drwxr-xr-x 2 root root 4096 Nov 9 09:51 .webmin
-r--r--r-- 1 root root 11 Nov 10 09:36 .X0-lock
drwxr-xr-x 8 root root 4096 Dec 2 2006 X11
drwxrwxrwt 2 root root 4096 Nov 10 09:46 .X11-unix
-r--r--r-- 1 root root 11 Nov 10 09:46 .X1-lock
In /tmp
drwx------ 2 root root 4096 Nov 10 09:36 ssh-rZeGRO5089
drwxr-xr-x 2 root root 4096 Nov 9 21:25 vmware-config0
drwxr-xr-x 2 root root 4096 Nov 9 21:50 vmware-config1
drwxrwxrwt 3 root root 4096 Nov 9 21:52 VMwareDnD
drwx------ 2 root root 4096 Nov 9 21:25 vmware-root
drwxr-xr-x 2 root root 4096 Nov 9 09:51 .webmin
-r--r--r-- 1 root root 11 Nov 10 09:36 .X0-lock
drwxr-xr-x 8 root root 4096 Dec 2 2006 X11
drwxrwxrwt 2 root root 4096 Nov 10 09:46 .X11-unix
-r--r--r-- 1 root root 11 Nov 10 09:46 .X1-lock
Hi,
The problem here is you're already running an X session and even a Gnome session over your host. So all you need is to connect tit through a VNC session but it seems that you're trying to restart another X session.
According to the PS output you should srat whr vnc client and connect it with
hostname:1
or
hostname:5901
IF the hostname is not resolvable through your VNC client system (pi.e., ping hostname does not return an IP address) the to use the ip address instead of hostname such as x.x.x.x:1.
Will you please describe how do you try to login using the VNC ?
Cheers,
K.
The problem here is you're already running an X session and even a Gnome session over your host. So all you need is to connect tit through a VNC session but it seems that you're trying to restart another X session.
According to the PS output you should srat whr vnc client and connect it with
hostname:1
or
hostname:5901
IF the hostname is not resolvable through your VNC client system (pi.e., ping hostname does not return an IP address) the to use the ip address instead of hostname such as x.x.x.x:1.
Will you please describe how do you try to login using the VNC ?
Cheers,
K.
ASKER
Hi there, KeremE
Hmmm.... I wonder if this has something to do with the vmware tools setup? I did have a problem running the vmware tools setup and saw something about display settings invalid or something. I ran it again and, to the prompt "Do you want to overwrite the config file?" I said YES. It was only subsequent to that that I had the issue with VNC.
I start VNCserver in the services that auto start. Perhaps I should think about NOT doing that? I could always go in and manually start VNCserver :1 any time we reboot the server?
Cheers
Chris
Hmmm.... I wonder if this has something to do with the vmware tools setup? I did have a problem running the vmware tools setup and saw something about display settings invalid or something. I ran it again and, to the prompt "Do you want to overwrite the config file?" I said YES. It was only subsequent to that that I had the issue with VNC.
I start VNCserver in the services that auto start. Perhaps I should think about NOT doing that? I could always go in and manually start VNCserver :1 any time we reboot the server?
Cheers
Chris
> I start VNCserver in the services that auto start. Perhaps I should think about NOT doing that? I could
> always go in and manually start VNCserver :1 any time we reboot the server?
But it is obvious that when you run the VNC server there's a clash occuring. BTW I think that you'd connect to some IP over the VMWare not over the target system.
Reboot the VMware Client and don't try to start VNCServer this time.
Cheers,
K.
> always go in and manually start VNCserver :1 any time we reboot the server?
But it is obvious that when you run the VNC server there's a clash occuring. BTW I think that you'd connect to some IP over the VMWare not over the target system.
Reboot the VMware Client and don't try to start VNCServer this time.
Cheers,
K.
ASKER
Hi KeremE
OK - I've stopped the service from starting automatically. I then manually killed the VNCserver with vncserver -kill :1 and tested that it wasn't working. All OK. Then I restarted the computer and made sure it still wasn't running. I then started it manually with vncserver :1 all OK. Then I had a look at the log file at /root/.vnc and this is what it said.
Tue Nov 10 19:05:32 2009
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 /SecurityP olicy
Could not init font path element /usr/X11R6/lib/X11/fonts/T TF/, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/C ID/, removing from list!
gnome-session: you're already running a session manager
.vnc/ninah:1.log (END)
Any more ideas? It's still the same.
Cheers
Chris
OK - I've stopped the service from starting automatically. I then manually killed the VNCserver with vncserver -kill :1 and tested that it wasn't working. All OK. Then I restarted the computer and made sure it still wasn't running. I then started it manually with vncserver :1 all OK. Then I had a look at the log file at /root/.vnc and this is what it said.
Tue Nov 10 19:05:32 2009
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
Could not init font path element /usr/X11R6/lib/X11/fonts/T
Could not init font path element /usr/X11R6/lib/X11/fonts/C
gnome-session: you're already running a session manager
.vnc/ninah:1.log (END)
Any more ideas? It's still the same.
Cheers
Chris
gnome-session: you're already running a session manager
means that it is already running. Please don't start VNC at all. and please post your
netstat -anpt
output.
means that it is already running. Please don't start VNC at all. and please post your
netstat -anpt
output.
ASKER
Hi there, KeremE
Definitely has something to do with the GNOME interface. If I change the runlevel to 3 then start vncserver, it works absolutely fine. So at runlevel 5 the system is starting the GNOME desktop as my default, which is what I have on all my other CentOS machines. The only difference is on this machine for some reason the desktop stops VNCserver from running?
Cheers
Chris
Definitely has something to do with the GNOME interface. If I change the runlevel to 3 then start vncserver, it works absolutely fine. So at runlevel 5 the system is starting the GNOME desktop as my default, which is what I have on all my other CentOS machines. The only difference is on this machine for some reason the desktop stops VNCserver from running?
Cheers
Chris
I think the problem is not the VNC. The problem is your system already runs a session manager. I guess the problem is this particular system is already running X. This means that VMWare tools was installed over this particular system while the others don't have it.
If you had sent the netstat -anpt output before you'd run vncserver we would have looked into it.
Cheers,
K.
If you had sent the netstat -anpt output before you'd run vncserver we would have looked into it.
Cheers,
K.
Will you also send me the output of:
rpm -qa |grep -i "vmware"
Cheers,
K.
rpm -qa |grep -i "vmware"
Cheers,
K.
ASKER
Hi there, KeremE
Sorry - I didn't send the output from the netstat because it's full of the server IP which I'm not happy having in a public forum. If I can search and replace I will send it though because i really do need it resolved. I have just discovered another CentOS server I have virtualised has exactly the same issue. While it's at runlevel 5 and therefore running the Gnome, the vncserver will not work. If I bring runlevel to 3 and then manually start vncserver, all works fine.
Will also have a look at the other command output for you. Sorry for the delays getting back to you - been a little busy this side with work. Will try and do something tonight later or tomorrow.
Best wishes
Chris
Sorry - I didn't send the output from the netstat because it's full of the server IP which I'm not happy having in a public forum. If I can search and replace I will send it though because i really do need it resolved. I have just discovered another CentOS server I have virtualised has exactly the same issue. While it's at runlevel 5 and therefore running the Gnome, the vncserver will not work. If I bring runlevel to 3 and then manually start vncserver, all works fine.
Will also have a look at the other command output for you. Sorry for the delays getting back to you - been a little busy this side with work. Will try and do something tonight later or tomorrow.
Best wishes
Chris
ASKER
Just did the rpm -qa on the affected machine with runlevel at 3 and returns nothing. Will reset runlevel and reboot later and see if there is a difference and let you know.
ASKER
Thanks for the help!
You're welcome
Try this out.