[FreeNX-kNX] NX Connection per hand
Christian Wore
cwore at web.de
Wed Feb 28 20:14:16 UTC 2007
Hello,
i want to build a little bash skript which starts a NX connection.
I know that NX is a text based protocol, so it shouldn't be a problem.
After some time with google i found this:
http://www.nomachine.com/ar/view.php?ar_id=AR03C00171
they talk about the nxproxy. But on my freenx server, nxproxy isn't
installed and a connection with nomachine 2 client works fine. So i
think that nxproxy isn't necessary..do i am right?
so on.. i try to build a connection manual.
Here is the log:
user at debian~$ ssh nx at 192.168.15.21
Linux foo.fara.local 2.6.17-11-386 #2 Thu Feb 1 19:50:13 UTC 2007 i686
The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.
Last login: Wed Feb 28 17:52:19 2007 from foo.fara.local
HELLO NXSERVER - Version 1.5.0-60 OS (GPL)
NX> 105 login
login
NX> 101 User: cwore
cwore
NX> 102 Password:
NX> 103 Welcome to: foo.fara.local user: cwore
NX> 105 startsession --session="testsession" --type="unix-kde"
--cache="8M" --images="32M" --link="isdn" --render="1"
--kbtype="pc105/de" --nodelay="1" --backingstore="when_requested"
--imagecompressionmethod="0" --geometry="640x480+380+252" --media="0"
--agent_server="" --agent_user="" agent_password="******""
--screeninfo="640x480x24+render"
startsession --session="testsession" --type="unix-kde" --cache="8M"
--images="32M" --link="isdn" --render="1" --kbtype="pc105/de"
--nodelay="1" --backingstore="when_requested"
--imagecompressionmethod="0" --geometry="640x480+380+252" --media="0"
--agent_server="" --agent_user="" agent_password="******""
--screeninfo="640x480x24+render"
NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL)
NX> 700 Session id: foo.fara.local-1000-54FC58573D87635BED6ABD651F028A45
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 85c62c8bb9075292fda59e717ea763b1
NX> 702 Proxy IP: 192.168.15.23
NX> 706 Agent cookie:
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 0
NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
/usr/lib/nx/nxserver: line 1190: 5589 Terminated sleep
$AGENT_STARTUP_TIMEOUT
NX> 105 NX> 1006 Session status: running
<--little break for some seconds-->
NX> 596 Session startup failed.
NX> 1004 Error: NX Agent exited with exit status 1.
Can't open
/var/lib/nxserver/db/running/sessionId{54FC58573D87635BED6ABD651F028A45}:
No such file or directory.
mv: cannot stat
`/var/lib/nxserver/db/running/sessionId{54FC58573D87635BED6ABD651F028A45}':
No such file or directory
NX> 1006 Session status: closed
NX> 1001 Bye.
Thats the log.
<--end-->
and here is the output from the session file:
NXAGENT - Version 2.1.0
Copyright (C) 2001, 2006 NoMachine.
See http://www.nomachine.com/ for more information.
Info: Agent running with pid '5776'.
Session: Starting session at 'Wed Feb 28 21:02:20 2007'.
Info: Proxy running in server mode with pid '5776'.
Info: Waiting for connection from '192.168.15.23' on port '5000'.
Info: Aborting the procedure due to signal '1'.
Fatal server error:
Error: Unable to open display
'nx/nx,options=/home/cwore/.nx/C-foo.fara.local-1000-54FC58573D87635BED6ABD651F028A45/options:1000'.
xsetroot: unable to open display 'unix:1000'
xset: unable to open display "unix:1000"
xsetroot: unable to open display 'unix:1000'
startkde: Starting up...
xprop: unable to open display 'unix:1000'
usage: xprop [-options ...] [[format [dformat]] atom] ...
where options include:
-grammar print out full grammar for command line
-display host:dpy the X server to contact
-id id resource id of window to examine
-name name name of window to examine
-font name name of font to examine
-remove propname remove a property
-set propname value set a property to a given value
-root examine the root window
-len n display at most n bytes of any property
-notype do not display the type field
-fs filename where to look for formats for properties
-frame don't ignore window manager frames
-f propname format [dformat] formats to use for property of given name
-spy examine window properties forever
ksplash: cannot connect to X server unix:1000
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kded: cannot connect to X server unix:1000
DCOP aborting call from 'anonymous-5849' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
kcminit_startup: cannot connect to X server unix:1000
ksmserver: cannot connect to X server unix:1000
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
xprop: unable to open display 'unix:1000'
usage: xprop [-options ...] [[format [dformat]] atom] ...
where options include:
-grammar print out full grammar for command line
display host:dpy the X server to contact
-id id resource id of window to examine
-name name name of window to examine
-font name name of font to examine
-remove propname remove a property
-set propname value set a property to a given value
-root examine the root window
-len n display at most n bytes of any property
-notype do not display the type field
-fs filename where to look for formats for properties
-frame don't ignore window manager frames
-f propname format [dformat] formats to use for property of given name
-spy examine window properties forever
startkde: Done.
<--end-->
I think nxagent couldnt start. But why? does nxclient execute the
nxagent seperated so that i can't see this in the log files?
I hope someone can tell me a little bit more about "building a nx
connection"
thanks!
More information about the FreeNX-kNX
mailing list