[spacecrusader]

Hello,

Installed FreeNX via http://fedoranews.org/contributors/rick_stout/freenx/
and
http://wiki.centos.org/FreeNX Tutorials.

Installed the windows client, did the settings and copied the key. I login, it authenticates, then it says Session Startup failed.

hered the error:



NX> 203 NXSSH running with pid: 3960
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.101 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
which: no xauth in (/usr/local/bin:/bin:/usr/bin)
HELLO NXSERVER - Version 1.5.0-50-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:
which: no xauth in (/usr/local/bin:/bin:/usr/bin)
NX> 103 Welcome to: spacecrusader user: root
NX> 105 listsession --user="root" --status="suspended,running" --geometry="1024x768x32+render" --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="isdn" --backingstore="1" --nodelay="1" --encryption="1" --cache="8M" --images="32M" --media="0" --session="server" --type="unix-gnome" --geometry="1024x740" --kbtype="pc102/en_US" --screeninfo="1024x740x32+render"

NX> 1000 NXNODE - Version 1.5.0-50-SVN OS (GPL)
NX> 700 Session id: spacecrusader-1000-97AAC3708D78F37ED86C66D00B432EEF
NX> 705 Session display: 1000
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: e891926c028908d4322860e293afc0c1
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: e891926c028908d4322860e293afc0c1
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 105 /usr/bin/nxserver: line 1077: 7574 Terminated sleep $AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
Can't open /var/lib/nxserver/db/running/sessionId{97AAC3708D78F37ED86C66D00B432EEF}: No such file or directory.
NX> 1006 Session status: closed
mv: cannot stat `/var/lib/nxserver/db/running/sessionId{97AAC3708D78F37ED86C66D00B432EEF}': No such file or directory
Killed by signal 15.


Any idea how to fix this?

[stubbe]

have you switch on the "enable remote desktop" or something like that on Gnome? Since I've tested VNC and it kept failing turn out that the default setting for the remote desktop access is off.

[ChadJorgenson]

FreeNx isn't really anything like VNC; or at least, it's not from a setup standpoint. The client itself does the enabling of the remote desktop. I'm running into this too, and to remedy it I tried re-run the setup again and it's failing on some dependencies. My guess is that yours will have the same thing show up if you re-run setup:

[root@linux~]# nxsetup --install --clean --purge --override
------> It is recommended that you use the NoMachine key for
easier setup. If you answer "y", FreeNX creates a custom
KeyPair and expects you to setup your clients manually.
"N" is default and uses the NoMachine key for installation.

Do you want to use your own custom KeyPair? [y/N] yRemoving special user "nx" ...done
Removing session database ...done
Removing logfile ...done
Removing home directory of special user "nx" ...done
Removing configuration files ...done
Setting up /etc/nxserver ...done
Generating public/private dsa key pair.
Your identification has been saved in /etc/nxserver/users.id_dsa.
Your public key has been saved in /etc/nxserver/users.id_dsa.pub.
The key fingerprint is:
<garbage removed>
Setting up /var/lib/nxserver/db ...done
Setting up /var/log/nxserver.log ...done
Setting up special user "nx" ...done
Setting up known_hosts and authorized_keys2 ...Unique key generated; your users must install

/var/lib/nxserver/home/.ssh/client.id_dsa.key

on their computers.
done
Setting up permissions ...done

----> Testing your nxserver configuration ...
Error: Invalid value "APPLICATION_LIBRARY_PRELOAD=/usr/lib/libX11.so.6.2:/usr/lib/libXext.so.6.4:/usr/lib/libXcomp.so.1:/usr/lib/libXcompext.so.1:/usr/lib/libXrender.so.1.2"
Warning: Invalid value "COMMAND_START_KDE=/usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/startkde"
Users will not be able to request a KDE session.
Warning: Invalid value "COMMAND_START_GNOME=/usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/gnome-session"
Users will not be able to request a Gnome session.
Warning: Invalid value "COMMAND_START_CDE=cdwm"
Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA.
Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use SAMBA.
Error: Could not find 1.5.0 version string in nxagent. NX 1.5.0 backend is needed for this version of FreeNX.

Errors occured during config check.
Please correct the configuration file.



But wow.. I have no idea there. Anyone?

[Predseda3D]

Originally Posted by spacecrusader

Hello,

Installed FreeNX via http://fedoranews.org/contributors/rick_stout/freenx/
and
http://wiki.centos.org/FreeNX Tutorials.

Installed the windows client, did the settings and copied the key. I login, it authenticates, then it says Session Startup failed.

hered the error:

NX> 105 /usr/bin/nxserver: line 1077: 7574 Terminated sleep $AGENT_STARTUP_TIMEOUT
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
Can't open /var/lib/nxserver/db/running/sessionId{97AAC3708D78F37ED86C66D00B432EEF}: No such file or directory.
NX> 1006 Session status: closed
mv: cannot stat `/var/lib/nxserver/db/running/sessionId{97AAC3708D78F37ED86C66D00B432EEF}': No such file or directory
Killed by signal 15.


Any idea how to fix this?

Hi,

freenx 0.5.0
nxagent 1.5.0
libxcomp1 1.5.0
libxcompext1 1.5.0
nxlibs 1.5.0

And everything work great for me. I tested this with NX Client 2.0.0-98 and NX Client 1.5.0-138.
I tested it with FreeNX 0.4.4 and 0.4.5 and work good too.

If somebody have problem with NX Clients versions 2.0.0 and FreeNX 0.4.x or 0.5.0, you can read about some solution here:
http://openfacts.berlios.de/index-en...roblem_Solving

or here:
http://wiki.debian.org/freenx

or here:
http://gentoo-wiki.com/Talk:HOWTO_Fr....4.x_and_0.5.0

Hope that will help.

Predseda

[Bill Kress]

I notice the exact same problem as the original poster running CentOS 4.3.

It acts like the startsession command may be failing--all the SSL stuff seems to be working fine.

I tried Gnome, KDE and "Default X startup script", none of them worked.

Any other ideas would be appreciated.

[TrevorB]

Originally Posted by Bill Kress

I notice the exact same problem as the original poster running CentOS 4.3.

It acts like the startsession command may be failing--all the SSL stuff seems to be working fine.

I tried Gnome, KDE and "Default X startup script", none of them worked.

Any other ideas would be appreciated.

Have you set ENABLE_2_0_0_BACKEND="1" in your /etc/nxserver/node.conf file?

Trevor B

[EonStrife]

I'm using Vista connecting to CentOS, with nomachine on vista side and freenx on CentOS side, with the desktop is Gnome.

After I installed the nomachine and freenx, it works, I can use it for few days. Then, suddenly I got this error,

===
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
Can't open /var/lib/nxserver/db/running/sessionId{647C4B6666165157169C354D3A4F1648}: No such file or directory.
mv: cannot stat `/var/lib/nxserver/db/running/sessionId{647C4B6666165157169C354D3A4F1648}': No such file or directory
NX> 1006 Session status: closed
Exited with status 0. User pressed Ok.
===

and I am stuck in the splash screen. That means, I can't go to the desktop as root.

Then, by using PuTTY, I created a new user, and strangely though, the new user doesn't get this error and can go to the desktop.

In the beginning, I was trying to add new user, but I couldn't. After searching around, I found that it's caused by the autofs. Thus, I played around starting and stopping the autofs, and yes, I could add new user. When I first login as the new user, I'm required to input passphrase for the ssh key or rsa or soemthing like that. After that, I couldn't get to the desktop anymore as the root.

This is portion of the bash history, the command I issued around the time I messed up :

===
useradd aaa
useradd --help
useradd abc
passwd aaa
useradd --help
useradd -d /home/aaaa/ -p aaaaaa aaa
which useradd
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
userdel --help
userdel aaa
passwd aaa
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
cd /home/
ls
rmdir --help
cd aaa
ls
del --help
delfile --help
cd \.
cd /.
cd /home/
rm -r /home/aaa/
ls
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs reload
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs start
/etc/rc.d/init.d/autofs stop
/etc/rc.d/init.d/autofs start
ls
/etc/rc.d/init.d/autofs stop
exit
ypcat
ypcat group
group
grouplist
groupls
groups
users
uname
uname -s -n -m -r
id
whoami
w root
w
ps
ps
ps -f
ps -a
===

Thanks.