|
»
Blank screen after terminated session
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
Blank screen after terminated session
by Jonathan Bayer-2
::
Rate this Message:
Hi,
I have the Free-nx server installed on a CentOS 5.3 Xen system. I also downloaded and installed the free NoMachine client. When first starting up the CentOS server, the NoMachine client attaches to the server and displays the desktop nicely. I then click the little x (running the client on a Linux box), and click the Terminate button. I then try to start it again, but now I get a blank screen. This is totally repeatable, the only way to get FreeNX to work is to reboot the CentOS server, which will be unacceptable in a production environment. I tried restarting the freenx server, no luck. Any suggestions would be greatly appreciated. JBB ________________________________________________________________ Were you helped on this list with your FreeNX problem? Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: http://www.nomachine.com/kb/ ________________________________________________________________ FreeNX-kNX mailing list --- FreeNX-kNX@... https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________ |
|
|
Re: Blank screen after terminated session
by ChrisB-6
::
Rate this Message:
Jonathan Bayer <jbayer@...> wrote on 24/09/2009 21:17:01: > Hi, > > I have the Free-nx server installed on a CentOS 5.3 Xen system. I also > downloaded and installed the free NoMachine client. > > When first starting up the CentOS server, the NoMachine client attaches > to the server and displays the desktop nicely. I then click the little > x (running the client on a Linux box), and click the Terminate button. > > I then try to start it again, but now I get a blank screen. This is Do you mean a blank X session AFTER sucessfully connecting to the FreeNX server the second time. If you ps -ef , what state is the new session ?? When you terminate the first session, does is die completely, partialy, not at all ?? Check what's still running. > totally repeatable, the only way to get FreeNX to work is to reboot the > CentOS server, which will be unacceptable in a production environment. > > I tried restarting the freenx server, no luck. > Please explain what you mean by this. The FreeNX server is run by the user after connecting from the client. There is no server daemin process to re-start !! > Any suggestions would be greatly appreciated. > > > > JBB > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > > http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ > > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/ > > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx > ________________________________________________________________ ________________________________________________________________ Were you helped on this list with your FreeNX problem? Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: http://www.nomachine.com/kb/ ________________________________________________________________ FreeNX-kNX mailing list --- FreeNX-kNX@... https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________ |
|
|
Re: Blank screen after terminated session
by Jonathan Bayer-2
::
Rate this Message:
On Fri, 2009-09-25 at 09:12 +0100, ChrisB wrote:
> > > Jonathan Bayer <jbayer@...> wrote on 24/09/2009 21:17:01: > > > Hi, > > > > I have the Free-nx server installed on a CentOS 5.3 Xen system. I > also > > downloaded and installed the free NoMachine client. > > > > When first starting up the CentOS server, the NoMachine client > attaches > > to the server and displays the desktop nicely. I then click the > little > > x (running the client on a Linux box), and click the Terminate > button. > > > > I then try to start it again, but now I get a blank screen. This > is > > > Do you mean a blank X session AFTER sucessfully connecting to the > FreeNX server the second time. > If you ps -ef , what state is the new session ?? > > When you terminate the first session, does is die completely, > partialy, not at all ?? Check what's still running. > > > > > > totally repeatable, the only way to get FreeNX to work is to reboot > the > > CentOS server, which will be unacceptable in a production > environment. > > > > I tried restarting the freenx server, no luck. > > > > Please explain what you mean by this. > The FreeNX server is run by the user after connecting from the > client. > There is no server daemin process to re-start !! > > > > > Any suggestions would be greatly appreciated. > > > > OK. I rebooted the system. Before doing anything, I did a ps -ef, here is the output: > PID TTY STAT TIME COMMAND > 4509 pts/2 Ss 0:00 -bash LANG=en_US.UTF-8 USER=root LOGNAME=root HOME=/root PATH=/usr/local > 4545 pts/2 R+ 0:00 \_ ps ef HOSTNAME=godzilla TERM=xterm SHELL=/bin/bash HISTSIZE=1000 KDE > 4484 tty7 Ss+ 0:02 /usr/bin/Xorg :0 -br -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7 > 4382 tty6 Ss+ 0:00 /sbin/mingetty tty6 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi > 4380 tty5 Ss+ 0:00 /sbin/mingetty tty5 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi > 4378 tty4 Ss+ 0:00 /sbin/mingetty tty4 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi > 4377 tty3 Ss+ 0:00 /sbin/mingetty tty3 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi > 4376 tty2 Ss+ 0:00 /sbin/mingetty tty2 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi > 4375 tty1 Ss+ 0:00 /sbin/mingetty tty1 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi Also, I did a ps ax | grep nx, and got nothing. Now I started freenx: ps -ef PID TTY STAT TIME COMMAND 4509 pts/2 Ss 0:00 -bash LANG=en_US.UTF-8 USER=root LOGNAME=root HOME=/root PATH=/usr/local 5338 pts/2 R+ 0:00 \_ ps ef HOSTNAME=godzilla TERM=xterm SHELL=/bin/bash HISTSIZE=1000 KDE 4484 tty7 Ss+ 0:02 /usr/bin/Xorg :0 -br -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7 4382 tty6 Ss+ 0:00 /sbin/mingetty tty6 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4380 tty5 Ss+ 0:00 /sbin/mingetty tty5 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4378 tty4 Ss+ 0:00 /sbin/mingetty tty4 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4377 tty3 Ss+ 0:00 /sbin/mingetty tty3 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4376 tty2 Ss+ 0:00 /sbin/mingetty tty2 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4375 tty1 Ss+ 0:00 /sbin/mingetty tty1 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi ps ax | grep nx 4547 ? Ss 0:00 sshd: nx [priv] 4549 ? S 0:00 sshd: nx@notty 4550 ? Ss 0:00 /bin/bash /usr/bin/nxserver 4829 ? S 0:00 /bin/bash /usr/bin/nxserver 4832 ? S 0:00 /bin/bash /usr/bin/nxserver 4835 ? S 0:00 /bin/bash /usr/bin/nxserver 4849 ? S 0:00 ssh -l root 127.0.0.1 -p 22 -x -2 -i /etc/nxserver/users.id_dsa -o PubkeyAuthentication yes -o RSAAuthentication yes -o RhostsAuthentication no -o PasswordAuthentication no -o RhostsRSAAuthentication no -o StrictHostKeyChecking no /usr/bin/nxnode --startsession 4853 ? Ss 0:00 /bin/bash /usr/bin/nxnode --startsession 5080 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 5081 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 5083 ? S 0:00 /usr/lib/NX/nxagent -persistent -D -name NX - root@godzilla:1003 - godzilla (GPL Edition) -option /root/.nx/C-godzilla-1003-C7310C228B877A7D7EE819E01A0FF1CC/options -keyboard pc102/us -geometry 1024x768+328+141 -nolisten tcp :1003 5085 ? S 0:00 tee /root/.nx/C-godzilla-1003-C7310C228B877A7D7EE819E01A0FF1CC/session 5086 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 5087 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 5418 pts/2 S+ 0:00 grep nx Now I closed the freenx session by clicking the Terminate button in the dialog which opens up when I click the "x" box. ps -ef PID TTY STAT TIME COMMAND 4509 pts/2 Ss 0:00 -bash LANG=en_US.UTF-8 USER=root LOGNAME=root HOME=/root PATH=/usr/local 5622 pts/2 R+ 0:00 \_ ps ef HOSTNAME=godzilla TERM=xterm SHELL=/bin/bash HISTSIZE=1000 KDE 4484 tty7 Ss+ 0:02 /usr/bin/Xorg :0 -br -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7 4382 tty6 Ss+ 0:00 /sbin/mingetty tty6 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4380 tty5 Ss+ 0:00 /sbin/mingetty tty5 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4378 tty4 Ss+ 0:00 /sbin/mingetty tty4 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4377 tty3 Ss+ 0:00 /sbin/mingetty tty3 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4376 tty2 Ss+ 0:00 /sbin/mingetty tty2 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4375 tty1 Ss+ 0:00 /sbin/mingetty tty1 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi ps ax | grep nx again gave nothing Now, I started the freenx client again. ps ef PID TTY STAT TIME COMMAND 4509 pts/2 Ss 0:00 -bash LANG=en_US.UTF-8 USER=root LOGNAME=root HOME=/root PATH=/usr/local 7057 pts/2 R+ 0:00 \_ ps ef HOSTNAME=godzilla TERM=xterm SHELL=/bin/bash HISTSIZE=1000 KDE 4484 tty7 Ss+ 0:02 /usr/bin/Xorg :0 -br -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7 4382 tty6 Ss+ 0:00 /sbin/mingetty tty6 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4380 tty5 Ss+ 0:00 /sbin/mingetty tty5 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4378 tty4 Ss+ 0:00 /sbin/mingetty tty4 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4377 tty3 Ss+ 0:00 /sbin/mingetty tty3 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4376 tty2 Ss+ 0:00 /sbin/mingetty tty2 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4375 tty1 Ss+ 0:00 /sbin/mingetty tty1 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi ps ax | grep nx 6410 ? Ss 0:00 sshd: nx [priv] 6412 ? S 0:00 sshd: nx@notty 6413 ? Ss 0:00 /bin/bash /usr/bin/nxserver 6692 ? S 0:00 /bin/bash /usr/bin/nxserver 6695 ? S 0:00 /bin/bash /usr/bin/nxserver 6700 ? S 0:00 /bin/bash /usr/bin/nxserver 6712 ? S 0:00 ssh -l root 127.0.0.1 -p 22 -x -2 -i /etc/nxserver/users.id_dsa -o PubkeyAuthentication yes -o RSAAuthentication yes -o RhostsAuthentication no -o PasswordAuthentication no -o RhostsRSAAuthentication no -o StrictHostKeyChecking no /usr/bin/nxnode --startsession 6716 ? Ss 0:00 /bin/bash /usr/bin/nxnode --startsession 6943 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 6944 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 6946 ? S 0:00 /usr/lib/NX/nxagent -persistent -D -name NX - root@godzilla:1003 - godzilla (GPL Edition) -option /root/.nx/C-godzilla-1003-98EFB0FA49F1F386D4E99FB468A25E22/options -keyboard pc102/us -geometry 1024x768+328+141 -nolisten tcp :1003 6948 ? S 0:00 tee /root/.nx/C-godzilla-1003-98EFB0FA49F1F386D4E99FB468A25E22/session 6949 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 6951 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 7061 pts/2 S+ 0:00 grep nx and I have a blank screen. Again, I close the client. Now I get: ps ef PID TTY STAT TIME COMMAND 4509 pts/2 Ss 0:00 -bash LANG=en_US.UTF-8 USER=root LOGNAME=root HOME=/root PATH=/usr/local 7808 pts/2 R+ 0:00 \_ ps ef HOSTNAME=godzilla TERM=xterm SHELL=/bin/bash HISTSIZE=1000 KDE 4484 tty7 Ss+ 0:02 /usr/bin/Xorg :0 -br -audit 0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7 4382 tty6 Ss+ 0:00 /sbin/mingetty tty6 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4380 tty5 Ss+ 0:00 /sbin/mingetty tty5 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4378 tty4 Ss+ 0:00 /sbin/mingetty tty4 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4377 tty3 Ss+ 0:00 /sbin/mingetty tty3 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4376 tty2 Ss+ 0:00 /sbin/mingetty tty2 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi 4375 tty1 Ss+ 0:00 /sbin/mingetty tty1 HOME=/ TERM=linux SELINUX_INIT=YES PATH=/bin:/usr/bi ps ax | grep nx 7404 ? S 0:00 /bin/bash /usr/bin/nxserver 7407 ? S 0:00 /bin/bash /usr/bin/nxserver 7408 ? S 0:00 /bin/bash /usr/bin/nxserver 7424 ? S 0:00 ssh -l root 127.0.0.1 -p 22 -x -2 -i /etc/nxserver/users.id_dsa -o PubkeyAuthentication yes -o RSAAuthentication yes -o RhostsAuthentication no -o PasswordAuthentication no -o RhostsRSAAuthentication no -o StrictHostKeyChecking no /usr/bin/nxnode --startsession 7428 ? Ss 0:00 /bin/bash /usr/bin/nxnode --startsession 7657 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession 7805 pts/2 S+ 0:00 grep nx For a lark, I killed all these processes and tried connecting again, no luck. Not sure it is significent, but I am logging in as root. JBB ________________________________________________________________ Were you helped on this list with your FreeNX problem? Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: http://www.nomachine.com/kb/ ________________________________________________________________ FreeNX-kNX mailing list --- FreeNX-kNX@... https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________ |
|
|
Re: Blank screen after terminated session
by ChrisB-6
::
Rate this Message:
Jonathan Bayer <jbayer@...> wrote on 25/09/2009 15:59:31: > > > > SNIP > > OK. I rebooted the system. Before doing anything, I did a ps -ef, here > Now I started freenx: > > ps -ef > > PID TTY STAT TIME COMMAND > 4509 pts/2 Ss 0:00 -bash LANG=en_US.UTF-8 USER=root > LOGNAME=root HOME=/root PATH=/usr/local > 5338 pts/2 R+ 0:00 \_ ps ef HOSTNAME=godzilla TERM=xterm > SHELL=/bin/bash HISTSIZE=1000 KDE > 4484 tty7 Ss+ 0:02 /usr/bin/Xorg :0 -br -audit 0 -auth > /var/gdm/:0.Xauth -nolisten tcp vt7 > 4382 tty6 Ss+ 0:00 /sbin/mingetty tty6 HOME=/ TERM=linux > SELINUX_INIT=YES PATH=/bin:/usr/bi > 4380 tty5 Ss+ 0:00 /sbin/mingetty tty5 HOME=/ TERM=linux > SELINUX_INIT=YES PATH=/bin:/usr/bi > 4378 tty4 Ss+ 0:00 /sbin/mingetty tty4 HOME=/ TERM=linux > SELINUX_INIT=YES PATH=/bin:/usr/bi > 4377 tty3 Ss+ 0:00 /sbin/mingetty tty3 HOME=/ TERM=linux > SELINUX_INIT=YES PATH=/bin:/usr/bi > 4376 tty2 Ss+ 0:00 /sbin/mingetty tty2 HOME=/ TERM=linux > SELINUX_INIT=YES PATH=/bin:/usr/bi > 4375 tty1 Ss+ 0:00 /sbin/mingetty tty1 HOME=/ TERM=linux > SELINUX_INIT=YES PATH=/bin:/usr/bi > > ps ax | grep nx > > 4547 ? Ss 0:00 sshd: nx [priv] > 4549 ? S 0:00 sshd: nx@notty > 4550 ? Ss 0:00 /bin/bash /usr/bin/nxserver > 4829 ? S 0:00 /bin/bash /usr/bin/nxserver > 4832 ? S 0:00 /bin/bash /usr/bin/nxserver > 4835 ? S 0:00 /bin/bash /usr/bin/nxserver > 4849 ? S 0:00 ssh -l root 127.0.0.1 -p 22 -x -2 -i > /etc/nxserver/users.id_dsa -o PubkeyAuthentication yes -o > RSAAuthentication yes -o RhostsAuthentication no -o > PasswordAuthentication no -o RhostsRSAAuthentication no -o > StrictHostKeyChecking no /usr/bin/nxnode --startsession > 4853 ? Ss 0:00 /bin/bash /usr/bin/nxnode --startsession > 5080 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession > 5081 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession > 5083 ? S 0:00 /usr/lib/NX/nxagent -persistent -D -name > NX - root@godzilla:1003 - godzilla (GPL Edition) -option /root/. > nx/C-godzilla-1003-C7310C228B877A7D7EE819E01A0FF1CC/options - > keyboard pc102/us -geometry 1024x768+328+141 -nolisten tcp :1003 > 5085 ? S 0:00 tee /root/.nx/C-godzilla-1003- > C7310C228B877A7D7EE819E01A0FF1CC/session > 5086 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession > 5087 ? S 0:00 /bin/bash /usr/bin/nxnode --startsession > 5418 pts/2 S+ 0:00 grep nx > > OK , that's not all of it though. There should be a startkde and a start_kdeinit or some such somewhere . . . But sounds like the difficult bits are working though. Looks like it isn't finishing off either starting up or shutting down ( or both ) properly It might be worth trying a different user if you haven't already . . . Also If you set debug on in /etc/nxserver/node.conf *ON THE SERVER* NX_LOG_LEVEL=6 NX_LOG_SECURE=1 # writeable for the "nx" user NX_LOGFILE=/var/log/nxserver.log SESSION_LOG_CLEAN=0 You should see in the log where it is getting stuck. Are you setting up printers or shares, if so does it work without them. You will need to set up debugging, then make a fresh connection, disconnect and connect again !! I get the following. The NX> 999 Bye is where the startup finishes, the last line when I terminate and disconnect. NX> 105 bye Bye NX> 999 Bye session_status A ... B Terminating server_nxnode_echo: NX> 1009 Session status: terminating session_close A ... B server_nxnode_echo: NX> 1006 Session status: closed If you have the Nomachine client on the server, you can run nxclient --admin as the user, which will tell you what it thinks is still running looking at the .nx directory. > > > JBB > > > > ________________________________________________________________ > Were you helped on this list with your FreeNX problem? > Then please write up the solution in the FreeNX Wiki/FAQ: > > http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ > > Don't forget to check the NX Knowledge Base: > http://www.nomachine.com/kb/ > > ________________________________________________________________ > FreeNX-kNX mailing list --- FreeNX-kNX@... > https://mail.kde.org/mailman/listinfo/freenx-knx > ________________________________________________________________ ________________________________________________________________ Were you helped on this list with your FreeNX problem? Then please write up the solution in the FreeNX Wiki/FAQ: http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ Don't forget to check the NX Knowledge Base: http://www.nomachine.com/kb/ ________________________________________________________________ FreeNX-kNX mailing list --- FreeNX-kNX@... https://mail.kde.org/mailman/listinfo/freenx-knx ________________________________________________________________ |
| Free embeddable forum powered by Nabble | Forum Help |
