[FreeNX-kNX] Weird behaviour in FreeNX-0.7.0
Mark Van De Vyver
mvyver at gmail.com
Sat Sep 1 01:05:55 UTC 2007
Hi,
On 9/1/07, Miguel Angel Alvarez <maacruz at gmail.com> wrote:
> Hi,
>
> I have just upgraded to FreeNX-0.7.0/NX-2.1.0 in Opensuse 10.2 from the
> buildservice repositories, and I'm seeing a really weird behaviour.
> Sometimes the session starts just fine, sometimes it fails with a timeout
> after the client shows "autentication completed". It seems completely random.
> What's going on?
I've _generally_ had these versions working fine on openSUSE 10.2 -
the only time I saw something like what you describe was when the
server network connection was under-load. I've not seen random
behavior.
It's not possible to say just how much 'activity' yields this
behavior. Of course it may not be the network traffic, but something
related. Difficult to debug/isolate.
Strangely the load was on a interface other than the one FreeNX was
trying to connect to.
I don't have access to these machines now, but maybe ssh and fireup
top and iftop to see if that shows anything. I hope to be able to do
this in the next few weeks...
HTH
Mark
> Logs of a failed session follows
>
> /var/log/nxserver.log:
> -- NX SERVER START: -c /usr/bin/nxserver - ORIG_COMMAND=
> HELLO NXSERVER - Version 1.5.0-70 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: miguel
> NX> 102 Password:
> Info: Auth method: passdb ssh
> NX> 103 Welcome to: enol user: miguel
> NX> 105
> listsession --user="miguel" --status="suspended,running" --geometry="1680x1050x24+render+fulls
> creen" --type="unix-kde"
> NX> 127 Sessions list of user 'miguel' for reconnect:
>
> Display Type Session ID Options Depth
> Screen Status Se
> ssion Name
> ------- ---------------- -------------------------------- -------- ----- -------------- ----------- --
> ----------------------------
>
>
> NX> 148 Server capacity: not reached for user: miguel
> NX> 105
> startsession --session="localhost" --type="unix-kde" --cache="8M" --images="32M" --link="lan"
> --kbtype="pc102/es" --nodelay="1" --backingstore="when_requested" --geometry="1680x1001" --fullscreen=
> "1" --media="0" --agent_server="" --agent_user=""
> agent_password="******"" --screeninfo="1680x1050x24
> +render+fullscreen"
>
> &session=localhost&type=unix-kde&cache=8M&images=32M&link=lan&kbtype=pc102/es&nodelay=1&backingstore=w
> hen_requested&geometry=1680x1001&fullscreen=1&media=0&agent_server=&agent_user=&agent_password=******&
> screeninfo=1680x1050x24+render+fullscreen&clientproto=1.5.0&user=miguel&userip=127.0.0.1&uniqueid=D5CA
> 9346ED6A8D2E6542B2995BECC394&display=1000&host=127.0.0.1
> Password:
> NX> 1000 NXNODE - Version 1.5.0-70 OS (GPL)
> server_nxnode_echo: NX> 1000 NXNODE - Version 1.5.0-70 OS (GPL)
> NX> 700 Session id: enol-1000-D5CA9346ED6A8D2E6542B2995BECC394
> NX> 705 Session display: 1000
> NX> 703 Session type: unix-kde
> NX> 701 Proxy cookie: 84269706717242cd3a91156bea984a3a
> NX> 702 Proxy IP: 127.0.0.1
> NX> 706 Agent cookie: 84269706717242cd3a91156bea984a3a
> NX> 704 Session cache: unix-kde
> NX> 707 SSL tunneling: 0
> server_nxnode_echo: NX> 700 Session id:
> enol-1000-D5CA9346ED6A8D2E6542B2995BECC394
> server_nxnode_echo: NX> 705 Session display: 1000
> server_nxnode_echo: NX> 703 Session type: unix-kde
> server_nxnode_echo: NX> 701 Proxy cookie: 84269706717242cd3a91156bea984a3a
> server_nxnode_echo: NX> 702 Proxy IP: 127.0.0.1
> server_nxnode_echo: NX> 706 Agent cookie: 84269706717242cd3a91156bea984a3a
> server_nxnode_echo: NX> 704 Session cache: unix-kde
> server_nxnode_echo: NX> 707 SSL tunneling: 0
> NX> 1009 Session status: starting
> server_nxnode_echo: NX> 1009 Session status: starting
> NX> 710 Session status: running
> server_nxnode_echo: NX> 710 Session status: running
> NX> 1002 Commit
> server_nxnode_echo: NX> 1002 Commit
> NX> 1006 Session status: running
> session_status D5CA9346ED6A8D2E6542B2995BECC394 Running
> server_nxnode_echo: NX> 1006 Session status: running
> NX> 105 bye
> Bye
> NX> 999 Bye
> NX> 1001 Bye.
> NX> 105 NX> 1004 Error: NX Agent exited with exit status 1. To troubleshoot
> set SESSION_LOG_CLEAN=0 in
> node.conf and
> investigate "/home/miguel/.nx/F-C-enol-1000-D5CA9346ED6A8D2E6542B2995BECC394/session".
> You might also want to try: ssh -X myserver; /usr/bin/nxnode --agent to test
> the basic functionality.
> Session log follows:
>
> NXAGENT - Version 2.1.0
>
> Copyright (C) 2001, 2006 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Agent running with pid '19553'.
> Session: Starting session at 'Sat Sep 1 01:19:49 2007'.
> Info: Proxy running in server mode with pid '19553'.
> Info: Waiting for connection from '127.0.0.1' on port '5000'.
> Info: Aborting the procedure due to signal '1'.
>
> Fatal server error:
> Error: Unable to open
> display 'nx/nx,options=/home/miguel/.nx/C-enol-1000-D5CA9346ED6A8D2E6542B2995BECC394/options:1000'.
>
> NX> 1006 Session status: closed
> server_nxnode_echo: NX> 596 Session startup failed.
>
> /home/miguel/.nx/F-C-enol-1000-D5CA9346ED6A8D2E6542B2995BECC394/session
>
> NXAGENT - Version 2.1.0
>
> Copyright (C) 2001, 2006 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Agent running with pid '19553'.
> Session: Starting session at 'Sat Sep 1 01:19:49 2007'.
> Info: Proxy running in server mode with pid '19553'.
> Info: Waiting for connection from '127.0.0.1' on port '5000'.
> Info: Aborting the procedure due to signal '1'.
>
> Fatal server error:
> Error: Unable to open
> display 'nx/nx,options=/home/miguel/.nx/C-enol-1000-D5CA9346ED6A8D2E6542B2995BECC394/options:1000'.
>
> xset: unable to open display "unix:1000"
> xset: unable to open display "unix:1000"
> xset: unable to open display "unix:1000"
> xsetroot: unable to open display 'unix:1000'
> startkde: Starting up...
> ......
>
> --
> Don't see the world through a window, be open{source}minded, and be free :-)
> ________________________________________________________________
> 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
> ________________________________________________________________
>
More information about the FreeNX-kNX
mailing list