[FreeNX-kNX] Can't connect to nxserver from nxclient

[Erik P. Olsen]

On 26/01/09 13:50, Terje Andersen wrote:
> On Mon, 2009-01-26 at 13:23 +0100, Erik P. Olsen wrote:
>> I am new to freenx so forgive me if the answer is simple. I want to connect two
>> boxes both with Fedora 10 but am getting authentication failure. It is difficult
>> to diagnose what the problem is. Nothing in /var/log/messages or secure. Only
>> hint I get is from pam-unix which reports through Logwatch:
>>
>> sshd:
>>     Authentication Failures:
>>        nx (epowork.epolan.dk): 1 Time(s)
>>
>> Is there anything I can do to further diagnose what's going on? BTW I have
>> disabled selinux so it is not from there the problem comes.
>>
> 
> Hi Erik,
> 
> Find your node.conf file (normally in /etc/nxserver) and set
> NX_LOG_LEVEL=5 (without the # in front) and change 
> SESSION_LOG_CLEAN=0 (remove the # infront).
> This will make the nxserver script log to (normally) this file:
> /var/log/nxserver.log
> Watch that file as you log in, and if it tells you to investigate a
> session, then look at the error-file in the session log
> (/home/<userid>/.nx/<session-id>/error).

Hi Terje,

Made the changes you proposed and ~/.nx/<session-ID>/session had:

Error: Aborting session with 'Could not open default font 'fixed''.
Session: Aborting session at 'Tue Jan 27 00:55:12 2009'.
Session: Session aborted at 'Tue Jan 27 00:55:12 2009'.
Warning: Signals were not blocked in process with pid '5217'.
Info: Watchdog running with pid '5287'.
Info: Waiting the watchdog process to complete.

** (gnome-session:5291): WARNING **: Cannot open display:

and ./error:

Loop: WARNING! Connected to remote version 3.3.0 with local version 3.2.0.
Loop: WARNING! Signals were not blocked in process with pid '5217'.

What can you make out of this? Can the missing fixed font really block for the
connection?

> 
> Also look at your physical client logs.
> 
> If this doesn't help, try running the setup-procedure again with:
> 
> nxsetup --install --setup-nomachine-key --clean --purge
> 
> This will remove the previous FreeNX setup/konfig, remove the keys, and
> reinstall it again.
> 
> If this also fails, there is also at the wiki (see bottom of this mail)
> some instructions on how to debug SSHD problems.
> 
> I did an install on a Fedora10 a few weeks ago, and I can't remember
> having any issues (besides the 'fixed' font that should have been fixed
> by now, I think) - so if you can't figure it out, please return here :-)

Where can I get the fix for the fixed font which apparently is not fixed at all :-)

-- 
Erik.