1 |
> > > I don't see how that could be because I was able to log in when the |
2 |
> > > system was freshly booted yesterday. I'll grab a monitor and keyboard |
3 |
> > > from the garage, have a look, and report back here. |
4 |
> > |
5 |
> > when I have problems with ssh, I run another instance in debug mode: |
6 |
> > |
7 |
> > In one terminal (local box): |
8 |
> > |
9 |
> > /usr/sbin/sshd -p 2222 -d |
10 |
> > |
11 |
> > from remote box: |
12 |
> > |
13 |
> > ssh $machine -p 2222 |
14 |
> > |
15 |
> > then you can look at the output from the local box to see what's going on. |
16 |
> > |
17 |
> > very handy. |
18 |
> |
19 |
> As well as checking the firewall and syslog messages on the server. |
20 |
> |
21 |
> Here's another long shot: If your physical network (cables, connectors, etc) |
22 |
> are playing up you could be dropping packets, which will leave TCP |
23 |
> connections hanging and cause the maximum connection limit to be reached. |
24 |
> ifconfig should show errors in this case. |
25 |
|
26 |
I'm on the box now and it's quite non-functional. ctrl+alt+del prints |
27 |
"INIT: cannot execute "/sbin/shutdown". I'm going to do a hard reset |
28 |
and we'll see what happens. |
29 |
|
30 |
- Grant |
31 |
-- |
32 |
gentoo-user@g.o mailing list |