[FreeNX-kNX] Minimum bandwidth req's
Hristo Benev
hristo.benev at waveroad.ca
Thu Feb 22 17:34:04 UTC 2007
Igor Manassypov wrote:
> >From your experience, what are the minimum bandwidth requirements for
> near-realtime response from nxserver? I cant figure that part out, I
> need to calculate how many concurrent clients can a particular line
> sustain.
>
>
> Thanks!
>
>
> -igor
>
>
> On Thu, 2007-02-22 at 18:02 +0100, freenx-knx-request at kde.org wrote:
>
>> Send FreeNX-kNX mailing list submissions to
>> freenx-knx at kde.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://mail.kde.org/mailman/listinfo/freenx-knx
>> or, via email, send a message with subject or body 'help' to
>> freenx-knx-request at kde.org
>>
>> You can reach the person managing the list at
>> freenx-knx-owner at kde.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of FreeNX-kNX digest..."
>>
>>
>> ________________________________________________________________
>> Don't forget to check the NX Knowledge Base:
>> http://www.nomachine.com/kb/
>> Please also check the FreeNX Wiki+FAQ for hints.
>> http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>> ________________________________________________________________
>>
>>
>>
>> Today's Topics:
>>
>> 1. encoding/compression not respected when rootless mode used?
>> (Tomasz Chmielewski)
>> 2. nxclient can't connect to freenx server anymore (Nico De Ranter)
>> 3. Re: nxclient can't connect to freenx server anymore (Fabian Franz)
>> 4. Re: nxclient can't connect to freenx server anymore (Hristo Benev)
>> 5. Re: Memory leak in nxagent, with patch (Dimitar Paskov)
>> 6. Re: Memory leak in nxagent, with patch (Jo-Erlend Schinstad)
>> 7. Re: nxclient can't connect to freenx server anymore
>> (Nico De Ranter)
>> 8. Re: Memory leak in nxagent, with patch (Dimitar Paskov)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 22 Feb 2007 12:15:05 +0100
>> From: Tomasz Chmielewski <mangoo at wpkg.org>
>> Subject: [FreeNX-kNX] encoding/compression not respected when rootless
>> mode used?
>> To: FreeNX-kNX <freenx-knx at kde.org>
>> Message-ID: <45DD7B39.7090205 at wpkg.org>
>> Content-Type: text/plain; charset=ISO-8859-2; format=flowed
>>
>> I have Linux / nx 2.1.0 / freenx 0.6.0 on the server side, and Linux /
>> nxclient-2.1.0-11 on the client side.
>>
>> I noticed that when I connect in a rootless mode to start single apps,
>> encoding/compression settings are not respected.
>>
>> In other words, although I set encoding to jpeg,
>> worst quality (0), the quality of the started application is very good.
>>
>> This has a bad side effect for me - for example, when I start Mozilla
>> Thunderbird, and want to display the "About" window (or images etc.),
>> the connection freezes, and breaks after some time.
>>
>> If I start the whole KDE session, and Thunderbird in it, About window is
>> displayed without problems - I also see that the quality is really "jpeg".
>>
>>
>> Is it a configuration problem on my side, or perhaps custom
>> encoding/compression is really not respected in rootless / single
>> application mode?
>>
>>
>> --
>> Tomasz Chmielewski
>> http://wpkg.org
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 22 Feb 2007 13:10:34 +0100
>> From: Nico De Ranter <nico at sonycom.com>
>> Subject: [FreeNX-kNX] nxclient can't connect to freenx server anymore
>> To: freenx-knx at kde.org
>> Message-ID: <1172146234.7604.155.camel at zebra.sonytel.be>
>> Content-Type: text/plain
>>
>>
>> Hi,
>>
>> I have been running NX on a number of Centos 4.4 systems for a while now
>> and I am very happy with it. However after a recent system upgrade I
>> suddenly can't connect to the server anymore.
>>
>> 'm currently running:
>> nxclient-2.1.0-11
>> freenx-0.5.0-12.el4.centos
>> nx-2.1.0-5.el4.centos
>>
>> When trying to connect I get the following messages:
>>
>> NX> 203 NXSSH running with pid: 11207
>> NX> 285 Enabling check on switch command
>> NX> 285 Enabling skip of SSH config files
>> NX> 285 Setting the preferred NX options
>> NX> 200 Connected to address: 192.168.1.1 on port: 22
>> NX> 202 Authenticating user: nx
>> NX> 208 Using auth method: publickey
>> NX> 204 Authentication failed.
>>
>> It looks like nxclient can't login as user 'nx' anymore on the remote
>> system. However the ssh keys seem fine. When I try to connect manually
>> using nx's private key I can logon without problems. I have verified
>> the key for the server which is configured on the client and that looks
>> ok too. The nxserver logs on the server are empty (but I don't think he
>> even gets that far).
>>
>> Any idea why this may be the case or how to fix it? Any idea how to
>> increase the verbosity of the log files for nxclient?
>>
>> Thanks in advance,
>>
>> Nico
>>
>> --
>> Nico De Ranter
>> Senior System Administrator
>> Sony Service Center (NSCE)
>> The Corporate Village, Da Vincilaan 7-D1
>> B-1935 Zaventem, Belgium
>> Telephone: +32 (0)2 700 86 41 Fax: +32 (0)2 700 86 22
>>
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Thu, 22 Feb 2007 15:06:03 +0100
>> From: "Fabian Franz" <FabianFranz at gmx.de>
>> Subject: Re: [FreeNX-kNX] nxclient can't connect to freenx server
>> anymore
>> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
>> Message-ID: <20070222140603.154000 at gmx.net>
>> Content-Type: text/plain; charset="us-ascii"
>>
>>
>>> Hi,
>>>
>>> I have been running NX on a number of Centos 4.4 systems for a while now
>>> and I am very happy with it. However after a recent system upgrade I
>>> suddenly can't connect to the server anymore.
>>>
>>> 'm currently running:
>>> nxclient-2.1.0-11
>>> freenx-0.5.0-12.el4.centos
>>> nx-2.1.0-5.el4.centos
>>>
>>> When trying to connect I get the following messages:
>>>
>>> NX> 203 NXSSH running with pid: 11207
>>> NX> 285 Enabling check on switch command
>>> NX> 285 Enabling skip of SSH config files
>>> NX> 285 Setting the preferred NX options
>>> NX> 200 Connected to address: 192.168.1.1 on port: 22
>>> NX> 202 Authenticating user: nx
>>> NX> 208 Using auth method: publickey
>>> NX> 204 Authentication failed.
>>>
>>> It looks like nxclient can't login as user 'nx' anymore on the remote
>>> system. However the ssh keys seem fine. When I try to connect manually
>>> using nx's private key I can logon without problems. I have verified
>>> the key for the server which is configured on the client and that looks
>>> ok too. The nxserver logs on the server are empty (but I don't think he
>>> even gets that far).
>>>
>>> Any idea why this may be the case or how to fix it? Any idea how to
>>> increase the verbosity of the log files for nxclient?
>>>
>> You are right this is a SSH problem, but I have no idea. Sometimes running nxsetup again can help.
>>
>> You might want to run sshd in debug mode.
>>
>> /etc/init.d/ssh stop
>>
>> sshd -v -v -v
>>
>> or so ...
>>
>> cu
>>
>> Fabian
>>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Thu, 22 Feb 2007 09:11:59 -0500
>> From: Hristo Benev <hristo.benev at waveroad.ca>
>> Subject: Re: [FreeNX-kNX] nxclient can't connect to freenx server
>> anymore
>> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
>> Message-ID: <45DDA4AF.8070305 at waveroad.ca>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> Fabian Franz wrote:
>>
>>>> Hi,
>>>>
>>>> I have been running NX on a number of Centos 4.4 systems for a while now
>>>> and I am very happy with it. However after a recent system upgrade I
>>>> suddenly can't connect to the server anymore.
>>>>
>>>> 'm currently running:
>>>> nxclient-2.1.0-11
>>>> freenx-0.5.0-12.el4.centos
>>>> nx-2.1.0-5.el4.centos
>>>>
>>>> When trying to connect I get the following messages:
>>>>
>>>> NX> 203 NXSSH running with pid: 11207
>>>> NX> 285 Enabling check on switch command
>>>> NX> 285 Enabling skip of SSH config files
>>>> NX> 285 Setting the preferred NX options
>>>> NX> 200 Connected to address: 192.168.1.1 on port: 22
>>>> NX> 202 Authenticating user: nx
>>>> NX> 208 Using auth method: publickey
>>>> NX> 204 Authentication failed.
>>>>
>>>> It looks like nxclient can't login as user 'nx' anymore on the remote
>>>> system. However the ssh keys seem fine. When I try to connect manually
>>>> using nx's private key I can logon without problems. I have verified
>>>> the key for the server which is configured on the client and that looks
>>>> ok too. The nxserver logs on the server are empty (but I don't think he
>>>> even gets that far).
>>>>
>>>> Any idea why this may be the case or how to fix it? Any idea how to
>>>> increase the verbosity of the log files for nxclient?
>>>>
>>>>
>>> You are right this is a SSH problem, but I have no idea. Sometimes running nxsetup again can help.
>>>
>>> You might want to run sshd in debug mode.
>>>
>>> /etc/init.d/ssh stop
>>>
>>> sshd -v -v -v
>>>
>>> or so ...
>>>
>>> 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=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
>>> ________________________________________________________________
>>>
>>>
>> It could be just key mismatch....
>>
>> Compare the key of the server and client.
>>
>> Hristo Benev
>> http://hbcom.info
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: http://mail.kde.org/pipermail/freenx-knx/attachments/20070222/a96bad97/attachment-0001.html
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Thu, 22 Feb 2007 16:14:46 +0200
>> From: Dimitar Paskov <pascoff at nola7.com>
>> Subject: Re: [FreeNX-kNX] Memory leak in nxagent, with patch
>> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
>> Message-ID: <200702221614.46518.pascoff at nola7.com>
>> Content-Type: text/plain; charset="iso-8859-15"
>>
>> Hi, I have the same problem and the worst part is that it affects not only the
>> nxagent but the X server where the nxclient is started ... the problem is
>> that I use NX with thin clients with 128MB RAM which is not enough. This
>> problem occurs when viewing graphics - pictures, photos, scanned files,
>> anything that has an image ... I think it is something with caching images
>> from applications running inside nxagent, which caches this images and sends
>> them through nxclient to the X server where the client is started. When this
>> cache becomes bigger than the available memory on the client side (thin
>> client) the X server crashes ... the problem continues when you try to resume
>> the session (which is alive on the server) and the cached stuff from
>> nxagent "returns" to the client and fills the whole memory again ...
>> to fix this you have to kill nxagent or the application from which it caches
>> images ... I'm not sure if it's a memory leak or it is designed to work like
>> that, may be its a X server problem ...
>>
>>
>>> Due to having long sessions, I've been afflicted by memory leaks in
>>> nxagent. Such leaks can be visually seen at:
>>> http://img57.imageshack.us/img57/3018/memorymonthbl4.png
>>> The green area, representing total application memory usage for the
>>> whole system, illustrates the leaks: nxagent would go from 30MB
>>> resident to 200+, until I'd finally get pissed off and would restart
>>> the session.
>>>
>>> I finally decided to do something about it. The attached patch fixes
>>> those memory leaks. Note that not all leaks are fixed. Essentially all
>>> of the others (that my workload triggers) are in initialisation code,
>>> so they only occur once, and, therefor, have less impact.
>>>
>>> The patch should apply cleanly against nxagent-2.1.0-18, currently the
>>> latest available from the NoMachines's source page
>>> (http://www.nomachine.com/sources.php)
>>>
>>> The main leak is in nxagentSynchronizeRegion, so it probably affects
>>> most workloads.
>>>
>>> Anik
>>>
>>> PS: this leak fix was facilitated by valgrind. If you're a C/C++
>>> developer/maintainer and have never looked into it, you should.
>>>
>> ------------------------------
>>
>> Message: 6
>> Date: Thu, 22 Feb 2007 16:04:22 +0100
>> From: "Jo-Erlend Schinstad" <joerlend.schinstad at gmail.com>
>> Subject: Re: [FreeNX-kNX] Memory leak in nxagent, with patch
>> To: "User Support for FreeNX Server and kNX Client"
>> <freenx-knx at kde.org>
>> Message-ID:
>> <bc66a2e50702220704i46044876xde2fc6caba18c3d8 at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>
>> On 22/02/07, Dimitar Paskov <pascoff at nola7.com> wrote:
>>
>>> [snip] ... the problem continues when you try to resume
>>> the session (which is alive on the server) and the cached stuff from
>>> nxagent "returns" to the client and fills the whole memory again ...
>>> to fix this you have to kill nxagent or the application from which it caches
>>> images ... I'm not sure if it's a memory leak or it is designed to work like
>>> that, may be its a X server problem ...
>>>
>> This is very interesting. I'm running a nx server on Ubuntu Edgy
>> running in a VMWare virtual machine. My problem is I have just enough
>> RAM for the host and guest OS. My nx sessions are running 24/7 and
>> after a week, the system begins to slow down. I checked, and it turns
>> out nxagent is uses _alot_ more RAM as time goes by. It seems to be ok
>> when I just close the session and open a new one. I don't have to kill
>> anything. Can you check this please? Even though the problem itself
>> might not be solvable, it might be possible to establish better
>> habits.
>>
>> cheers
>> Jo-Erlend
>>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Thu, 22 Feb 2007 16:24:15 +0100
>> From: Nico De Ranter <nico at sonycom.com>
>> Subject: Re: [FreeNX-kNX] nxclient can't connect to freenx server
>> anymore
>> To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
>> Cc: admin at sonycom.com
>> Message-ID: <1172157855.7604.174.camel at zebra.sonytel.be>
>> Content-Type: text/plain
>>
>>
>> Yep, it was a key mismatch. Altough the key in the nx homedir and the
>> one on the client looked the same. However running 'nxsetup --install
>> --setup-nomachine-key --override' fixed it.
>>
>> Thanks
>>
>> Nico
>>
>> On Thu, 2007-02-22 at 09:11 -0500, Hristo Benev wrote:
>>
>>> Fabian Franz wrote:
>>>
>>>>> Hi,
>>>>>
>>>>> I have been running NX on a number of Centos 4.4 systems for a while now
>>>>> and I am very happy with it. However after a recent system upgrade I
>>>>> suddenly can't connect to the server anymore.
>>>>>
>>>>> 'm currently running:
>>>>> nxclient-2.1.0-11
>>>>> freenx-0.5.0-12.el4.centos
>>>>> nx-2.1.0-5.el4.centos
>>>>>
>>>>> When trying to connect I get the following messages:
>>>>>
>>>>> NX> 203 NXSSH running with pid: 11207
>>>>> NX> 285 Enabling check on switch command
>>>>> NX> 285 Enabling skip of SSH config files
>>>>> NX> 285 Setting the preferred NX options
>>>>> NX> 200 Connected to address: 192.168.1.1 on port: 22
>>>>> NX> 202 Authenticating user: nx
>>>>> NX> 208 Using auth method: publickey
>>>>> NX> 204 Authentication failed.
>>>>>
>>>>> It looks like nxclient can't login as user 'nx' anymore on the remote
>>>>> system. However the ssh keys seem fine. When I try to connect manually
>>>>> using nx's private key I can logon without problems. I have verified
>>>>> the key for the server which is configured on the client and that looks
>>>>> ok too. The nxserver logs on the server are empty (but I don't think he
>>>>> even gets that far).
>>>>>
>>>>> Any idea why this may be the case or how to fix it? Any idea how to
>>>>> increase the verbosity of the log files for nxclient?
>>>>>
>>>>>
>>>> You are right this is a SSH problem, but I have no idea. Sometimes running nxsetup again can help.
>>>>
>>>> You might want to run sshd in debug mode.
>>>>
>>>> /etc/init.d/ssh stop
>>>>
>>>> sshd -v -v -v
>>>>
>>>> or so ...
>>>>
>>>> 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=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
>>>> ________________________________________________________________
>>>>
>>>>
>>> It could be just key mismatch....
>>>
>>> Compare the key of the server and client.
>>>
>>> Hristo Benev
>>> http://hbcom.info
>>> ________________________________________________________________
>>> 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
>>> ________________________________________________________________
>>>
>
> ________________________________________________________________
> 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
> ________________________________________________________________
>
All depend on the quality (compression level) and on services/apps.
With max compression even dial up is OK. (response time less than a second)
But for better quality WAN is recommended.
So you may calculate at 64Kb at minimum.
Hristo Benev
http://hbcom.info
More information about the FreeNX-kNX
mailing list