Bug#794755: systemd kills ssh-server

[Michael Biebl]

[please always CC the bug report]

Am 06.08.2015 um 14:58 schrieb qwer at vienna.at:
> On Thu, Aug 06, 2015 at 01:25:59PM +0200, Michael Biebl wrote:
>> It looks like ssh service is restarted too often within a short period
> 
> Perfectly true.
> 
>> of time due to some external process (most likely the if-up.d hook).
> 
> Yes.
> 
>> Therefor systemd marks the service as failed, it's not that systemd
>> kills ssh-server.
> 
> But how to restart the ssh-server?
> Well, I did have to change one ethernet-card serving the ssh-server.
> And /etc/init.d/ssh of course not can be used.
> journalctl -xb shows quite nice that the ssh-server can't be started.
> But I really would like to have it again in spite of using telnet-SSL.
> But I don't know how to do it.

You can reset the failed-state via
systemctl reset-failed foo.service

Btw, it seems the return code from ssh was 255.
That typically indicates a configuration error which you might investigate.
journalctl -u ssh.service
should give you the full log.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150806/263e0f31/attachment-0002.sig>