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

Marcelo Boveto Shima marceloshima at gmail.com
Wed Jun 17 03:38:38 UTC 2009


The package provides a init script?On maybe you can try to execute the
following before starting a nx session:

mkdir -m1755 /tmp/.X11-unix/
nxserver --cleanup
nxserver --start

On Tue, Jun 16, 2009 at 5:40 AM, Morgan Cox <morgancoxuk at gmail.com> wrote:

> Hi.
>
>
> I am having a major issue with the Arch linux version of FreeNX -
> http://wiki.archlinux.org/index.php/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: 194.216.112.15 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 SET SHELL_MODE SHELL
> NX> 105 SET AUTH_MODE PASSWORD
> 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="194.216.112.15"
> --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 $AGENT_STARTUP_TIMEOUT
> 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
> "/home/yossarian/.nx/F-C-winwinwinwin-1000-4019A7CF25937E24257EA1658F4247F9/session".
> 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: 127.0.0.1
> NX> 706 Agent cookie: 3219d0ffd770c6a8309ca8d6dd7e128b
> NX> 704 Session cache: unix-kde
> NX> 707 SSL tunneling: 1
> NX> 280 Exiting on signal: 15
>
> ________________________________________________________________
>     Were you helped on this list with your FreeNX problem?
>    Then please write up the solution in the FreeNX Wiki/FAQ:
>
> 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
> ________________________________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090617/670472b3/attachment.html>


More information about the FreeNX-kNX mailing list