From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#34580: Service ssh-daemon could not be started Date: Sat, 28 Sep 2019 16:11:20 +0200 Message-ID: <87impctss7.fsf@gnu.org> References: <20190219212126.GA2371@jurong> <87pnjqm809.fsf@gnu.org> <6d672221-0e2f-40cd-b129-1f893fe13472@www.fastmail.com> <87o8z6kclh.fsf@gnu.org> <75efee63-c5e4-4d7f-aec2-e1afa3a8ba00@www.fastmail.com> <87pnjkzrca.fsf@gnu.org> <754a6968-2d9e-431d-a545-7580fd81b7db@www.fastmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:45448) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iEDS7-0001Ha-92 for bug-guix@gnu.org; Sat, 28 Sep 2019 10:12:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iEDS6-00073q-3b for bug-guix@gnu.org; Sat, 28 Sep 2019 10:12:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:42167) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iEDS6-00073X-0l for bug-guix@gnu.org; Sat, 28 Sep 2019 10:12:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iEDS5-0008Ij-Ng for bug-guix@gnu.org; Sat, 28 Sep 2019 10:12:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <754a6968-2d9e-431d-a545-7580fd81b7db@www.fastmail.com> (Brant Gardner's message of "Sat, 28 Sep 2019 07:38:49 -0500") 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: Brant Gardner Cc: 34580@debbugs.gnu.org "Brant Gardner" skribis: > Okay, I did those steps exactly: > > - clone > - patch -p1 < your-patch > - ./bootstrap > - ./configure --localstatedir=3D/var > - make check > - sudo -E ./pre-inst-env guix system reconfigure /path/to/myconfig.scm > - reboot > > I had no issues or errors at any step and on reboot ssh-daemon tried & fa= iled to start so all went according to plan, but /tmp does *not* have a ssh= log file in it. > > Not sure where this went sideways, any advice? Does the PID that =E2=80=98herd status ssh-daemon=E2=80=99 reports (under = =E2=80=9CRunning value=E2=80=9D) correspond to =E2=80=98strace=E2=80=99? BTW, it may be that the problem will show up less frequently because sshd starts more slowly when running under =E2=80=98strace=E2=80=99. That= =E2=80=99s the hard part with timing-related bugs=E2=80=A6 Thanks for testing! Ludo=E2=80=99.