[FreeNX-kNX] maybe timing problems with nfs home and KDE NXSession? WAS: problems to log in

Fri Jan 12 16:27:36 UTC 2007

The part you should be investigating is this:
NX> 1004 Error: NX Agent exited with exit status 1.

I had a problem in this area a while back and IIRC this message is a little 
misleading and could be caused by many things. There's a brief section on how 
to debug this sort of thing in the wiki:
http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ/Server

Look for the section 'What can I do if nxagent won't start or I get a "NX>" 
protocol error?' about half way down the page. In essence it's a quick guide 
to manually doing what the nx client and server do so you can see what stage 
it dies at.

On Friday 12 January 2007 15:55, Sebastian Reitenbach wrote:
> Hi Emmanuel,
>
> User Support for FreeNX Server and kNX Client <freenx-knx at kde.org> wrote:
> > .nfsXXXXXXXx are files asked to be removed, but still in use by another
>
> process, so the nfs server renames the file "foobar" to ".nfsXXXXXXXXX" and
> when the last fd will be closed, ".nfsXXXXXXXX" will disappear.
>
> > you can try to change the .nx directory to set ip in an non-nfs FS, for
>
> example USER_FAKE_HOME=/var/tmp/$USER-nx in your node.conf
>
> thanks a lot for that hint. No clue why I haven't found out about that by
> myself. Nevertheless, now with the USER_FAKE_HOME set, I am always unable
> to log in.
> The directory gets created, the .nx subdirectory too, but the behaviour is
> the same, with a chance of 66% I am unable to login. Well, now without the
> .nfs error message.
>
> with SESSION_LOG_CLEAN=0 set, I get the following message when the
> connection fails:
> NX> 707 SSL tunneling: 0
> NX> 1004 Error: NX Agent exited with exit status 1.
> NX> 1006 Session status: closed
> NX> 105 mv: target
> `/tmp/user-nx/.nx/F-C-server3-1098-A195278126698704E3393F565EB90E4D/' is
> not a directory: No such file or directory
> NX> 596 Session startup failed.
>
> unfortunately the file F-C-server3-1098-A195278126698704E3393F565EB90E4D is
> not there.
>
> kind regards
> Sebastian
>
> > Emmanuel
> >
> > Le vendredi 12 janvier 2007 10:10, Sebastian Reitenbach a écrit :
> > > Hi all,
> > >
> > > meanwhile I observed the following:
> > > an other user account tried to log in, but it it did not worked, with a
> > > different error message:
> > >
> > > NX> 1000 NXNODE - Version 1.5.0-50 OS (GPL)
> > > NX> 700 Session id: server3-1098-4C65B1DFE60A64FEFBA3352C9A81CB7F
> > > NX> 705 Session display: 1098
> > > NX> 703 Session type: unix-kde
> > > NX> 701 Proxy cookie: fd11aa90481a5a48a0567cef8971b95f
> > > NX> 702 Proxy IP: 10.10.10.33
> > > NX> 706 Agent cookie: fd11aa90481a5a48a0567cef8971b95f
> > > NX> 704 Session cache: unix-kde
> > > NX> 707 SSL tunneling: 0
> > > NX> 1004 Error: NX Agent exited with exit status 1.
> > > NX> 1006 Session status: closed
> > > NX> 105 NX> 596 Session startup failed.
> > > rm: cannot remove directory
> > > `/home/user1/.nx/C-server3-1098-4C65B1DFE60A64FEFBA3352C9A81CB7F/':
> > > Directory not empty
> > >
> > > there was no problem to log in.
> > >
> > >
> > > -- NX SERVER START: -c /usr/bin/nxserver - ORIG COMMAND=
> > > HELLO NXSERVER - Version 1.5.0-50 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: user3
> > > NX> 102 Password:
> > > Info: Auth method: passdb ssh
> > > NX> 103 Welcome to: server3 user: user3
> > > NX> 105
> > > listsession --user="user3" --status="suspended,running"
> > > --geometry="1280x1024x16+render+fullscreen" --type="unix-kde"
> > > NX> 127 Sessions list of user 'user3' for reconnect:
> > >
> > > Display Type             Session ID                       Options 
> > > Depth Screen         Status      Session Name
> > > ------- ---------------- -------------------------------- --------
> > > ----- -------------- ----------- ------------------------------
> > >
> > >
> > > NX> 148 Server capacity: not reached for user: user3
> > > NX> 105
> > > startsession --session="KDE" --type="unix-kde" --cache="8M"
> > > --images="32M" --link="lan" --kbtype="pc102/" --nodelay="1"
> > > --encryption="1"
> > > --backingstore="when requested" --geometry="1280x1024" --fullscreen="1"
> > > --media="0" --agent server="" --agent user=""
> > > agent password="******""  --screeninfo="1280x1024x16+render+fullscreen"
> > >
> > > &session=KDE&type=unix-kde&cache=8M&images=32M&link=lan&kbtype=pc102/&n
> > >o delay=1&
> > > encryption=1&backingstore=when
> > > requested&geometry=1280x1024&fullscreen=1 &media=0
> > > &agent server=&agent user=&agent
> > > password=******&screeninfo=1280x1024x16 +render+
> > > fullscreen&clientproto=1.5.0&user=user3&userip=192.168.0.47&uniqueid=78
> > >8 3CC8D0B3 1FC29D9EB28A6AFE967C0&display=1098&host=127.0.0.1
> > > user3 at 127.0.0.1's password:
> > > NX> 1000 NXNODE - Version 1.5.0-50 OS (GPL)
> > > NX> 700 Session id: server3-1098-7883CC8D0B31FC29D9EB28A6AFE967C0
> > > NX> 705 Session display: 1098
> > > NX> 703 Session type: unix-kde
> > > NX> 701 Proxy cookie: 9d41abe59ab8b8bb5659c9c39ab49994
> > > NX> 702 Proxy IP: 127.0.0.1
> > > NX> 706 Agent cookie: 9d41abe59ab8b8bb5659c9c39ab49994
> > > NX> 704 Session cache: unix-kde
> > > NX> 707 SSL tunneling: 1
> > > NX> 1004 Error: NX Agent exited with exit status 1.
> > > NX> 1006 Session status: closed
> > > NX> 105 NX> 596 Session startup failed.
> > > rm: cannot remove
> > > `/home/user3/.nx/C-server3-1098-7883CC8D0B31FC29D9EB28A6AFE967C0//.nfs0
> > >2 8548b400 00038e':
> > > Device or resource busy
> > >
> > > this happened about five times, then the login suddenly worked. On a
> > > second sever, where the home directories are not nfs mounted, this
> > > never did happen.
> > >
> > > when I make an lsof on the file .nfs028548b40000038e, then startkde and
> > > a handfull of other kde startup processes is using this file.
> > >
> > > unfortunately I cannot find the place where it tries to rm the .nfs...
> > > file, I assumed this is in the nxserver script.
> > >
> > > where Is the place where the nxserver tries to rm the .nfs file from
> > > the home directory? I think when I add a sleep before it, then it might
> > > work.
> > >
> > > kind regards
> > > Sebastian
> > >
> > >
> > > Sebastian Reitenbach <itlistuser at rapideye.de>, User Support for FreeNX
> > > Server
> > >
> > > and kNX Client <freenx-knx at kde.org> wrote:
> > > > Hi all,
> > > >
> > > > when I try to login with knx to an freenx server, below are the
> > > > messages
> > >
> > > from
> > >
> > > > the nxserver.log file. Others do not have a problem to login via knx.
> > > > nxserver --list do not show any running session for the user.
> > > > I exchanged my home directory, to make sure that is not the reason,
> > > > but
> > >
> > > still
> > >
> > > > the problem persists.
> > > >
> > > > any hint what I can do about that:
> > > >
> > > > kind regards
> > > > Sebastian
> > >
> > >      Were you helped on this list with your FreeNX problem?
> > >     Then please write up the solution in the FreeNX Wiki/FAQ:
> > >   http://openfacts.berlios.de/index-en.phtml?title=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
> >
> >      Were you helped on this list with your FreeNX problem?
> >     Then please write up the solution in the FreeNX Wiki/FAQ:
> >   http://openfacts.berlios.de/index-en.phtml?title=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