From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: bug#34580: Service ssh-daemon could not be started Date: Thu, 21 Feb 2019 00:08:07 +0100 Message-ID: <20190220230807.GA13841@jurong> References: <20190219212126.GA2371@jurong> <20190220222158.GA24808@jasmine.lan> <20190220224802.GA13647@jurong> <20190220225154.GA26281@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([209.51.188.92]:41264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gwazn-00054N-Mo for bug-guix@gnu.org; Wed, 20 Feb 2019 18:09:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gwaz9-0004ar-F7 for bug-guix@gnu.org; Wed, 20 Feb 2019 18:09:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:57976) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gwaz8-0004Z8-Ci for bug-guix@gnu.org; Wed, 20 Feb 2019 18:09:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gwaz7-0003Hp-UB for bug-guix@gnu.org; Wed, 20 Feb 2019 18:09:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20190220225154.GA26281@jasmine.lan> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Leo Famulari Cc: 34580@debbugs.gnu.org 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