From mboxrd@z Thu Jan 1 00:00:00 1970 From: Taegil Bae Subject: bug#30993: issue: ssh-daemon could not be started Date: Tue, 20 Nov 2018 10:33:17 +0900 Message-ID: References: <20180329200803.GA15842@jasmine.lan> <87efbgvk3o.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56137) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gOuvX-00024o-CN for bug-guix@gnu.org; Mon, 19 Nov 2018 20:34:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gOuvS-0006MA-Tt for bug-guix@gnu.org; Mon, 19 Nov 2018 20:34:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:57226) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gOuvS-0006LX-R0 for bug-guix@gnu.org; Mon, 19 Nov 2018 20:34:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gOuvS-0004G9-HO for bug-guix@gnu.org; Mon, 19 Nov 2018 20:34:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87efbgvk3o.fsf@gnu.org> Content-Language: en-US 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 30993@debbugs.gnu.org Hello, On 11/20/18 6:22 AM, Ludovic Courtès wrote: > Taegil Bae skribis: > >> I have experienced this issue on a slow machine (Thinkpad T60). By >> placing avahi-daemon after ssh-daemon, I fixed this issue. I added >> ssh-daemon into the requirement of avahi-shepherd-service, and >> reconfigured the system. > This is very surprising. Are you sure this is fully reproducible? > How would you explain this? At least in my machine it seems reproducible. I just reproduced that: reconfigured the system without my modification of avahi-daemon, checked ssh-daemon not started, reconfigured the system again with the modification, and then checked ssh-daemon started. I am not a professional. But I guess that avahi-daemon manipulates network things such as the host name, and ssh-daemon waits for that to be completed. Look at this failing case: Nov 20 09:37:57 localhost avahi-daemon[344]: Found user 'avahi' (UID 985) and group 'avahi' (GID 973). Nov 20 09:37:59 localhost avahi-daemon[344]: Successfully dropped root privileges. Nov 20 09:38:00 localhost avahi-daemon[344]: avahi-daemon 0.7 starting up. Nov 20 09:38:18 localhost shepherd[1]: Service avahi-daemon has been started. Nov 20 09:38:01 localhost avahi-daemon[344]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Nov 20 09:38:05 localhost avahi-daemon[344]: Successfully called chroot(). Nov 20 09:38:12 localhost avahi-daemon[344]: Successfully dropped remaining capabilities. Nov 20 09:38:32 localhost shepherd[1]: Service ssh-daemon could not be started. Nov 20 09:38:15 localhost avahi-daemon[344]: Loading service file /services/sftp-ssh.service. Nov 20 09:38:17 localhost avahi-daemon[344]: Loading service file /services/ssh.service. Nov 20 09:38:19 localhost avahi-daemon[344]: Network interface enumeration completed. Nov 20 09:38:22 localhost avahi-daemon[344]: Server startup complete. Host name is gravity.local. Local service cookie is 4157419020. Nov 20 09:38:29 localhost avahi-daemon[344]: Service "gravity" (/services/ssh.service) successfully established. Nov 20 09:38:32 localhost avahi-daemon[344]: Service "gravity" (/services/sftp-ssh.service) successfully established. Nov 20 09:38:36 localhost avahi-daemon[344]: write() failed while writing return value to pipe: Broken pipe Nov 20 09:39:12 localhost avahi-daemon[344]: Joining mDNS multicast group on interface wls3.IPv6 with address fe80::4c7d:9233:7845:eb88. Nov 20 09:39:12 localhost avahi-daemon[344]: New relevant interface wls3.IPv6 for mDNS. Nov 20 09:39:12 localhost avahi-daemon[344]: Registering new address record for fe80::4c7d:9233:7845:eb88 on wls3.*. Nov 20 09:39:12 localhost avahi-daemon[344]: Joining mDNS multicast group on interface wls3.IPv4 with address 192.168.42.242. Nov 20 09:39:12 localhost avahi-daemon[344]: New relevant interface wls3.IPv4 for mDNS. Nov 20 09:39:12 localhost avahi-daemon[344]: Registering new address record for 192.168.42.242 on wls3.IPv4. Regards, Taegil