public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Phil Edwards <phil@jaj.com>
Cc: law@redhat.com, geoffk@geoffk.org,
	David Edelsohn <dje@watson.ibm.com>,
	overseers@sources.redhat.com
Subject: Re: SSH CVS problem
Date: Fri, 24 Jan 2003 15:11:00 -0000	[thread overview]
Message-ID: <20030124151136.GA8500@redhat.com> (raw)
In-Reply-To: <20030124145106.GA1006@disaster.jaj.com>

On Fri, Jan 24, 2003 at 09:51:06AM -0500, Phil Edwards wrote:
>On Thu, Jan 23, 2003 at 10:06:57PM -0700, law@redhat.com wrote:
>> In message <200301240439.XAA23822@makai.watson.ibm.com>, David Edelsohn writes:
>>  >	Sometime between 9:49pm EST and 11:30pm EST on Thursday, SSH
>>  >started refusing connections from me:
>>  >
>>  >Updating CVS tree
>>  >ssh: connect to address 66.187.233.205 port 22: Connection refused
>>  >cvs [update aborted]: end of file from server (consult above messages if any)
>>  >Adjusting file timestamps
>>  >CVS update of full tree failed.
>>  >
>>  >
>>  >	Did someone change an IP address filter?
>> More likely this means the SSH server has died or something like
>> that -- I can't connect to the SSH server either.
>
>So who's in the Raleigh office that can walk over to the box and frob it?
>
>On a longer-term note, wasn't sshd running under one of those "supervisory"
>programs that would notice such a crash and restart it?  Even just running
>it out of inittab might work.

sshd has been restarted.  Don't know why it crashed.  I'm investigating.

cgf

      reply	other threads:[~2003-01-24 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24  4:39 David Edelsohn
2003-01-24  5:02 ` law
2003-01-24 14:51   ` Phil Edwards
2003-01-24 15:11     ` Christopher Faylor [this message]

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=20030124151136.GA8500@redhat.com \
    --to=cgf@redhat.com \
    --cc=dje@watson.ibm.com \
    --cc=geoffk@geoffk.org \
    --cc=law@redhat.com \
    --cc=overseers@sources.redhat.com \
    --cc=phil@jaj.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).