<br><tt><font size=2>Freek de Kruijf <f.de.kruijf@gmail.com> wrote
on 05/04/2010 23:34:05:<br>
<br>
> Op maandag 5 april 2010 17:23:38 schreef Morgan Cox:<br>
> > Hi.<br>
> > <br>
> > This is carrying on from<br>
> > <br>
> > </font></tt><a href="http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-wo"><tt><font size=2>http://old.nabble.com/Arch-Linux---After-reboot-have-to-login-4-times-to-wo</font></tt></a><tt><font size=2><br>
> > rk-------%28every-single-time%29-to26482511.html<br>
> > <br>
> > I have removed all nx packages, removed all trace of the nx user,<br>
> > recompiled the nx-common, nxserver and freenx packages and re-installed<br>
> > them.<br>
> > <br>
> > This is still occurring...<br>
> <br>
> This is a recurring issue and the solution can be found in the archive.
If I <br>
> recall correctly, it has to do with files /tmp/.n* remaining in the
/tmp <br>
> directory. Delete these files and you are OK.</font></tt>
<br>
<br>
<br><tt><font size=2>That's exactly what it isn't !!</font></tt>
<br>
<br><tt><font size=2>The logic uses the presence of these files to determine
the next free display.</font></tt>
<br>
<br><tt><font size=2>If any of the lock files exists, then the display
number is incremented successively</font></tt>
<br><tt><font size=2>until none exist for that display, at which point
that display is selected.</font></tt>
<br>
<br><tt><font size=2>This could cause probems with simultaneous logins,
but not the first four every time.</font></tt>
<br>
<br><tt><font size=2>In addition, most distros use the freenx-server service
to remove such files at </font></tt>
<br><tt><font size=2>service start, though Suse never seem to bothereven
with that.</font></tt>
<br>
<br><tt><font size=2>The logic also checks in turn for</font></tt>
<br>
<br><tt><font size=2> AGENT_DISPLAY=$SESS_DISPLAY+6000</font></tt>
<br><tt><font size=2> SAMBA_DISPLAY=$SESS_DISPLAY+3000</font></tt>
<br><tt><font size=2> MEDIA_DISPLAY=$SESS_DISPLAY+7000</font></tt>
<br><tt><font size=2> CUPS_DISPLAY=$SESS_DISPLAY+9000</font></tt>
<br>
<br><tt><font size=2>and then increments the display again if the agent
display, or samba media or cups ports</font></tt>
<br><tt><font size=2>are in use.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>I think the issue is to do with loading shared libraries,
which only needs to be done </font></tt>
<br><tt><font size=2>once, the first time.</font></tt>
<br>
<br><tt><font size=2>There is though, a dearth of detailed information
from the victims regarding</font></tt>
<br>
<br><tt><font size=2> 32 or 64 bit NX-libraries
or both</font></tt>
<br><tt><font size=2> library versions</font></tt>
<br><tt><font size=2> FreeNx versions</font></tt>
<br><tt><font size=2> Which distro /
version</font></tt>
<br>
<br><tt><font size=2>I would expect the issue to re-occur, without a reboot
if the machine was left </font></tt>
<br><tt><font size=2>without the NX libraries being used for some time
and thus getting flushed out, </font></tt>
<br><tt><font size=2>but there is little detailed reporting, just me-toos.</font></tt>
<br>
<br><tt><font size=2>Yossarian seems to complain about every two months
when he reboots, but he doesn't seem </font></tt>
<br><tt><font size=2>too keen to try any testing or tell us about versions.</font></tt>
<br>
<br>
<br><tt><font size=2>I know quite a few charities etc rely on Freenx, so
it would be nice to fix this annoyance.</font></tt>
<br>
<br><tt><font size=2>Anyone with this issue could helpfully change . .
.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>--- /usr/bin/nxnode 2008-12-04 13:31:37.000000000
+0000</font></tt>
<br><tt><font size=2>+++ /usr/bin/nxnode.000 2010-04-06
14:35:21.000000000 +0100</font></tt>
<br><tt><font size=2>@@ -543,7 +543,7 @@</font></tt>
<br><tt><font size=2> NODE_FAILED=""</font></tt>
<br><tt><font size=2> if [ $NODE_AGENT_EXIT_STATUS
-ne 0 ]</font></tt>
<br><tt><font size=2> then</font></tt>
<br><tt><font size=2>-
echo "NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot
set SESSION_LOG_CLEAN=0 in node.conf and investigate \"$USER_FAKE_HOME/.nx/F-C-$sess_id/session\".
You might also want to try: ssh -X myserver; $PATH_BIN/nxnode --agent to
test the basic functionality. Session log follows:"</font></tt>
<br><tt><font size=2>+
echo "NX> 1004 Error: NX Agent exited with exit status $NODE_AGENT_EXIT_STATUS.
To troubleshoot set SESSION_LOG_CLEAN=0 in node.conf and investigate \"$USER_FAKE_HOME/.nx/F-C-$sess_id/session\".
You might also want to try: ssh -X myserver; $PATH_BIN/nxnode --agent to
test the basic functionality. Session log follows:"</font></tt>
<br><tt><font size=2>
cat "$USER_FAKE_HOME/.nx/C-$sess_id/session" 1>&2</font></tt>
<br><tt><font size=2>
NODE_FAILED="failed"</font></tt>
<br><tt><font size=2> fi</font></tt>
<br>
<br>
<br><tt><font size=2>. . . and then tell us what the real error code from
nxagent is.</font></tt>
<br>
<br><tt><font size=2>Note the session log mentioned won't actually exist
for being dumped.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>cb</font></tt>
<br><tt><font size=2><br>
> <br>
> -- <br>
> fr.gr.<br>
> <br>
> Freek de Kruijf<br>
> ________________________________________________________________<br>
> Were you helped on this list with your FreeNX
problem?<br>
> Then please write up the solution in the FreeNX Wiki/FAQ:<br>
> <br>
> </font></tt><a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ"><tt><font size=2>http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</font></tt></a><tt><font size=2><br>
> <br>
> Don't forget to check the NX Knowledge
Base:<br>
> </font></tt><a href=http://www.nomachine.com/kb/><tt><font size=2>http://www.nomachine.com/kb/</font></tt></a><tt><font size=2>
<br>
> <br>
> ________________________________________________________________<br>
> FreeNX-kNX mailing list --- FreeNX-kNX@kde.org<br>
> </font></tt><a href="https://mail.kde.org/mailman/listinfo/freenx-knx"><tt><font size=2>https://mail.kde.org/mailman/listinfo/freenx-knx</font></tt></a><tt><font size=2><br>
> ________________________________________________________________<br>
</font></tt>