GNU bug report logs - #33299
'ssh-daemon' fails to start

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 33299 in the body.
You can then email your comments to 33299 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: swedebugia <swedebugia <at> riseup.net>
To: bug-guix <at> gnu.org
Subject: shepherd: Service ssh-daemon could not be started.
Date: Wed, 7 Nov 2018 11:03:10 +0100

[Message part 1 (text/plain, inline)]

Hi

This morning I started my GuixSD VM as usual.

Openssh server was not running even though it was enabled and should 
have been respawned. Hmm.

Lucky for me SSH is not the only way into this system...

From the host I got:

$ ssh  sdb <at> localhost -p10022
ssh_exchange_identification: read: Connection reset by peer

On the guest:

$ grep -3 "ssh-daemon could not /var/log/messages
Nov  7 07:19:30 localhost vmunix: [    0.366701] VFS: Dquot-cache hash 
table entries: 512 (order 0, 4096 bytes)
Nov  7 07:19:30 localhost vmunix: [    0.367764] AppArmor: AppArmor 
Filesystem Enabled
Nov  7 07:19:30 localhost vmunix: [    0.368569] pnp: PnP ACPI init
Nov  7 07:19:31 localhost shepherd[1]: Service ssh-daemon could not be 
started.
Nov  7 07:19:31 localhost vmunix: [    0.370291] pnp: PnP ACPI: found 6 
devices
Nov  7 07:19:31 localhost vmunix: [    0.378960] clocksource: acpi_pm: 
mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
Nov  7 07:19:31 localhost vmunix: [    0.380434] NET: Registered 
protocol family 2

Herd said:

$ cat sshd-stopped
Status of ssh-daemon:
  It is stopped.
  It is enabled.
  Provides (ssh-daemon).
  Requires (syslogd).
  Conflicts with ().
  Will be respawned.               <-- not true!

Starting it yielded:

$ cat sshd-start
Service ssh-daemon has been started.

How do I increase the verbosity of shepherd? I did not find anything 
about that in the shepherd manual 
<https://www.gnu.org/software/shepherd/manual/shepherd.html#Invoking-shepherd>.

Is there a way to debug further?

-- 
Cheers
Swedebugia
PS
$ guix --version
guix (GNU Guix) 1f44934fb6e2cefccbecd4fa347025349fa9ff76 (=0.15

[Message part 2 (text/html, inline)]

Message #12 received at 33299 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: swedebugia <swedebugia <at> riseup.net>
Cc: 33299 <at> debbugs.gnu.org, 30993 <at> debbugs.gnu.org
Subject: Re: bug#33299: shepherd: Service ssh-daemon could not be started.
Date: Wed, 07 Nov 2018 22:36:33 +0100

Hello,

swedebugia <swedebugia <at> riseup.net> skribis:

> This morning I started my GuixSD VM as usual.
>
> Openssh server was not running even though it was enabled and should
> have been respawned. Hmm.

This seems to be the same issue as described in
<https://issues.guix.info/issue/30993> (I’ve now merged both).

It’s a serious problem…

Thanks for reporting it,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.