From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Brant Gardner" Subject: bug#34580: Service ssh-daemon could not be started Date: Fri, 20 Sep 2019 15:00:40 -0500 Message-ID: References: <20190219212126.GA2371@jurong> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=10d46c19ef214cde95868cc7d632710f Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39599) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBP7P-0005Io-Ah for bug-guix@gnu.org; Fri, 20 Sep 2019 16:03:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iBP7O-00064k-85 for bug-guix@gnu.org; Fri, 20 Sep 2019 16:03:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:49746) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iBP7N-00064Y-VC for bug-guix@gnu.org; Fri, 20 Sep 2019 16:03:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iBP7N-0002sT-Qg for bug-guix@gnu.org; Fri, 20 Sep 2019 16:03:01 -0400 In-Reply-To: <20190219212126.GA2371@jurong> Sender: "Debbugs-submit" Resent-Message-ID: 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: 34580@debbugs.gnu.org --10d46c19ef214cde95868cc7d632710f Content-Type: text/plain Adding my nickel here, I observed the exact same behavior yesterday. I have several Guix System instances, this is currently the only one that has exhibited the problem of ssh failing to start and logging no messages about it. Networking: (static-networking-service "enp1s0" "192.168.1.253" #:gateway "192.168.1.100" #:name-servers '("192.168.1.123" "192.168.1.252")) The most useful thing I could find in the logs: Sep 19 15:30:46 localhost sshd[261]: Server listening on 0.0.0.0 port 22. Sep 19 15:31:19 localhost shepherd[1]: Service ssh-daemon could not be started. Sep 19 15:39:58 localhost sshd[585]: Server listening on 0.0.0.0 port 22. Sep 19 15:39:58 localhost sshd[585]: Server listening on :: port 22. Sep 19 15:39:59 localhost shepherd[1]: Service ssh-daemon has been started. The 15:30/15:31 lines are the boot messages, the 15:39 messages are my manual call to 'herd start ssh-daemon'. -- Brant Gardner --10d46c19ef214cde95868cc7d632710f Content-Type: text/html Content-Transfer-Encoding: quoted-printable
Adding my = nickel here, I observed the exact same behavior=20 yesterday.  I have several Guix System instances, this is currently= the=20 only one that has exhibited the problem of ssh failing to start and=20 logging no messages about it.

Networking:

       &n= bsp;     (static-networking-service
&n= bsp;           &n= bsp; "enp1s0" "192.168.1.253"
    &nbs= p;         #:gateway "192.168.1.= 100"
         = ;     #:name-servers '("192.168.1.123" "192.168.1.25= 2"))

The most useful thing I could find in = the logs:

Sep 19 15:30:46 localhost sshd[26= 1]: Server listening on 0.0.0.0 port 22.
Sep 19 15:31:19 l= ocalhost shepherd[1]: Service ssh-daemon could not be started.
=
Sep 19 15:39:58 localhost sshd[585]: Server listening on 0.0.0.0 po= rt 22.
Sep 19 15:39:58 localhost sshd[585]: Server listeni= ng on :: port 22.
Sep 19 15:39:59 localhost shepherd[1]: S= ervice ssh-daemon has been started.

The 15:= 30/15:31 lines are the boot messages, the 15:39 messages are my manual c= all to 'herd start ssh-daemon'.

--
Br= ant Gardner



--10d46c19ef214cde95868cc7d632710f--