Re: remote port forwarding unstable
- From: Adriana Rodean <adrya1984@xxxxxxxxx>
- Date: Tue, 20 Oct 2009 08:53:49 +0300
Hi,
Here is some more info after little investigation :)
Message i get is: "Warning: remote port forwarding failed for listen port 1026"
SSH makes connection but port isn't opened and in server logs i see:
IPP-Linux:~# cat /var/log/auth.log | grep 18722
Oct 19 13:37:20 IPP-Linux sshd[18722]: error: bind: Address already in use
Oct 19 13:37:20 IPP-Linux sshd[18722]: error:
channel_setup_fwd_listener: cannot listen to port: 1026
IPP-Linux:~# cat /var/log/auth.log | grep 18737
Oct 19 13:37:47 IPP-Linux sshd[18737]: error: bind: Address already in use
Oct 19 13:37:47 IPP-Linux sshd[18737]: error:
channel_setup_fwd_listener: cannot listen to port: 1026
But i closed the previous console with ssh listening to that port, and
is no ssh process on client when i want to connect again on the same
port. So how come it still says that port is in use on server?
This happens in only 2% of the cases, very rare, i change nothing in
the way i connect or close the client, but somehow it seems that port
still hangs on server after closing ssh console ... or at least that's
what sshd says because with "netstat -an" i don't see that port busy
Thank you Rabbi for that command, next time when it happens i'll use it :)
Thanks,
Adriana
- Follow-Ups:
- Re: remote port forwarding unstable
- From: Greg Wooledge
- Re: remote port forwarding unstable
- From: Quintin Beukes
- Re: remote port forwarding unstable
- References:
- remote port forwarding unstable
- From: Adriana Rodean
- remote port forwarding unstable
- Prev by Date: Re: Manipulating Forwards on an existing shell
- Next by Date: Re: Manipulating Forwards on an existing shell
- Previous by thread: remote port forwarding unstable
- Next by thread: Re: remote port forwarding unstable
- Index(es):
Relevant Pages
|