public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: bbcolo22 <bbcolo22@gmail.com>
To: cygwin@cygwin.com
Subject: Re: slow ssh login on a cygwin machine
Date: Wed, 29 Aug 2012 21:04:00 -0000	[thread overview]
Message-ID: <CAGyNrDfmz1Tr04UUTu3Cr4UUSHsZj+OrMoet310vOwghpS=BJA@mail.gmail.com> (raw)
In-Reply-To: <503E72C9.9070902@cygwin.com>

I tried. They don't know. But thanks anyway.

On Wed, Aug 29, 2012 at 1:52 PM, Larry Hall (Cygwin) [via Cygwin] <
ml-node+s1069669n92401h51@n5.nabble.com> wrote:

> On 8/29/2012 3:43 PM, bbcolo22 wrote:
>
> > I am having exactly the same problem that Ilya described. The problem
> > appeared out of nowhere 1 week ago on many (but not all) of our
> production
> > servers running COPSSH. No errors, but an SSH login that used to take
> 3-5
> > seconds now takes > 90 seconds. I can clear see a delay of exactly 45
> > seconds here:
> >
> > ...
> > debug1: Trying private key: /home/dbmsmonitor/.ssh/id_rsa
> > debug3: no such identity: /home/dbmsmonitor/.ssh/id_rsa
> > debug1: Offering DSA public key: /home/dbmsmonitor/.ssh/id_dsa
> > debug3: send_pubkey_test
> > debug2: we sent a publickey packet, wait for reply
> > (45 second delay).
> >
> > ... followed by a shorter, second delay at the same place the Ilya
> > described.
> >
> > Not all of our production servers (running COPSSH on Windows) have the
> > problem, but even rebooting a server can make the problem appear. I've
> > tried:
> >
> > - Different SSH clients (ssh, putty, etc.).
> > - Changing SSHD_CONFIG options. including turning off DNS (I can see
> that it
> > gets past the DNS lookup OK).
> > - Specifying many of the SSH -o client options.
> > - Reinstalling COPSSH.
> >
> > Any ideas? I'm desperate. :@(
>
> cygwin.com/acronyms/#BLODA?
>
> You'll really want to talk to the COPSSH folks about this.  Despite my
> off-hand suggestion of BLODA above, we don't support COPSSH here.  If
> the comment helps, great.  Otherwise, see COPSSH authors for support.
>
> --
> Larry
>
> _____________________________________________________________________
>
> A: Yes.
>  > Q: Are you sure?
>  >> A: Because it reverses the logical flow of conversation.
>  >>> Q: Why is top posting annoying in email?
>
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
>
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://cygwin.1069669.n5.nabble.com/slow-ssh-login-on-a-cygwin-machine-tp5558p92401.html
>  To unsubscribe from slow ssh login on a cygwin machine, click here<http://cygwin.1069669.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5558&code=YmJjb2xvMjJAZ21haWwuY29tfDU1NTh8MTk1MTU5NTg2OA==>
> .
> NAML<http://cygwin.1069669.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://cygwin.1069669.n5.nabble.com/slow-ssh-login-on-a-cygwin-machine-tp5558p92402.html
Sent from the Cygwin list mailing list archive at Nabble.com.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2012-08-29 20:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 15:00 Ilya Dogolazky
2012-02-28 15:03 ` Corinna Vinschen
2012-02-28 15:34   ` Ilya Dogolazky
2012-02-28 15:50     ` Corinna Vinschen
2012-02-28 16:55       ` Corinna Vinschen
2012-02-29 14:40         ` Ilya Dogolazky
2012-02-29 15:17           ` Corinna Vinschen
2012-08-29 20:12             ` bbcolo22
2012-08-29 20:42               ` Larry Hall (Cygwin)
2012-08-29 21:04                 ` bbcolo22 [this message]
2012-08-29 22:19                   ` Christopher Faylor
2012-08-29 23:42                     ` bbcolo22

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGyNrDfmz1Tr04UUTu3Cr4UUSHsZj+OrMoet310vOwghpS=BJA@mail.gmail.com' \
    --to=bbcolo22@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).