[FreeNX-kNX] Nx can't create new sessions

[Spiro Stathakis]

Hi Chris,

Yes it is very peculiar that kde works and gnome does not.
A reinstall of the master nx box using

nxsetup --install --setup-nomachine-key --clean --purge

does seem to have  resolved and the key thing was simply down to the
nxcheckload user not having keys with the slave nodes
set up been working without problems for a while and forgot
how it was configured.

A rm -rf ~/.nx was also in order but all things seem ok now.

Thanks for help. Not sure what the problem was or if it was
fixed or whether it will crop up again but we are back in ;) !

We are using SLED 10.2 x86_64 .





2009/8/20 Spiro Stathakis <spiro.stathakis at gmail.com>:
> Hi
> Thanks for the reply. Before I received your mail I
> did a :
>
> nxsetup --install --setup-nomachine-key --clean --purge
>
> which re initialised my environment. I can now
> create a new session to the host machine but
> having problems getting the load balancing
> feature to work.
>
> It looks like key issues as I get a password
> box with green and blue bars. So trying to work
> out what bits of the setup are not happy.
>
> Cheers,
>
> Spiro
>
>
>
> 2009/8/20  <chris at ccburton.com>:
>>
>>
>> Spiro Stathakis <spiro.stathakis at gmail.com> wrote on 20/08/2009 11:09:12:
>>
>>> Hi there,
>>>
>>> Firstly thank you for FreeNX...it is a masterpiece of Unix engineering.
>>>
>>> Secondly, please will you advise on some diagnostic commands I can
>>> run to track down a sudden problem. ;)
>>>
>>> We got load balancing enabled and
>>> currently new sessions cannot be created. Existing sessions are not
>>> affected and users can attach and dettach from these as normal.
>>>
>>> When a new session is created everything seems fine but the
>>> NX screen area appears and disappears in a flash.
>>>
>>> Error logging is turned up full blast but nothing indicating a problem.
>>>
>>> Below is the output of the Nx client when making a connection. The
>>> session lasts for a second and then simply terminates.
>>>
>>> Any pointers into what could possibly cause the problem would be most
>>> welcome. (Problem persists on all client platforms and accross
>>> different networks)
>>>
>>> Info: Proxy running in client mode with pid '30468'.
>>> Session: Starting session at 'Thu Aug 20 10:56:39 2009'.
>>> Warning: Connected to remote version 3.2.0 with local version 3.3.0.
>>> Info: Connection with remote proxy completed.
>>> Warning: Unrecognized session type 'unix-gnome'. Assuming agent session.
>>
>>
>>
>> Warning: Unrecognized session type 'unix-gnome'. Assuming agent session.
>>
>>
>> Did you mean gnome, is it installed. Try KDE and see if that works . . . .
>>
>>
>>
>>> Info: Using LAN link parameters 1536/24/1/0.
>>> Info: Using pack method 'adaptive-9' with session 'unix-gnome'.
>>> Info: Not using NX delta compression.
>>> Info: Not using ZLIB data compression.
>>> Info: Not using ZLIB stream compression.
>>> Info: Not using a persistent cache.
>>> Info: Forwarding X11 connections to display ':0.0'.
>>> Info: Listening to font server connections on port '11029'.
>>> Session: Session started at 'Thu Aug 20 10:56:40 2009'.
>>> Info: Established X server connection.
>>> Info: Using shared memory parameters 1/2048K.
>>> Session: Terminating session at 'Thu Aug 20 10:56:40 2009'.
>>> Session: Session terminated at 'Thu Aug 20 10:56:40 2009'.
>>>
>>>
>>> Yours,
>>>
>>> Spiro
>>> ________________________________________________________________
>>>      Were you helped on this list with your FreeNX problem?
>>>     Then please write up the solution in the FreeNX Wiki/FAQ:
>>>
>>> http://openfacts2.berlios.de/wikien/index.php/BerliosProject: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
>>> ________________________________________________________________
>>
>