On 2015-04-08 16:45:16 -0600, Bob Proulx wrote:
> I see mdns there and immediately have an immune reaction due to many
> problems with it before. As you have already determined it is the
> source of your current 5 second timeout. I recommend purging
> libnss-mdns from your system. That will solv
On 09/04/2015 9:38 AM, "Igor Cicimov" wrote:
>
>
> On 09/04/2015 3:11 AM, "Vincent Lefevre" wrote:
> >
> > When connecting by SSH to a particular machine, ssh hangs for
> > 5 seconds. The client machine doesn't matter (except for the
> >
On 09/04/2015 3:11 AM, "Vincent Lefevre" wrote:
>
> When connecting by SSH to a particular machine, ssh hangs for
> 5 seconds. The client machine doesn't matter (except for the
> machine itself). For instance:
>
> xvii:~> ssh -vvv 2>>(ts -s "%.s"
Vincent Lefevre wrote:
> Vincent Lefevre wrote:
> > Bob Proulx wrote:
> nameserver 140.77.1.32
> nameserver 140.77.167.2
That is a second potential source of timeout.
man resolv.conf
nameserver Name server IP address
Internet address of a name server that the resolve
On 2015-04-09 00:09:08 +0200, Vincent Lefevre wrote:
> According to
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414569
> "avahi-daemon: delay on resolving IP addresses when mdns is
> specified in /etc/nsswitch.conf"
>
> the 5-second delay shouldn't occur, as this bug was fixed wit
On 2015-04-08 23:57:53 +0200, Vincent Lefevre wrote:
> On 2015-04-08 14:27:38 -0600, Bob Proulx wrote:
> > grep "^hosts" /etc/nsswitch.conf
>
> hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
[...]
> [...]
> 23:54:03 mprotect(0x7f5b92ff3000, 4096, PROT_READ) = 0
> 23:54:03 munmap
On 2015-04-08 14:27:38 -0600, Bob Proulx wrote:
> Vincent Lefevre wrote:
> > Yes, but with nslookup, the failure is *immediate*. So, this doesn't
> > explain the 5-second delay.
>
> What is the configuration of /etc/resolv.conf? /etc/nsswitch.conf?
>
> cat /etc/resolv.conf
domain lip.ens-lyon
Vincent Lefevre wrote:
> Michael Graham wrote:
> > Vincent Lefevre wrote:
> > > # /usr/sbin/sshd -D -ddd -p 80 -f /etc/ssh/sshd_config 2>>(ts -s "%.s")
> > > [...]
> > > (I use port 80 since port 22 is already taken by the normal sshd and
> > > the gateway to the machine seems to filter arbitrary
On 2015-04-08 13:46:06 -0400, Michael Graham wrote:
> On 8 April 2015 at 13:41, Vincent Lefevre wrote:
> > # /usr/sbin/sshd -D -ddd -p 80 -f /etc/ssh/sshd_config 2>>(ts -s "%.s")
> > [...]
> > 3.315346 debug3: Trying to reverse map address 140.77.51.8.
>
> So sshd is doing the reverse lookup and
On 8 April 2015 at 13:41, Vincent Lefevre wrote:
> # /usr/sbin/sshd -D -ddd -p 80 -f /etc/ssh/sshd_config 2>>(ts -s "%.s")
> [...]
> 3.315346 debug3: Trying to reverse map address 140.77.51.8.
So sshd is doing the reverse lookup and fails
> ypig:~> nslookup 140.77.51.8
> ;; Got SERVFAIL reply fr
On 2015-04-08 19:21:12 +0200, Sven Hartge wrote:
> Vincent Lefevre wrote:
>
> > When connecting by SSH to a particular machine, ssh hangs for
> > 5 seconds. The client machine doesn't matter (except for the
> > machine itself).
>
> 5 seconds smells like some D
Vincent Lefevre wrote:
> When connecting by SSH to a particular machine, ssh hangs for
> 5 seconds. The client machine doesn't matter (except for the
> machine itself).
5 seconds smells like some DNS problem.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
--
To UNSUBSC
When connecting by SSH to a particular machine, ssh hangs for
5 seconds. The client machine doesn't matter (except for the
machine itself). For instance:
xvii:~> ssh -vvv 2>>(ts -s "%.s") ypig
[...]
0.278462 debug2: key: /home/vinc17/.ssh/id_rsa (0x7f943e415e90), expli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florian Kulzer wrote:
> On Sun, Jun 17, 2007 at 12:12:46 -0400, Allan Wind wrote:
>> On 2007-06-17T16:44:52+0200, "Jørgen P. Tjernø" wrote:
>>> I'm having some issues with ssh taking about ~12 seconds to connect -
>>> but the ssh session itself is snap
On Sun, Jun 17, 2007 at 12:12:46 -0400, Allan Wind wrote:
> On 2007-06-17T16:44:52+0200, "Jørgen P. Tjernø" wrote:
> > I'm having some issues with ssh taking about ~12 seconds to connect -
> > but the ssh session itself is snappy - no lag at all.
>
> [...]
>
> > Anyone have any suggestions? :-)
>
On 2007-06-17T16:44:52+0200, "Jørgen P. Tjernø" wrote:
> I'm having some issues with ssh taking about ~12 seconds to connect -
> but the ssh session itself is snappy - no lag at all.
[...]
> Anyone have any suggestions? :-)
It probably trying to do a forward or reverse DNS lookup. Does it make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having some issues with ssh taking about ~12 seconds to connect -
but the ssh session itself is snappy - no lag at all. The load average
on the remote host is fine, and both local and remote DNS queries work
like they should. The problem is there w
Hi,
I've been having problems ssh'ing into one of my debian "woody" 3.0r2
boxes. I can ssh into the box and move around somewhat but if I do a
long listing like ls -l on /usr/lib or bring up a top in a ssh window
the ssh connection seems to hang and won't free itself. Some times if I
create ano
Both I and a friend have noticed that our slogin connections
hang (timeout?) after not using our connections for about 15 minutes.
I noticed this hanging after I upgraded from potato to woody
about 10 months ago, and my friend noticed this hanging
after he upgraded from potato to woody about 3 m
Dimitri Maziuk <[EMAIL PROTECTED]> writes:
> * Bill Wohler ([EMAIL PROTECTED]) spake thusly:
> > I just started noticing that ssh hangs with X commands. I believe
> > this behavior began with the recent ssh upgrade on woody.
>
> Try "ssh -1".
>
&
* Bill Wohler ([EMAIL PROTECTED]) spake thusly:
> I just started noticing that ssh hangs with X commands. I believe
> this behavior began with the recent ssh upgrade on woody.
Try "ssh -1".
I get this a lot when connecting to ssh-2.5.1p2 on IRIX, with
tty logins as well
I just started noticing that ssh hangs with X commands. I believe
this behavior began with the recent ssh upgrade on woody.
For example, if you run "ssh host date", you get your prompt back.
However, if you run "ssh host xterm" and log out of the term, the
xterm goes
22 matches
Mail list logo
