Kai Yang Tay
2007-Apr-25 04:48 UTC
[CentOS] Having trouble with FreeNX, Need help to make it work perfectly
Hi thanks for the reply i am really grateful if you can tell me how to make FreeNX work like charm. I am really stuck with it, and after reinstalling the server is definitely pissing off my boss. Please help me thanks. ========================== Please let me review how my FreeNX was screwed up. After i fresh install my CentOS 5, I 'yum install freenx' and so if i am not wrong I actually install freenx 0.5.0-12 or something.... but i think ya shd be -12. Ok... so after i install freenx through yum. I follow what's on http://wiki.centos.org/FreeNX I --adduser and --passwd etc. Then copy the /etc/nxserver/client_id*.key over to my NX Client on Windows. Initially all works out. The NX session starts and i can do what i want over this remote session, and i proceed with updating of the critical updates for other apps from yum. The problem comes after i do this, right after the yum update. I choose to reboot my server. I reboot the server over the NX remote session. By going System -> Log Off -> Reboot. The NX Client's Window automatically closed (in quite a violent way with error msg). Then the server reboot. After the reboot, I try to reconnect to Server again using NX. But this time it fails with the following message. ===================================================================================NX> 203 NXSSH running with pid: 5940 NX> 285 Enabling check on switch command NX> 285 Enabling skip of SSH config files NX> 285 Setting the preferred NX options NX> 200 Connected to address: 192.168.1.5 on port: 22 NX> 202 Authenticating user: nx NX> 208 Using auth method: publickey HELLO NXSERVER - Version 1.5.0-60-SVN OS (GPL) NX> 105 hello NXCLIENT - Version 1.5.0 NX> 134 Accepted protocol: 1.5.0 NX> 105 SET SHELL_MODE SHELL NX> 105 SET AUTH_MODE PASSWORD NX> 105 login NX> 101 User: root NX> 102 Password: NX> 103 Welcome to: XQSVR200611 user: root NX> 105 listsession --user="root" --status="suspended,running" --geometry="1280x1024x32+render+fullscreen" --type="unix-gnome" NX> 127 Sessions list of user 'root' for reconnect: Display Type Session ID Options Depth Screen Status Session Name ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------ NX> 148 Server capacity: not reached for user: root NX> 105 startsession --link="lan" --backingstore="1" --nodelay="1" --encryption="1" --cache="32M" --images="64M" --media="0" --session="XQSVR200611" --type="unix-gnome" --geometry="1280x994" --fullscreen="1" --kbtype="pc102/en_US" --screeninfo="1280x1024x32+render+fullscreen" NX> 1000 NXNODE - Version 1.5.0-60-SVN OS (GPL) NX> 700 Session id: XQSVR200611-1000-1279B1D659A32AEF7AA88D7C50CA5619 NX> 705 Session display: 1000 NX> 703 Session type: unix-gnome NX> 701 Proxy cookie: 64b824b7aa9edb0a55c6e220710fba3c NX> 702 Proxy IP: 127.0.0.1 NX> 706 Agent cookie: 64b824b7aa9edb0a55c6e220710fba3c NX> 704 Session cache: unix-gnome NX> 707 SSL tunneling: 1 NX> 1009 Session status: starting NX> 710 Session status: running NX> 1002 Commit NX> 105 /usr/bin/nxserver: line 1190: 6719 Terminated sleep $AGENT_STARTUP_TIMEOUT NX> 1006 Session status: running NX> 596 Session startup failed. NX> 1004 Error: NX Agent exited with exit status 1. Can't open /var/lib/nxserver/db/running/sessionId{1279B1D659A32AEF7AA88D7C50CA5619}: No such file or directory. mv: cannot stat `/var/lib/nxserver/db/running/sessionId{1279B1D659A32AEF7AA88D7C50CA5619}': No such file or directory NX> 1006 Session status: closed NX> 1001 Bye. bye Killed by signal 15. I really do not know what's wrong. When i try to connect back locally at my server. The GNOME UI is gone! I am now left with only the console logon menu. This same problem happens everytime, even with CentOS 4.4 recently. (In the past, ard DEC 2006, I did the exact same thing on my CentOS 4.4 Server, it works without any problem EVEN with the same violent exiting way, I have never have a problem connecting back to the server. But recently after i failed my installation of CentOS 5 and go back to CentOS 4.4, the problem starts to occur like what i have mentioned. And I really did what was written on the wiki, nothing i have done now is different from what i did in the past.) Please, and sincerely please. Guys, if you all know what's wrong please tell me, how should I solve it? Did I miss out something? like installing of NX Node or NX Client on the server etc? Well explained or guide is really appreciated. Thanks, really Thank You.
Tim Wunder
2007-Apr-25 10:48 UTC
[CentOS] Having trouble with FreeNX, Need help to make it work perfectly
First step, get X working on the local login first. If there is no running X server, FreeNX has nothing to connect to. HTH, Tim On Wednesday 25 April 2007 12:48:31 am Kai Yang Tay wrote:> Hi thanks for the reply i am really grateful if you can tell me how to > make FreeNX work like charm. > > I am really stuck with it, and after reinstalling the server is > definitely pissing off my boss. > > Please help me thanks. > > ==========================> > Please let me review how my FreeNX was screwed up. > > After i fresh install my CentOS 5, I 'yum install freenx' and so if i > am not wrong > I actually install freenx 0.5.0-12 or something.... but i think ya shd be > -12. > > Ok... so after i install freenx through yum. I follow what's on > http://wiki.centos.org/FreeNX > > I --adduser and --passwd etc. Then copy the > /etc/nxserver/client_id*.key over to my NX Client on Windows. > > Initially all works out. The NX session starts and i can do what i > want over this remote session, and i proceed with updating of the > critical updates for other apps from yum. > > The problem comes after i do this, right after the yum update. > > I choose to reboot my server. I reboot the server over the NX remote > session. By going System -> Log Off -> Reboot. > The NX Client's Window automatically closed (in quite a violent way > with error msg). Then the server reboot. > After the reboot, I try to reconnect to Server again using NX. But > this time it fails with the following message. > > ==========================================================================>========= NX> 203 NXSSH running with pid: 5940 > NX> 285 Enabling check on switch command > NX> 285 Enabling skip of SSH config files > NX> 285 Setting the preferred NX options > NX> 200 Connected to address: 192.168.1.5 on port: 22 > NX> 202 Authenticating user: nx > NX> 208 Using auth method: publickey > HELLO NXSERVER - Version 1.5.0-60-SVN OS (GPL) > NX> 105 hello NXCLIENT - Version 1.5.0 > NX> 134 Accepted protocol: 1.5.0 > NX> 105 SET SHELL_MODE SHELL > NX> 105 SET AUTH_MODE PASSWORD > NX> 105 login > NX> 101 User: root > NX> 102 Password: > NX> 103 Welcome to: XQSVR200611 user: root > NX> 105 listsession --user="root" --status="suspended,running" > --geometry="1280x1024x32+render+fullscreen" --type="unix-gnome" > NX> 127 Sessions list of user 'root' for reconnect: > > Display Type Session ID Options Depth Screen Status Session Name > ------- ---------------- -------------------------------- -------- > ----- -------------- ----------- ------------------------------ > > > NX> 148 Server capacity: not reached for user: root > NX> 105 startsession --link="lan" --backingstore="1" --nodelay="1" > --encryption="1" --cache="32M" --images="64M" --media="0" > --session="XQSVR200611" --type="unix-gnome" --geometry="1280x994" > --fullscreen="1" --kbtype="pc102/en_US" > --screeninfo="1280x1024x32+render+fullscreen" > > NX> 1000 NXNODE - Version 1.5.0-60-SVN OS (GPL) > NX> 700 Session id: XQSVR200611-1000-1279B1D659A32AEF7AA88D7C50CA5619 > NX> 705 Session display: 1000 > NX> 703 Session type: unix-gnome > NX> 701 Proxy cookie: 64b824b7aa9edb0a55c6e220710fba3c > NX> 702 Proxy IP: 127.0.0.1 > NX> 706 Agent cookie: 64b824b7aa9edb0a55c6e220710fba3c > NX> 704 Session cache: unix-gnome > NX> 707 SSL tunneling: 1 > NX> 1009 Session status: starting > NX> 710 Session status: running > NX> 1002 Commit > NX> 105 /usr/bin/nxserver: line 1190: 6719 Terminated sleep > $AGENT_STARTUP_TIMEOUT > NX> 1006 Session status: running > NX> 596 Session startup failed. > NX> 1004 Error: NX Agent exited with exit status 1. > Can't open > /var/lib/nxserver/db/running/sessionId{1279B1D659A32AEF7AA88D7C50CA5619}: > No such file or directory. > mv: cannot stat > `/var/lib/nxserver/db/running/sessionId{1279B1D659A32AEF7AA88D7C50CA5619}': > No such file or directory > NX> 1006 Session status: closed > NX> 1001 Bye. > bye > Killed by signal 15. > > I really do not know what's wrong. When i try to connect back locally > at my server. The GNOME UI is gone! I am now left with only the > console logon menu. This same problem happens everytime, even with > CentOS 4.4 recently. > > (In the past, ard DEC 2006, I did the exact same thing on my CentOS > 4.4 Server, it works without any problem EVEN with the same violent > exiting way, I have never have a problem connecting back to the > server. But recently after i failed my installation of CentOS 5 and go > back to CentOS 4.4, the problem starts to occur like what i have > mentioned. And I really did what was written on the wiki, nothing i > have done now is different from what i did in the past.) > > Please, and sincerely please. Guys, if you all know what's wrong > please tell me, how should I solve it? > Did I miss out something? like installing of NX Node or NX Client on > the server etc? > > Well explained or guide is really appreciated. Thanks, really Thank You. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20070425/3666fb99/attachment-0003.sig>
Kai Yang Tay
2007-Apr-26 01:08 UTC
[CentOS] Having trouble with FreeNX, Need help to make it work perfectly
Hi Let's assume i give up trying to get X working. The reason is that even after i typed 'startx' nothing is working, a serious fatal error message was shown. How about from fresh installed CentOS 5? How should i do it? - Signed - Tay Kai Yang