> > > I don't see how that could be because I was able to log in when the
> > > system was freshly booted yesterday.  I'll grab a monitor and keyboard
> > > from the garage, have a look, and report back here.
> >
> > when I have problems with ssh, I run another instance in debug mode:
> >
> > In one terminal (local box):
> >
> > /usr/sbin/sshd -p 2222 -d
> >
> > from remote box:
> >
> > ssh $machine -p 2222
> >
> > then you can look at the output from the local box to see what's going on.
> >
> > very handy.
>
> As well as checking the firewall and syslog messages on the server.
>
> Here's another long shot:  If your physical network (cables, connectors, etc)
> are playing up you could be dropping packets, which will leave TCP
> connections hanging and cause the maximum connection limit to be reached.
> ifconfig should show errors in this case.

I'm on the box now and it's quite non-functional.  ctrl+alt+del prints
"INIT: cannot execute "/sbin/shutdown".  I'm going to do a hard reset
and we'll see what happens.

- Grant
-- 
[EMAIL PROTECTED] mailing list

Reply via email to