[FreeNX-kNX] Installing Freenx
Gregory Carter
gcarter at aesgi.com
Mon Feb 18 18:55:10 UTC 2008
Oh, dear....
-rw------- 1 gcarter gcarter 17121280 2008-02-17 20:06 core.23449
Had a ton of core files from yesterdays testing, which I did not
previously notice because I wasn't ls'ing the server account directory.
:-)
So it would appear the process is dieing or at the bare minimum core
dumping.
-gc
Alastair Johnson wrote:
> On Monday 18 February 2008, Gregory Carter wrote:
>
>> Jim,
>>
>> How long must you leave the connection going before the watchdog
>> signal kicks in? I left the connection up for a good 10 minutes and it
>> did not report any errors in the nxserver.log, or the client
>> session/SomeHost logs in the account .nx cookie directories for the
>> session.
>>
>
> ~2minutes for me. The problem is nxagent segfaulting so if you're not seeing
> this in the logs then you have a different problem. Just seen your other post
> with attached logs so more in that thread.
>
>
>> I tried running the nxserver in a 32 bit session using linux32 but
>> that had no effect either. So I am wondering if this might be a ssh
>> issue? I think I will try running sshd in a 32bit environment on the
>> server and see what happens.
>>
>> I am curious: What exactly is the know problem you cite below that has
>> been fixed in the version 3.0 libraries? Is there a link I can read
>> about it?
>>
>
> Search the list archives. Fabian posted a patch in Feb. 07 that got nxagent to
> compile and work for him. Some time later that patch was used in the fedora
> nx package. I posted about a problem I had in September 07 in a thread
> called 'Odd nxagent segfault issue' where someone suggested it was an issue
> in the backingstore code. Since then a few others have reported similar
> problems, at least one using a 32 bit client. I don't recall a fix being made
> for 2.1 series libs, but the 3.0.0 release from nomachine seems to have fixed
> 64 bit support.
>
>
>> -gc
>>
>> Alastair Johnson wrote:
>>
>>> Gregory,
>>>
>>> I just checked the versions on my FC8 64 bit box and it's showing nx
>>> version 2.1.0-22.fc7 which explains the problem. Apologies to whoever it
>>> was I questioned about this version a couple of weeks ago. This version
>>> contains a patch to support 64 bit, but the patch is only partially
>>> successful. It works perfectly for some people. Others (like me) have
>>> reported failures when connecting from 64 bit clients but not 32 bit
>>> clients, or vice versa, or success with windows clients but not linux
>>> clients. The problem is fixed in the 3.0 series libraries, but there
>>> isn't an FC8 binary of these yet AFAIK. With this bug the client will get
>>> through authentication and session setup, but sits for a long time at
>>> 'Established the display connection' or similar before failing. If you
>>> retry this a few times the failure will become instant. If you hit the
>>> 'Details' button the end of the log will look something like:
>>>
>>> Session: Session started at 'Mon Feb 18 11:20:08 2008'.
>>> Info: Established X server connection.
>>> Info: Using shared memory parameters 1/2048K.
>>> Session: Terminating session at 'Mon Feb 18 11:21:08 2008'.
>>> Info: Waiting the cleanup timeout to complete.
>>> Warning: Parent process appears to be dead. Exiting watchdog.
>>>
>>> Is this the sort of thing you're seeing?
>>>
>>> Jim,
>>>
>>> it sounds like your problem is ssh authentication. To check that ssh is
>>> correctly configured you should copy /etc/nxserver/client.id_dsa.key to
>>> the client machine, making sure that it's readable only by the user. you
>>> should now be able to connect to the server as user nx without needing a
>>> password: # ssh -i /wherever/you/put/your/client.id_dsa.key
>>> nx at your.server HELLO NXSERVER - Version 2.1.0-71 OS (GPL)
>>> NX> 105
>>> If this doesn't work you should look at the server's ssh logs to find out
>>> why.
>>>
>>> On Sunday 17 February 2008, Gregory Carter wrote:
>>>
>>>> Yeah, have the same problem with a 64 bit install of Fedora.
>>>>
>>>> I got the exact same installation working on a 32 bit system, works
>>>> fine.
>>>>
>>>> Something isn't playing cricket!
>>>>
>>>> -gc
>>>>
>>>> Jim wrote:
>>>>
>>>>> Alastair Johnson wrote:
>>>>>
>>>>>> On Saturday 09 February 2008, Jim wrote:
>>>>>>
>>>>>>> Alastair Johnson wrote:
>>>>>>>
>>>>>>>> On Saturday 09 February 2008, Jim wrote:
>>>>>>>>
>>>>>>>>> Yong Liu wrote:
>>>>>>>>>
>>>>>>>>>> Ubuntu package: freenx
>>>>>>>>>>
>>>>>>>>>> http://www.datakeylive.com/ubuntu/dists/gutsy/
>>>>>>>>>>
>>>>>>>>>> Yong
>>>>>>>>>>
>>>>>>>>>> -----Original Message-----
>>>>>>>>>> From: Jim [mailto:mickeyboa at sbcglobal.net]
>>>>>>>>>> Sent: Saturday, February 09, 2008 2:49 AM
>>>>>>>>>> To: nx
>>>>>>>>>> Subject: [FreeNX-kNX] Installing Freenx
>>>>>>>>>>
>>>>>>>>>> What packages do I install for freenx, for the node, server ,
>>>>>>>>>> client ?
>>>>>>>>>>
>>>>>>>>> I guess it would have been smart to let you know that I was going
>>>>>>>>> to install In Fedora 8.
>>>>>>>>> I know where the rpm's are but I don't know which ones to install
>>>>>>>>> for client, node, server
>>>>>>>>>
>>>>>>>> In that case all you need to do is:
>>>>>>>> yum install freenx
>>>>>>>>
>>>>>>>> When you set up the client you will need to set the key to match
>>>>>>>> the server's /etc/nxserver/client.id_dsa.key since this is different
>>>>>>>> from the nomachine key.
>>>>>>>>
>>>>>>> Let me get my thinking straight,
>>>>>>> I take the key from server /etc/nxserver/client.id_dsa.key and copy
>>>>>>> it to the client box, what's the path on the client box
>>>>>>> that the key goes in ?
>>>>>>>
>>>>>> It goes in the configuration GUI of the client. Rick Stout's page will
>>>>>> walk you through with screenshots. It may seem old (last update was
>>>>>> for FC5) but the GUI configuration has barely changed since then.
>>>>>>
>>>>>> http://fedoranews.org/contributors/rick_stout/freenx/
>>>>>>
>>>>>> A last point which may seem obvious, but from time to time people miss
>>>>>> it: you'll need KDE installed to start a KDE session, and Gnome to
>>>>>> start a Gnome session.
>>>>>>
>>>>>> If you still have problems then check the FAQ link in the footer for
>>>>>> instructions on enabling logging on the server.
>>>>>> ________________________________________________________________
>>>>>> 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
>>>>>> ________________________________________________________________
>>>>>>
>>>>> Trying to login the server from client and i'm getting error message:
>>>>>
>>>>> "The NX service is not available or the NX access was disabled on host
>>>>> 76.280.250.93."
>>>>>
>>>>> I can do a ssh -x bob at 76.280.250.93 and connect to server from client.
>>>>>
>>>>> freenx and nx is installed on FC8-x86_64 server and FC8-i386 client
>>>>> has nxclient-3.1.0-2 installed and
>>>>>
>>>>> /nxserver/client.id_dsa_key is copyied into nxclient-3.1.0-2 on client
>>>>> box.
>>>>>
>>>>> What am I not doing right ??
>>>>>
> ________________________________________________________________
> 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
> ________________________________________________________________
>
More information about the FreeNX-kNX
mailing list