1 |
Grant wrote: |
2 |
|
3 |
> >>> >> If it doesn't start I'm locked out of the remote system. |
4 |
> >>> > |
5 |
> >>> > You may be interested in : |
6 |
> >>> > /etc/init.d/sshd reload |
7 |
> >>> |
8 |
> >>> I get: |
9 |
> >>> |
10 |
> >>> # /etc/init.d/sshd reload |
11 |
> >>> * Reloading sshd ... |
12 |
> >>> No /usr/sbin/sshd found running; none killed. [ ok ] |
13 |
|
14 |
"/etc/init.d/ssh zap" should do it. If "/etc/init.d/ssh start" then still |
15 |
does not work, you may need to kill -9 the running sshd server. You may |
16 |
do this, running ssh sessions will not be terminated by this. |
17 |
|
18 |
You can also start/test the new sshd parallel to the running old one, but |
19 |
on another port: /usr/sbin/sshd -p 12345. Then connect with ssh -p 12345. |
20 |
|
21 |
[...] |
22 |
> >> When is the last time you did an etc-update? |
23 |
> > |
24 |
> > I just checked on my system. sshd is in /usr/bin/sshd. Not sbin. You |
25 |
> > have an outdated /etc/init.d/sshd file. You might need to etc-update, |
26 |
> > or reinstall sshd and run etc-update afterwards |
27 |
> |
28 |
> Thanks for helping me out with this. I re-emerged openssh and now |
29 |
> sshd restarts just fine. |
30 |
|
31 |
I just had the same problem. After upgrading from openssh-4.7_p1-r6 to |
32 |
5.1_p1-r1, /etc/init.d/sshd did not work. Configs had been updated |
33 |
already. I emerged 5.1_p1-r1 again, and now /etc/init.d/sshd works fine. |
34 |
|
35 |
Wonko |