[FreeNX-kNX] Have to attempt to login multiple times to login.

[olaf]

Hi!

(English is not my mother language, but I will try:)

I have the same problem with my freeNX-Server (OpenSuse 11.2, 32bit).
I'm testing with this server since a few weeks. All works fine, but every time 
after I reboot the server I have to login again and again without success, and 
after about ~4-10 tries the login will be succesful.
Some IT-technical said to me that there is a problem with the nx-startup after 
reboot, so it will initialized only by trying to login (?)

If anyone is interested in debugging this issue, I can look for the versions 
and other needed things.

Bye
Olaf


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