public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: overseers@sources.redhat.com
Subject: Re: ssh: connect to address 209.249.29.67 port 22: Connection refused
Date: Sat, 21 Dec 2002 09:46:00 -0000	[thread overview]
Message-ID: <20021221173117.GA22292@redhat.com> (raw)
In-Reply-To: <Pine.BSF.4.44.0212210737001.45761-100000@dair.pair.com>

On Sat, Dec 21, 2002 at 08:10:59AM -0500, Hans-Peter Nilsson wrote:
>This when trying some cvs operations.  An interesting detail is
>that I *have* one ssh shell connection active, open since
>"7:11pm" (PST?) yesterday.  Perhaps I'm only allowed one
>connection at a time?  I have to finish the htdig stuff before
>trying that theory. ;-)

I restarted sshd last night to reset a keep alive parameter in the hopes
that it would alleviate the problem with many open stalled ssh
connections.  I carefully tested the connection to make sure that it
was still up but apparently it died sometime thereafter.

>BTW, it seems that reverse dns lookup (e.g.  dig, nslookup) doesn't
>work for 209.249.29.67 anymore.

It seems to be flaky.  Sometimes it works, sometimes it doesn't.  It's
going to change soon, so I'm not too worried.

I restarted sshd.  Wish I knew what stopped it to begin with.  It was
probably me but I don't see how I did it.  I just used a
"service sshd restart".

I tried it again just now and it restarted sshd just fine.  Weird.

cgf

  reply	other threads:[~2002-12-21 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-21  8:11 Hans-Peter Nilsson
2002-12-21  9:46 ` Christopher Faylor [this message]
2002-12-21 15:43   ` Hans-Peter Nilsson
  -- strict thread matches above, loose matches on Subject: below --
2002-10-06  8:14 Hans-Peter Nilsson
2002-10-06 10:44 ` Christopher Faylor

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=20021221173117.GA22292@redhat.com \
    --to=cgf@redhat.com \
    --cc=hp@bitrange.com \
    --cc=overseers@sources.redhat.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).