SOS: PXES + NX/XDM

I have a small lan with 1 X server + 7 clients.  I'm using PXES 1.1
to connect to the X Server which is running Fedora Core 4.

Previously, I was using PXES with XDM but now I switched over to
freenx + nxclient on the PXES host. In either case, the X Sessions
will always be killed for some reason.

Whenever I use XDM, this is the only error message in the log files:

Feb 13 10:53:32 SERVER__X dbus: avc:  1 AV entries and 1/512 buckets used, longest chain length 1
Feb 13 10:53:32 SERVER__X gdm[30539]: gdm_slave_xioerror_handler: Fatal X error - Restarting host231.domain.com:0

On the PXES client, the client just reboots.

Whenever I use the NX version, this is the only trace in the log file:

Feb 16 16:53:03 SERVER__X sshd(pam_unix)[8117]: session opened for user USER by (uid=0)
Feb 16 16:53:03 SERVER__X sshd(pam_unix)[8117]: session closed for user USER

In other words, the user logged in with NX and got immediately kicked
out. This is a special case, usually it is not so quick to kick a user
out, maybe once every hour or 2 hours. At least with this version,
the user's session is preserved but it appears that with the NX-client
version, the users are kicked out more frequently.

I have no trace of what is going on in the freenx server logs.

[email protected]'s password:
NX> 1000 NXNODE - Version 1.4.0-44 OS (GPL)
NX> 700 Session id: SERVER__X.domain.com-1005-098CDBCBF25435A31DAD864637944057
NX> 705 Session display: 1005
NX> 703 Session type: unix-gnome
NX> 701 Proxy cookie: ff3826ea27513f0e2454861b173c6b16
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: 3ab28ece71db327a7ff6a8c9e807a1d3
NX> 704 Session cache: unix-gnome
NX> 707 SSL tunneling: 1
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1009 Session status: terminating
NX> 1006 Session status: closed
NX> 1001 Bye.


I would like further help in how I can debug where the problem is? Do
you have any suggestions? I am thinking that I can route the syslog
output of the clients to a log server, but I don't know how to turn
on syslog on the clients.

Hovanes


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642