[FreeNX-kNX] Unexpected timeout connecting

[Colin McKinnon]

On Wednesday 24 November 2004 12:43, Fabian Franz wrote:
> Am Mittwoch, 24. November 2004 10:09 schrieb Colin McKinnon:
> > On Tuesday 23 November 2004 20:40, Arnd Benninghoff wrote:
> > > Check the number of running nxagent-processes and kill them all.
> >
> > None :(
>
> What about ulimits? Do you have any in effect?
>

Just the defaults which seem generous enough (on the server):
core file size        (blocks, -c) 0
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) unlimited
max memory size       (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size          (512 bytes, -p) 8
stack size            (kbytes, -s) 8192
cpu time             (seconds, -t) unlimited
max user processes            (-u) unlimited
virtual memory        (kbytes, -v) unlimited

Client setup is similar, but max user processes 3839.

Is there anywhere a description of how [Free]Nx works? I've only been able to 
find the docs on the nomachine site which don't go into a lot of detail (and 
reading the source just gives too much for me to cope with!). I'm trying to 
get a 2nd installation going and I've got key files all over the place.

Ta,

>
> This is a really strange message at that part of the auth stage and should
> not happen. You should investigate _why_ it is killed.
>
> I just could think of ulimits having automatically killed processed, but I
> dunno.
>

Any suggestions how to proceed? I don't think its a ulimit thing - watching 
top for processor and memory usage doesn't even blip on the server when I 
connect.

There does seem to be some data not getting back to the client - while the 
client says 'Authentication completed', netstat on the server is reporting:

Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 cpc5-renf1-6-0-cust:ssh no-dns-yet.demon.:36394 
ESTABLISHED
tcp        0     48 cpc5-renf1-6-0-cust:ssh no-dns-yet.demon.:36388 
ESTABLISHED

(first connection is me monitoring from the client, second connection is nx) 
The send-Q sticks at 48 until the connection disappears and the client 
program reports a timeout.

Colin