[FreeNX-kNX] 0.7.2 and 3.2.0 backend

John Seng jsseng at yahoo.com
Thu May 1 14:21:58 UTC 2008


Here is the output of the session file.

I find that when the server machine boots (it starts xfce4 automatically), I can never connect.  After I
run an 'nxserver --restart', then I can sometimes connect.  Shouldn't the locally running X session not be on display 1000?

--------------------------------------------------------

xrdb: No such file or directory
xrdb: Can't open display ':1000'
/usr/bin/startxfce4: X server already running on display :1000
xrdb: No such file or directory
xrdb: Can't open display ':1000'
Agent pid 5222

(xfce4-session:5230): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.

(xfce4-session:5230): Gtk-WARNING **: cannot open display: :1000
Agent pid 5222 killed

-------------------------------------------------------------------

----- Original Message ----
From: Al Johnson <alastair at solutiontrax.com>
To: freenx-knx at kde.org
Sent: Thursday, May 1, 2008 4:08:09 AM
Subject: Re: [FreeNX-kNX] 0.7.2 and 3.2.0 backend

nxagent is exiting with status 1 on the server. We need to see the server side 
logs to find out why. See the FAQ for how to enable logging:
http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ/Problem_Solving

We particularly need to see ~/.nx/F-<whatever>/session as this has the output 
from nxagent.

On Thursday 01 May 2008 07:04:38 John Seng wrote:
> I'm currently using FreeNX 0.7.2 with the 3.2.0 backend.  I'm trying to
> connect to my Archlinux box using a 3.2.0 Windows client.  It sometimes
> connects (and works flawlessly) and sometimes does not connect with the
> following error.
>
> I'm not sure what it is, but might it be a race condition of some kind? 
> Here is the output:
>
> -----------------------------------------------------------
>
>
> NX> 203 NXSSH running with pid: 6944
> 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: 192.168.1.103 on port: 22
> NX> 202 Authenticating user: nx
> NX> 208 Using auth method: publickey
> HELLO NXSERVER - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
> NX> 105 hello NXCLIENT - Version 2.1.0
> NX> 134 Accepted protocol: 2.1.0
> NX> 105 SET SHELL_MODE SHELL
> NX> 105 SET AUTH_MODE PASSWORD
> NX> 105 login
> NX> 101 User: root
> NX> 102 Password:
> NX> 103 Welcome to: myhost user: root
> NX> 105 listsession --user="root" --status="suspended,running"
> --geometry="1024x768x16+render" --type="unix-application" NX> 127 Sessions
> list of user 'root' for reconnect:
>
> Display Type             Session ID                       Options  Depth
> Screen         Status      Session Name -------
> ---------------- -------------------------------- -------- -----
> -------------- ----------- ------------------------------
>
>
> NX> 148 Server capacity: not reached for user: root
> NX>
> 105 startsession  --virtualdesktop="1"
> --application="/usr/bin/startxfce4" --link="isdn" --backingstore="1"
> --encryption="1" --cache="16M" --images="64M" --shmem="1" --shpix="1"
> --strict="0" --composite="1" --media="0" --imagecompressionmethod="4"
> --imagecompressionlevel="2" --render="1" --session="robot"
> --type="unix-application" --geometry="1024x768" --client="winnt"
> --keyboard="pc102/en_US" --screeninfo="1024x768x16+render"
>
> NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
> NX> 700 Session id: myhost-1000-C2AD3301C69A84492E9A2BF9A1D11A5B
> NX> 705 Session display: 1000
> NX> 703 Session type: unix-application
> NX> 701 Proxy cookie: c97b450f8a5780b28d89a89c004b4fb7
> NX> 702 Proxy IP: 127.0.0.1
> NX> 706 Agent cookie: c97b450f8a5780b28d89a89c004b4fb7
> NX> 704 Session cache: unix-application
> NX> 707 SSL tunneling: 1
> NX> 105 /usr/NX/bin/nxserver: line 1368:  4896 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
> "/root/.nx/F-C-myhost-1000-C2AD3301C69A84492E9A2BF9A1D11A5B/session".
> You might also want to try: ssh -X myserver; /usr/NX/bin/nxnode --agent
> to test the basic functionality. Session log follows:
> NX> 1006 Session status: closed
> Can't open
> /usr/NX/var/db/running/sessionId{C2AD3301C69A84492E9A2BF9A1D11A5B}: No such
> file or directory. mv: cannot stat
> `/usr/NX/var/db/running/sessionId{C2AD3301C69A84492E9A2BF9A1D11A5B}': No
> such file or directory NX> 1001 Bye.
> 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://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
> ________________________________________________________________



-- 
Alastair Johnson
SolutionTrax Technologies - http://www.solutiontrax.com
T: 01908 268902   F: 0709 2117048
________________________________________________________________
     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