From: Andreas Enge <andreas@enge.fr>
To: Leo Famulari <leo@famulari.name>
Cc: 34580@debbugs.gnu.org
Subject: bug#34580: Service ssh-daemon could not be started
Date: Thu, 21 Feb 2019 00:08:07 +0100 [thread overview]
Message-ID: <20190220230807.GA13841@jurong> (raw)
In-Reply-To: <20190220225154.GA26281@jasmine.lan>
On Wed, Feb 20, 2019 at 05:51:54PM -0500, Leo Famulari wrote:
> On Wed, Feb 20, 2019 at 11:48:02PM +0100, Andreas Enge wrote:
> > I suppose so. I would be happy to provide further information, but there is
> > not much to see in the log files.
I grepped for "ssh" in /var/log/messages.
The failure on boot:
Feb 19 22:02:20 localhost vmunix: [ 6.712592] random: ssh-keygen: uninitialized urandom read (32 bytes read)
Feb 19 22:02:10 localhost sshd[359]: Server listening on 0.0.0.0 port 22.
Feb 19 22:02:25 localhost shepherd[1]: Service ssh-daemon could not be started.
And then starting by hand:
Feb 19 22:03:48 localhost sshd[380]: Server listening on 0.0.0.0 port 22.
Feb 19 22:03:48 localhost sshd[380]: Server listening on :: port 22.
Feb 19 22:03:48 localhost shepherd[1]: Service ssh-daemon has been started.
It looks as if ssh-keygen takes too long; this is called from
openssh-activation in services/ssh.scm, with a comment
"Generate missing host keys". Are these regenerated at each boot?
If yes, is there a race condition, one action not waiting for the
previous one to finish?
Andreas
next prev parent reply other threads:[~2019-02-20 23:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 21:21 bug#34580: Service ssh-daemon could not be started Andreas Enge
2019-02-20 22:21 ` Leo Famulari
2019-02-20 22:48 ` Andreas Enge
2019-02-20 22:51 ` Leo Famulari
2019-02-20 23:08 ` Andreas Enge [this message]
2019-02-20 23:56 ` Leo Famulari
2019-03-14 22:11 ` Leo Famulari
2019-03-15 16:35 ` Leo Famulari
2019-02-22 6:52 ` Chris Marusich
2019-09-20 20:00 ` Brant Gardner
2019-09-24 8:08 ` Ludovic Courtès
2019-09-24 12:20 ` Brant Gardner
2019-09-26 20:48 ` Ludovic Courtès
2019-09-27 14:57 ` Brant Gardner
2019-09-28 9:45 ` Ludovic Courtès
2019-09-28 12:38 ` Brant Gardner
2019-09-28 13:54 ` pelzflorian (Florian Pelz)
2019-09-28 17:44 ` Ludovic Courtès
2019-09-28 18:23 ` Danny Milosavljevic
2019-09-28 18:31 ` Danny Milosavljevic
2019-09-28 19:47 ` Ludovic Courtès
2019-09-28 19:47 ` Ludovic Courtès
2019-09-29 13:02 ` Brant Gardner
2019-09-28 14:11 ` Ludovic Courtès
2019-10-09 14:49 ` Brant Gardner
2019-10-11 10:14 ` Ludovic Courtès
2019-10-12 12:09 ` Brant Gardner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190220230807.GA13841@jurong \
--to=andreas@enge.fr \
--cc=34580@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).