Debugging

What tools can I use to figure out how to debug my nx
installation?

Please provide advanced methods....

I just upgraded my slackware distrobution to current and it
has broken my nx...
I have recompiled the nx from my source files...

But it still crashes on the final step just before the
screen begins to paint...

My nxserver.log doesn't have anything in it ...

And I have no idea how to figure out what the problem is...
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

See the FAQ for how to turn on logging, both for the server
and the session. 
by the sound of it you should look at the session and error
logs in the 
user's home directory. Most problems can be diagnosed from
the log files. See 
the FAQ, search the list archives in case someone's fixed it
before, and if 
that fails try posting the logs here. It also helps to give
version numbers 
for FreeNX, the NX libs, the client and the OS involved.

Advanced methods involve looking at the source  FreeNX
is a collection of 
shell scripts that use the NX libraries. There is usually
enough in the logs 
to spot where the error occurred and grep the scripts for
the message to give 
yourself a starting point. Now you can add your own echos to
logfile, or to 
your own debug file if you prefer.

On Monday 04 June 2007 20:25, Daniel Aquino wrote:
> What tools can I use to figure out how to debug my nx
installation?
>
> Please provide advanced methods....
>
> I just upgraded my slackware distrobution to current
and it has broken my
> nx... I have recompiled the nx from my source files...
>
> But it still crashes on the final step just before the
screen begins to
> paint...
>
> My nxserver.log doesn't have anything in it ...
>
> And I have no idea how to figure out what the problem
is...
>
____________________________________________________________
____
>      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=Free
NX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com
/kb/
>
>
____________________________________________________________
____
>        FreeNX-kNX mailing list --- FreeNX-kNXkde.org
>       http
s://mail.kde.org/mailman/listinfo/freenx-knx
>
____________________________________________________________
____

____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

On 6/5/07, Alastair Johnson <alastairsolutiontrax.com> wrote:
> See the FAQ for how to turn on logging, both for the
server and the session.

You mean for the client ?

> by the sound of it you should look at the session and
error logs in the
> user's home directory.

On the client or the server side ?

> Most problems can be diagnosed from the log files.

My client doesn't seem to have logs...
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

On Tuesday 05 June 2007 15:04, Daniel Aquino wrote:
> On 6/5/07, Alastair Johnson <alastairsolutiontrax.com> wrote:
> > See the FAQ for how to turn on logging, both for
the server and the
> > session.
>
> You mean for the client ?

I was meaning on the server, but you could do it at the
client end too. On the 
nomachine client you can go to the 'Environment' tab of the
config dialog and 
uncheck 'Remove old session files'. This stops the client
cleaning out its 
session files in the directory specified above the checkbox.


> > by the sound of it you should look at the session
and error logs in the
> > user's home directory.
>
> On the client or the server side ?

Server side

> > Most problems can be diagnosed from the log
files.
>
> My client doesn't seem to have logs...

See first answer. By default the client clears them at the
end of the session, 
so you may not have seen them.

>
____________________________________________________________
____
>      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=Free
NX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com
/kb/
>
>
____________________________________________________________
____
>        FreeNX-kNX mailing list --- FreeNX-kNXkde.org
>       http
s://mail.kde.org/mailman/listinfo/freenx-knx
>
____________________________________________________________
____

____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

On 6/5/07, Alastair Johnson <alastairsolutiontrax.com> wrote:
> I was meaning on the server


Here is the output of full loggin...



-- NX SERVER START: -c /usr/NX/bin/nxserver - ORIG_COMMAND=
HELLO NXSERVER - Version 1.5.0-60 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: daquino
NX> 102 Password:
Info: Auth method: passdb ssh
NX> 103 Welcome to: forsaken user: daquino
NX> 105 listsession --user="daquino"
--status="suspended,running"
--geometry="1024x768x32+render+fullscreen"
--type="unix-kde"
NX> 127 Sessions list of user 'daquino' for reconnect:

Display Type             Session ID                      
Options
Depth Screen         Status      Session Name
------- ---------------- --------------------------------
--------
----- -------------- -----------
------------------------------


NX> 148 Server capacity: not reached for user: daquino
NX> 105 startsession  --link="isdn"
--backingstore="1" --nodelay="1"
--cache="8M" --images="32M"
--media="0" --session="chino"
--type="unix-kde" --geometry="1024x745"
--fullscreen="1"
--kbtype="pc102/en_US"
--screeninfo="1024x768x32+render+fullscreen"

&link=isdn&backingstore=1&nodelay=1&cache=8M
&images=32M&media=0&session=chino&type=unix-
kde&geometry=1024x745&fullscreen=1&kbtype=pc102/
en_US&screeninfo=1024x768x32+render+fullscreen&clien
tproto=1.5.0&user=daquino&userip=205.169.0.34&un
iqueid=9211530FB02B08AEDE82C06AC9E55F1F&display=1002&
;host=127.0.0.1
daquino127.0.0.1's password:
NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL)
NX> 700 Session id:
forsaken-1002-9211530FB02B08AEDE82C06AC9E55F1F
NX> 705 Session display: 1002
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: cd9384dd38da3974c784358a69762189
NX> 702 Proxy IP: 205.169.0.34
NX> 706 Agent cookie: cd9384dd38da3974c784358a69762189
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 0
NX> 1009 Session status: starting
NX> 710 Session status: running
NX> 1002 Commit
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.
NX> 1006 Session status: closed
NX> 596 Session startup failed.
NX> 1001 Bye.
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

On Tuesday 05 June 2007 16:03, Daniel Aquino wrote:
> On 6/5/07, Alastair Johnson <alastairsolutiontrax.com> wrote:
> > I was meaning on the server
>
> Here is the output of full loggin...
>
>

snip...everything seems fine to here

> NX> 1001 Bye.
> NX> 105 NX> 1004 Error: NX Agent exited with exit
status 1.

So nxagent failed. The reason for this is probably in the
user's session and 
error files on the server, location described in the FAQ.

> NX> 1006 Session status: closed
> NX> 596 Session startup failed.
> NX> 1001 Bye.

____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

On 6/5/07, Alastair Johnson <alastairsolutiontrax.com> wrote:
> So nxagent failed. The reason for this is probably in
the user's session and
> error files on the server, location described in the
FAQ.

Some kinda error where kdeinit cant attach to the x
instance... ?


rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
cat session

NXAGENT - Version 2.1.0

Copyright (C) 2001, 2006 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '3518'.
Session: Starting session at 'Tue Jun  5 12:52:23 2007'.
Info: Proxy running in server mode with pid '3518'.
Info: Waiting for connection from '205.169.0.34' on port
'5002'.
Info: Aborting the procedure due to signal '15'.

Fatal server error:
Error: Unable to open display
'nx/nx,options=/home/daquino/.nx/C-forsaken-1002-484451D956D
E702F57C666946EB96D77/options:1002'.

lay "unix:1002"
xsetroot:  unable to open display 'unix:1002'
startkde: Starting up...
ksplash: cannot connect to X server unix:1002
xprop:  unable to open display 'unix:1002'
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

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kded: cannot connect to X server unix:1002
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably
crashed.
kcminit_startup: cannot connect to X server unix:1002
ksmserver: cannot connect to X server unix:1002
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
xprop:  unable to open display 'unix:1002'
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.
rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
clear
rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
ls
authority  errors  options  pids/  scripts/  session  stats
rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
cat stats
rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
ls pids/
rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
ls scripts/
authority
rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
cat scripts/authority
remove localhost:1002
remove unix:1002
exit
rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#
less session
    -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

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kded: cannot connect to X server unix:1002
kded: ERROR: KUniqueApplication: Registering failed!
kded: ERROR: Communication problem with kded, it probably
crashed.
kcminit_startup: cannot connect to X server unix:1002
ksmserver: cannot connect to X server unix:1002
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
xprop:  unable to open display 'unix:1002'
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.
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> On 6/5/07, Alastair Johnson <alastairsolutiontrax.com> wrote:
> > So nxagent failed. The reason for this is probably
in the user's session
> and
> > error files on the server, location described in
the FAQ.
> 
> Some kinda error where kdeinit cant attach to the x
instance... ?
>

nope 

Completely wrong.
 >rootforsaken:/home/daquino/.nx/F-C-forsaken-1002-484451D9
56DE702F57C666946EB96D77#

> cat session
> 
> NXAGENT - Version 2.1.0
> 
> Copyright (C) 2001, 2006 NoMachine.
> See http://www.nomachine.com/ for more information.
> 
> Info: Agent running with pid '3518'.
> Session: Starting session at 'Tue Jun  5 12:52:23
2007'.
> Info: Proxy running in server mode with pid '3518'.
> Info: Waiting for connection from '205.169.0.34' on
port '5002'.

Ah, it waits for connection on port 5002, but that
connection never comes.

Either opening the firewall for ports 5000-5999 or enabling
SSL encryption should help.

cu

Fabian
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

On 6/5/07, Fabian Franz <FabianFranzgmx.de> wrote:

> Either opening the firewall for ports 5000-5999 or
enabling SSL encryption should help.

I don't have firewall locally on the box...
Although port 22 is nat'd to it but that was never an
issue...


> Ah, it waits for connection on port 5002, but that
connection never comes.

I took off ssl to see if that was the problem it didn't work
with ssl either...
Here is the error log with ssl on...




NXAGENT - Version 2.1.0

Copyright (C) 2001, 2006 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Agent running with pid '11404'.
Session: Starting session at 'Wed Jun  6 10:42:20 2007'.
Info: Proxy running in server mode with pid '11404'.
Info: Waiting for connection from '127.0.0.1' on port
'5002'.
Info: Accepted connection from '127.0.0.1' with port
'54128'.
Info: Connection with remote proxy established.
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Info: Using isdn link parameters 384/24/1/0.
Info: Using agent parameters 5000/50/0/0.
Info: Using cache parameters 4/4194304/8192KB/8192KB.
Info: Using image streaming parameters
50/128/1024KB/1536/192.
Info: Using image cache parameters 1/1/32768KB.
Info: Using pack method '16m-jpeg-5' with session
'unix-kde'.
Info: Using ZLIB data compression 6/6/32.
Info: Using ZLIB stream compression 9/9.
Info: No suitable cache file found.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/1/2048K.
Info: No window manager has been detected.
nxagentOpenScreen: Forcing fullscreen mode with no window
manager running,
Info: Using local device configuration changes.
Info: Using alpha channel in render extension.
Session: Session started at 'Wed Jun  6 10:42:26 2007'.
Session: Terminating session at 'Wed Jun  6 10:42:30 2007'.
Info: End of NX transport requested by agent.
Info: Watchdog running with pid '12514'.
Info: Waiting the watchdog process to complete.
Info: Shutting down the NX transport.
Session: Session terminated at 'Wed Jun  6 10:42:40 2007'.
me 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

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kded: cannot connect to X server unix:1002
DCOP aborting call from 'anonymous-12283' to 'kded'
kded: ERROR: Communication problem with kded, it probably
crashed.
kcminit_startup: cannot connect to X server unix:1002
ksmserver: cannot connect to X server unix:1002
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
xprop:  unable to open display 'unix:1002'
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.
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> nxagentOpenScreen: Forcing fullscreen mode with no
window manager running,

Why would it say this if kde works fine ?

> Info: Waiting for connection from '127.0.0.1' on port
'5002'.

> kdeinit: Can't connect to the X Server.
> kded: cannot connect to X server unix:1002
> kcminit_startup: cannot connect to X server unix:1002
> ksmserver: cannot connect to X server unix:1002
> xprop:  unable to open display 'unix:1002'

And why is kde trying to use 1002 if it looks like nx is
listening on 5002 ?
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

help.... :[
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> help.... :[

öh, what?

cu

Fabian
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____

> öh, what?

I haven't been able to nx for days :[

Any more ideas whats wrong ?
____________________________________________________________
____
     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=Free
NX_FAQ
         Don't forget to check the NX Knowledge Base:
                 http://www.nomachine.com
/kb/ 

____________________________________________________________
____
       FreeNX-kNX mailing list --- FreeNX-kNXkde.org
      http
s://mail.kde.org/mailman/listinfo/freenx-knx
____________________________________________________________
____