[FreeNX-kNX] FreeNX - Odd bug in Arch linux version ? After reboot login fails a random number of times ?

Morgan Cox morgancoxuk at gmail.com
Tue Jun 16 08:40:06 UTC 2009


I am having a major issue with the Arch linux version of FreeNX -

After rebooting the freenx gateway machine my user (and other some other
users) are not able to login right away - The first couple of attempts
always fail

I would like to point out the following :-

- It is not a time thing - i.e it is not because I am not waiting long
enough after rebbot - I can leave it a few hours after reboot and the 1st
couple of attempts ALWAYS fail.
- I eventually can login just by trying a few time - after a few fails it
will then work ???  i.e i change no settings / options on the NX client or
NX server.
- When I do sucessfully login I can always login afterwards (suspended /
non-suspended sessions also work) until I reboot again - i.e once I have
logged in everything is fine  (until I reboot)

- Today it took 18 failed attempts before it worked ..........

Below is the error from a failed attempt.

Does anyone have any ideas?

NX> 203 NXSSH running with pid: 5678
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: on port: 3000
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 105 hello NXCLIENT - Version 3.2.0
NX> 134 Accepted protocol: 3.2.0
NX> 105 login
NX> 101 User: yossarian
NX> 102 Password:
NX> 103 Welcome to: winwinwinwin user: yossarian
NX> 105 listsession --user="yossarian" --status="suspended,running"
--geometry="1280x1024x24+render" --type="unix-kde"
NX> 127 Sessions list of user 'yossarian' for reconnect:

Display Type             Session ID                       Options  Depth
Screen         Status      Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------

NX> 148 Server capacity: not reached for user: yossarian
NX> 105 startsession  --link="adsl" --backingstore="1" --encryption="1"
--cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0"
--composite="1" --media="0" --imagecompressionmethod="3"
--imagecompressionlevel="-1" --render="1" --session=""
--type="unix-kde" --geometry="1280x974" --client="linux"
--keyboard="pc105/gb" --screeninfo="1280x974x24+render"

NX> 1000 NXNODE - Version 3.2.0-73 OS (GPL, using backend: 3.3.0)
NX> 105 /opt/NX/bin/nxserver: line 1531:  3871 Terminated              sleep
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot set
SESSION_LOG_CLEAN=0 in node.conf and investigate
You might also want to try: ssh -X myserver; /opt/NX/bin/nxnode --agent to
test the basic functionality. Session log follows:
Can't open
/opt/NX/var/db/running/sessionId{4019A7CF25937E24257EA1658F4247F9}: No such
file or directory.
mv: cannot stat
`/opt/NX/var/db/running/sessionId{4019A7CF25937E24257EA1658F4247F9}'NX> 1006
Session status: closed
NX> 700 Session id: winwinwinwin-1000-4019A7CF25937E24257EA1658F4247F9
: No such file or directory
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 3219d0ffd770c6a8309ca8d6dd7e128b
NX> 702 Proxy IP:
NX> 706 Agent cookie: 3219d0ffd770c6a8309ca8d6dd7e128b
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
NX> 280 Exiting on signal: 15
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090616/a75a89a9/attachment.html>

More information about the FreeNX-kNX mailing list