[FreeNX-kNX] freeNX server crashed, no login

olaf olaf-linux at gmx.de
Tue Apr 27 17:31:46 UTC 2010


I have now set SESSION_LOG_CLEAN=0 in node.conf and investigate 
"/home/ME/.nx/F-C-serv-1005-86073E20C0F6AD1738D6611C0DE1FAFA/session".

-->
xrdb: No such file or directory
xrdb: Can't open display ':1005'
$DISPLAY is not set or cannot connect to the X server.

And I have set all kde-settings back to the settings before freeNX crash

Bye
Olaf




Am Dienstag, 27. April 2010 18:38:59 schrieb olaf:
> Hi!
> 
> My FreeNX-Server crashed, I don't know why. The only things I have changed
> are some default parameters in kde like theme, colours a.s.o.
> I logout of my session (nomachine-client) and after that I'm no longer able
> to login.
> 
> ssh -X myserver; /usr/bin/nxnode --agent
> opens an nx-window with a black screen.
> 
> Please help.
> 
> Bye
> Olaf
> 
> NX> 203 NXSSH running with pid: 28995
> 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.3.5 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: ME
> NX> 102 Password:
> NX> 103 Welcome to: serv user: ME
> NX> 105 listsession --user="ME" --status="suspended,running" --
> geometry="1280x1024x24+render" --type="unix-kde"
> NX> 127 Sessions list of user 'ME' for reconnect:
> 
> Display Type             Session ID                       Options  Depth
> Screen         Status      Session Name
> ------- ---------------- -------------------------------- -------- -----
> -------------- ----------- ------------------------------
> 
> 
> NX> 148 Server capacity: not reached for user: ME
> NX> 105 startsession  --link="lan" --backingstore="1" --encryption="1" --
> cache="16M" --images="64M" --shmem="1" --shpix="1" --strict="0" --
> composite="1" --media="0" --session="192.168.2.4" --type="unix-kde" --
> geometry="1024x768+128+101" --client="linux" --keyboard="pc102/de" --
> screeninfo="1024x768x24+render"
> 
> NX> 1000 NXNODE - Version 2.1.0-72 OS (GPL, using backend: 3.2.0)
> NX> 700 Session id: serv-1005-1EDFC94ABABE6E7BB6626192628B4F54
> NX> 705 Session display: 1005
> NX> 703 Session type: unix-kde
> NX> 701 Proxy cookie: 6c34f71251b7d65cd9de618e7732bb0a
> NX> 702 Proxy IP: 127.0.0.1
> NX> 706 Agent cookie: 6c34f71251b7d65cd9de618e7732bb0a
> NX> 704 Session cache: unix-kde
> NX> 707 SSL tunneling: 1
> NX> 105 /usr/bin/nxserver: line 1371:  7934 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/ME/.nx/F-C-
> serv-1005-1EDFC94ABABE6E7BB6626192628B4F54/session". You might also want to
> try: ssh -X myserver; /usr/bin/nxnode --agent to test the basic
> functionality. Session log follows:
> Can't open
> /var/lib/nxserver/db/running/sessionId{1EDFC94ABABE6E7BB6626192628B4F54}:
> No such file or directory.
> mv: cannot stat
> `/var/lib/nxserver/db/running/sessionId{1EDFC94ABABE6E7BB6626192628B4F54}':
> No such file or directory
> NX> 1006 Session status: closed
> NX> 1001 Bye.
> NX> 280 Exiting on signal: 15



More information about the FreeNX-kNX mailing list