[FreeNX-kNX] Timing Out

[Andrew Villano]

When I include -i it hangs. When I leave that out I get a password
prompt immediately.

 

Warmest Regards,

 

Andrew Villano

Systems Specialist

Incentient LLC

________________________________

From: chris at ccburton.com [mailto:chris at ccburton.com] 
Sent: Thursday, August 20, 2009 3:17 PM
To: User Support for FreeNX Server and kNX Client
Subject: Re: [FreeNX-kNX] Timing Out

 


Andrew Villano <AVillano at incentient.com> wrote on 20/08/2009 19:45:13:

> Also an strace shows 
>   
> poll([{fd=7, events=POLLIN}], 1, 5000)  = 0 (Timeout) 
> gettimeofday({1250793874, 701186}, NULL) = 0 
> poll([{fd=7, events=POLLOUT}], 1, 0)    = 1 ([{fd=7,
revents=POLLOUT}]) 
> send(7, "==\1\0\0\1\0\0\0\0\0\0\4mail\nincentient\3com"..., 37, 
> MSG_NOSIGNAL) = 37 
> poll([{fd=7, events=POLLIN}], 1, 5000 



Right . . . 





>   
> Warmest Regards, 
>   
> Andrew Villano 
> Systems Specialist 
> Incentient LLC 
> 
> From: Andrew Villano [mailto:AVillano at incentient.com
<mailto:AVillano at incentient.com> ] 
> Sent: Thursday, August 20, 2009 2:29 PM
> To: User Support for FreeNX Server and kNX Client
> Subject: Re: [FreeNX-kNX] Timing Out 
>   
> tail -f /var/log/nxserver.log shows nothing. 
>   
> However, I am seeing entries in /var/log/secure 
>   
> Aug 20 14:14:48 barolo sshd[11425]: Accepted publickey for nx from 
> 75.127.217.67 port 31185 ssh2 

20 seconds 

> Aug 20 14:15:08 barolo sshd[11425]: pam_unix(sshd:session): session 
> opened for user nx by (uid=0) 

spawn etc 

> Aug 20 14:15:30 barolo sshd[11416]: pam_unix(sshd:session): session 
> closed for user nx 
> Aug 20 14:15:46 barolo sshd[11419]: pam_unix(sshd:session): session 
> closed for user nx 
> Aug 20 14:16:08 barolo sshd[11425]: pam_unix(sshd:session): session 
> closed for user nx 


Yup 1 min 20 


But tells us not very much . . . 

However if you put the key in a key file and run :- 


C:\Program Files\NX Client for Windows\bin\nxssh.exe   -v  -l nx  -i
/path/to/nx/client.id_dsa.key  -p 12019 75.127.217.69 



Assuming you DO listen on 12019 not 22 lake you say below . . 



We will get lost of debug and should get an NX prompt. 



If you "time" it we will know if the delay is in this bit of the
connection or later . . . 




>   
> My node.conf 
>   
> Only options 
> SSHD_PORT=12019 
> ENABLE_SSH_AUTHENTICATION="1" 
> NX_LOG_LEVEL=6 
> NX_LOG_SECURE=1 
> NX_LOGFILE=/var/log/nxserver.log 
>   
> I touch'd /var/log/nxserver.log and chmod 777'd it and chown'd it to
nx.... 
>   
> Strange......... 
>   
> Warmest Regards, 
>   
> Andrew Villano 
> Systems Specialist 
> Incentient LLC 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20090820/160069a0/attachment.html>