Comments on: FreeNX failure in Fedora 9 + 10 default setup SOLVED http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html Linux Stuff, IT News, and Open Source Software Tue, 07 Feb 2012 18:43:40 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: 5parky http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-2796 5parky Tue, 31 Jan 2012 18:55:45 +0000 http://206.196.110.11/?p=32#comment-2796 I had the same problem you did using the windows client on an oneiric server. I chmod'd the directory that the session ID was in (/var/lib/nxserver/db/running/) That fixed the problem. I had the same problem you did using the windows client on an oneiric server. I chmod’d the directory that the session ID was in (/var/lib/nxserver/db/running/)

That fixed the problem.

]]> By: mattb http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-2034 mattb Wed, 03 Mar 2010 23:31:20 +0000 http://206.196.110.11/?p=32#comment-2034 Your logs show 'NX> 705 Session display: 1005'. So you're probably okay. Try using the free nomachine client and see if you have the same error. Let me know! Your logs show ‘NX> 705 Session display: 1005′. So you’re probably okay. Try using the free nomachine client and see if you have the same error. Let me know!

]]> By: bill http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-2033 bill Tue, 02 Mar 2010 16:09:05 +0000 http://206.196.110.11/?p=32#comment-2033 I can connect using the nomachine nx client, but not qtnx. so I think the problem is there... I can connect using the nomachine nx client, but not qtnx. so I think the problem is there…

]]> By: bill http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-2032 bill Tue, 02 Mar 2010 16:01:23 +0000 http://206.196.110.11/?p=32#comment-2032 I'm having similar issues w/ Fedora 12 (on both the client and server). The end of the nxserver.log looks like: server_nxnode_echo: NX> 702 Proxy IP: 192.168.50.10 server_nxnode_echo: NX> 706 Agent cookie: 2d117415220e087ba69098340160bb04 server_nxnode_echo: NX> 704 Session cache: unix-gnome server_nxnode_echo: NX> 707 SSL tunneling: 1 nxnode_reader: NX> 1009 Session status: starting NX> 1009 Session status: starting nxnode_reader: NX> 710 Session status: running NX> 710 Session status: running nxnode_reader: NX> 1002 Commit NX> 1002 Commit server_nxnode_echo: NX> 1009 Session status: starting nxnode_reader: NX> 1006 Session status: running NX> 1006 Session status: running server_nxnode_echo: NX> 710 Session status: running server_nxnode_echo: NX> 1002 Commit NX> 105 session_status 22D6D471CE1988CF4B6BFEC14B4347C7 Running bye Bye NX> 999 Bye server_nxnode_echo: NX> 1006 Session status: running The end of the qtnx output looks like: NX> 705 Session display: 1005 NX> 703 Session type: unix-gnome NX> 701 Proxy cookie: 2d117415220e087ba69098340160bb04 NX> 702 Proxy IP: 192.168.50.10 NX> 706 Agent cookie: 2d117415220e087ba69098340160bb04 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 stdin> bye stdout> bye stderr> /usr/libexec/nx/nxserver: line 1585: 14420 Terminated sleep $AGENT_STARTUP_TIMEOUT Bye NX> 999 Bye NX> 1006 Session status: running Starting NX proxy NX_COMMFD=23Process started stderr> Segmentation fault (seg fault after i get a gui pop up saying it can't connect to the session) I’m having similar issues w/ Fedora 12 (on both the client and server).

The end of the nxserver.log looks like:
server_nxnode_echo: NX> 702 Proxy IP: 192.168.50.10
server_nxnode_echo: NX> 706 Agent cookie: 2d117415220e087ba69098340160bb04
server_nxnode_echo: NX> 704 Session cache: unix-gnome
server_nxnode_echo: NX> 707 SSL tunneling: 1
nxnode_reader: NX> 1009 Session status: starting
NX> 1009 Session status: starting
nxnode_reader: NX> 710 Session status: running
NX> 710 Session status: running
nxnode_reader: NX> 1002 Commit
NX> 1002 Commit
server_nxnode_echo: NX> 1009 Session status: starting
nxnode_reader: NX> 1006 Session status: running
NX> 1006 Session status: running
server_nxnode_echo: NX> 710 Session status: running
server_nxnode_echo: NX> 1002 Commit
NX> 105 session_status 22D6D471CE1988CF4B6BFEC14B4347C7 Running
bye
Bye
NX> 999 Bye
server_nxnode_echo: NX> 1006 Session status: running

The end of the qtnx output looks like:
NX> 705 Session display: 1005
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: 2d117415220e087ba69098340160bb04
NX> 702 Proxy IP: 192.168.50.10
NX> 706 Agent cookie: 2d117415220e087ba69098340160bb04
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
stdin> bye
stdout> bye
stderr> /usr/libexec/nx/nxserver: line 1585: 14420 Terminated sleep $AGENT_STARTUP_TIMEOUT
Bye
NX> 999 Bye
NX> 1006 Session status: running
Starting NX proxy
NX_COMMFD=23Process started
stderr>
Segmentation fault

(seg fault after i get a gui pop up saying it can’t connect to the session)

]]> By: John http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-2018 John Tue, 26 Jan 2010 04:15:51 +0000 http://206.196.110.11/?p=32#comment-2018 Thanks for the info, much appreciated. I was writing to say that I could not get connections to work, regardless of what I tried. I then realised that I had left my various test clients set to use unencrypted connections and that was the problem. Change the base display port and leave traffic encrypted (and I've lost track of the other many changes made prior to doing that :-( ). Really didn't expect this level of frustration given that I have had almost no issues with nx under Centos which I use heavily at work. That's the linux world for you. Cheers. Thanks for the info, much appreciated. I was writing to say that I could not get connections to work, regardless of what I tried. I then realised that I had left my various test clients set to use unencrypted connections and that was the problem. Change the base display port and leave traffic encrypted (and I’ve lost track of the other many changes made prior to doing that :-( ). Really didn’t expect this level of frustration given that I have had almost no issues with nx under Centos which I use heavily at work. That’s the linux world for you. Cheers.

]]> By: mattb http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-2008 mattb Fri, 08 Jan 2010 08:36:00 +0000 http://206.196.110.11/?p=32#comment-2008 You're most welcome, thank you for visiting! You’re most welcome, thank you for visiting!

]]> By: Josh http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-1995 Josh Sun, 03 Jan 2010 20:06:52 +0000 http://206.196.110.11/?p=32#comment-1995 Wow thanks so much, i have been poring over the logs for this nx problem..i have two desktops one running KDE and the other running XFCE and the XFCE one has been having the problems... first the ~/.Xauthority was owned by root, and finally i found this page that described my error exactly and after setting the ‘DISPLAY_BASE=1001′ it worked! thanks Wow thanks so much, i have been poring over the logs for this nx problem..i have two desktops one running KDE and the other running XFCE and the XFCE one has been having the problems…
first the ~/.Xauthority was owned by root, and finally i found this page that described my error exactly and after setting the ‘DISPLAY_BASE=1001′ it worked!

thanks

]]> By: Matt http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-1767 Matt Wed, 20 May 2009 00:52:28 +0000 http://206.196.110.11/?p=32#comment-1767 I've used Mac, Windows, and Linux client. So far as I can tell they all work well, but the Mac client requires X Windows to be installed and the Linux client sometimes incorrectly maps the keys. I’ve used Mac, Windows, and Linux client. So far as I can tell they all work well, but the Mac client requires X Windows to be installed and the Linux client sometimes incorrectly maps the keys.

]]> By: Christian Gutierrez http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-1766 Christian Gutierrez Tue, 19 May 2009 23:57:17 +0000 http://206.196.110.11/?p=32#comment-1766 Hi i installed freenx on Fedora 10 x86_64, and i can't connect a linux client, at the moment i don't have a windows machine; have anyone probed the connection with a linux client?. Hi i installed freenx on Fedora 10 x86_64, and i can’t connect a linux client, at the moment i don’t have a windows machine; have anyone probed the connection with a linux client?.

]]> By: vldo http://www.savelono.com/linux/freenx-failure-in-fedora-9-10-default-setup.html#comment-1765 vldo Tue, 12 May 2009 14:18:40 +0000 http://206.196.110.11/?p=32#comment-1765 I installed freenx on Fedora 11 and had similar problem. So i copied node.conf.sample to node.conf without changing anything and it started working (everything in node.conf is commented) I installed freenx on Fedora 11 and had similar problem. So i copied node.conf.sample to node.conf without changing anything and it started working (everything in node.conf is commented)

]]>