From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: ssh-daemon service fails to auto start Date: Sun, 11 Feb 2018 10:31:17 +0100 Message-ID: <87r2prlvoa.fsf@gmail.com> References: <9565fcd0-48eb-aac8-3c30-b3477f3d7f55@uni-bremen.de> <87wp00k3ce.fsf@gnu.org> <70093a20-9a2c-12d3-c59d-53796328fb9f@uni-bremen.de> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49945) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eknyp-00056X-Le for help-guix@gnu.org; Sun, 11 Feb 2018 04:31:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eknyn-0001bq-1o for help-guix@gnu.org; Sun, 11 Feb 2018 04:31:27 -0500 In-Reply-To: <70093a20-9a2c-12d3-c59d-53796328fb9f@uni-bremen.de> (Martin Castillo's message of "Tue, 6 Feb 2018 19:49:16 +0100") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Martin Castillo Cc: help-guix@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Martin Castillo writes: > On 29.01.2018 18:00, Ludovic Court=C3=A8s wrote: >> Hi Martin, >>=20 >> Martin Castillo skribis: >>=20 >>> i have a problem with the ssh-service. I want it to autostart on system >>> boot. >>> >>> my configuration is (similar to) desk,nossh.scm. >>=20 >> I tried this config in =E2=80=98guix system vm=E2=80=99 and sshd is auto= matically >> started on boot, as can be seen with =E2=80=98herd status ssh-daemon=E2= =80=99 etc. >>=20 >> Does this config work for you in =E2=80=98guix system vm=E2=80=99? > > No. > > >> Could you check /var/log/shepherd.log? It will tell you which services, >> besides sshd, failed to start. >>=20 >> =E2=80=98ssh-daemon=E2=80=99 depends only on =E2=80=98syslogd=E2=80=99, = so as long as =E2=80=98syslogd=E2=80=99 is >> started, =E2=80=98ssh-daemon=E2=80=99 should start. >>=20 > > I checked /var/log/shepherd.log. Only user-homes and ssh-daemon could > not be started. > > Has this maybe to do with missing randomness to create keys? (Even > though there are already server keys.) > > Maybe shepherd should store the output of launched programs? Is that > really not possible? I can't be the first one to need that. > > Martin I have experienced this problem as well. SSH daemon fails to start, but unfortunately Shepherd has nothing useful to say about why. If I ever find a way to reproduce it reliably, I'll share that info. I think multiple people have reported this problem on IRC. It can't be a coincidence... =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAlqADWYACgkQ3UCaFdgi Rp0cJQ//RjhQysgnyPnWt83PoLCamre2DLVI4dHctR2p9zEB611Znc8sNErSadeE T9dKMMphgwGFs/+oRCDRo11Ei0fCIFbLaHOmAwLDUBzbpH1XqPKD1fy+7GFJLaUX LXy2NN0qrmQHOxGgqMaeekZdfsLmb2OyUJFCJKReiX3Egb1XZFJ0RdnZAtFQPL8q qcVmgqnN1eeT6u3x4mdK1CKObf4zLR4iIDI0IOka4hJ5kOBc7h4qMbgBvzcLHQvQ 7RORdrYGd4tsVUbIarCrV1j3GNiVzAZLV3+nrpbi+N6EM0SNgs9/R24lK2yXUHHi 4F3Llxa049ezzRxTBiarYpP5FNxyRQXIHal6IvjfzyHXouv6J9PX7g+TqwsFzZFp qCNGuiZZ1Gv1q4pq5mEM8/X7HteaPQsFvr4rUuStk7pHmcoOoM1uxXlMf+J2YWDQ qFDazsVNSalpatX7Mm4Wl6f3WMdHNx/Lp8J7QE6wyg+OdNfpB9LX4Vu0JBsYWfk0 Vg/oxdC9FVseX1/dJjKFJWLvUXOBV8FQciLvWgnRd43MWT6a0QF3uKhGOk0Nrcv+ qO2vsNU82+Sp+E1TbcSiMLkwQJfaDx3j0XDvRc27O/FR3E/F5v2+GZ/RZBW0TBcf bKt6WX0yTcDoQLhnwUSPbcot9RzsyYpGhw9/51ALgxSXZkm0UbU= =iwpf -----END PGP SIGNATURE----- --=-=-=--