[FreeNX-kNX] Followup to Problem Connecting Windows Client toSuSE9.3FreeNX Server

[Kaplan, Andrew H.]

Hi there --

I checked the session file, and the output included the following:

Info: Agent running with pid '22761'.
Info: Starting X protocol compression.
Error: Lost connection to peer proxy on FD#8.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.

Fatal server error:
NXAGENT: Fatal IO error on display
"nx/nx,options=/home/ahk/.nx/C-fifa-1000-5E1B710736AD96EE3459B1B7209AE219/option
s: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...
kded: cannot connect to X server unix:1000 DCOP aborting call from
'anonymous-23409' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
kcminit: 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...
startkde: Done.

Has anyone seen the Fatal IO error message before? 



-----Original Message-----
From: Alastair Johnson [mailto:alastair at solutiontrax.com] 
Sent: Tuesday, August 29, 2006 12:48 PM
To: freenx-knx at kde.org
Subject: Re: [FreeNX-kNX] Followup to Problem Connecting Windows Client
toSuSE9.3FreeNX Server

First step as always is to check the logs. Places to look on the server are:
/var/log/nxserver.log
pathto_users_home_dir/.nx/C_session_id/session and errors

The name of the session_id bit will change with each session, and by default 
will be removed when the session ends. To get it to stick around after the 
end of the session edit /etc/nxserver/node.conf and set SESSION_LOG_CLEAN=0
While you're there you may wish to increase the log level with NX_LOG_LEVEL=6 
or maybe even 7. If you don't have a node.conf just copy the sample and add 
the required settings.

With a bit of luck the logs should say why things aren't working, or give 
enough information for someone on the list to work it out. If all else fails 
and you're confortable with shell scripts, start looking at /usr/bin/nxnode. 
Echoing diagnostics to file, or redirecting stdout and/or stderr of a suspect 
tommand to file can get you a long way. 

On Tuesday 29 August 2006 17:15, Kaplan, Andrew H. wrote:
> Hi there -
>
>
>
> I was able to get to the Wiki website and made the suggested changes to the
> nxnode file. After the changes were made,
>
> I stopped and restarted the nxserver. When I try to connect now, I do get a
> connection, but the remote desktop does not
>
> appear. I did a ps -ef |grep nx on the Linux box and there are indeed
> daemons running that are associated with the connection.
>
>
>
> What are my next steps? Thanks.

________________________________________________________________
     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
________________________________________________________________