From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Cournoyer Subject: bug#39708: nfs-service-type broken: rpc.mountd respawns too quickly Date: Sat, 07 Mar 2020 22:19:35 -0500 Message-ID: <8736aj7cu0.fsf@gmail.com> References: <878skw382o.fsf@apteryx.i-did-not-set--mail-host-address--so-tickle-me> <87a75azxu2.fsf@gnu.org> 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]:42552) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAmTz-0002Qi-QU for bug-guix@gnu.org; Sat, 07 Mar 2020 22:20:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jAmTy-00027a-BS for bug-guix@gnu.org; Sat, 07 Mar 2020 22:20:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:41837) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jAmTy-00027W-80 for bug-guix@gnu.org; Sat, 07 Mar 2020 22:20:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jAmTy-0007Sb-2n for bug-guix@gnu.org; Sat, 07 Mar 2020 22:20:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87a75azxu2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 22 Feb 2020 12:05:25 +0100") 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-mx.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 39708@debbugs.gnu.org Hello Ludovic! Ludovic Court=C3=A8s writes: > Hi, > > Maxim Cournoyer skribis: > >> The rpc.mountd service, one of the required services for >> nfs-service-type, respawns the process quickly until disabled. > > Does /var/log/messages contain hints? herd restart nfs Service nfs has been stopped. Service rpc.mountd is currently disabled. Service nfs depends on rpc.mountd. Service nfs could not be started. root@hurd ~# herd stop rpc.mountd root@hurd ~# herd enable rpc.mountd Enabled service rpc.mountd. root@hurd ~# herd status rpc.mountd Status of rpc.mountd: It is stopped. It is enabled. Provides (rpc.mountd). Requires (rpc.statd). Conflicts with (). Will be respawned. Last respawned on Sat Mar 07 21:56:43-0500 2020. root@hurd ~# herd restart nfs Service nfs is not running. Service rpc.mountd has been started. Service nfs has been started. And then, in /var/log/messages: Mar 7 21:56:4--8<---------------cut here---------------start------------->= 8--- Mar 7 22:06:45 localhost shepherd[1]: Service nfs has been stopped.=20 Mar 7 22:06:45 localhost shepherd[1]: Service rpc.mountd is currently disa= bled.=20 Mar 7 22:06:45 localhost shepherd[1]: Service nfs depends on rpc.mountd.=20 Mar 7 22:06:45 localhost shepherd[1]: Service nfs could not be started.=20 Mar 7 22:07:05 localhost shepherd[1]: Enabled service rpc.mountd.=20 Mar 7 22:07:15 localhost shepherd[1]: Service nfs is not running.=20 Mar 7 22:07:15 localhost shepherd[1]: Service rpc.mountd has been started.= =20 Mar 7 22:07:15 localhost shepherd[1]: Service nfs has been started.=20 Mar 7 22:07:15 localhost rpc.mountd[25270]: Version 2.4.2 starting Mar 7 22:07:15 localhost shepherd[1]: Respawning rpc.mountd.=20 Mar 7 22:07:15 localhost shepherd[1]: Service rpc.mountd has been started.= =20 Mar 7 22:07:15 localhost rpc.mountd[25272]: Version 2.4.2 starting Mar 7 22:07:15 localhost shepherd[1]: Respawning rpc.mountd.=20 Mar 7 22:07:15 localhost shepherd[1]: Service rpc.mountd has been started.= =20 Mar 7 22:07:15 localhost rpc.mountd[25274]: Version 2.4.2 starting Mar 7 22:07:15 localhost shepherd[1]: Respawning rpc.mountd.=20 Mar 7 22:07:15 localhost shepherd[1]: Service rpc.mountd has been started.= =20 Mar 7 22:07:15 localhost rpc.mountd[25276]: Version 2.4.2 starting Mar 7 22:07:15 localhost shepherd[1]: Respawning rpc.mountd.=20 Mar 7 22:07:15 localhost shepherd[1]: Service rpc.mountd has been started.= =20 Mar 7 22:07:15 localhost rpc.mountd[25278]: Version 2.4.2 starting Mar 7 22:07:15 localhost shepherd[1]: Respawning rpc.mountd.=20 Mar 7 22:07:15 localhost shepherd[1]: Service rpc.mountd has been started.= =20 Mar 7 22:07:15 localhost rpc.mountd[25280]: Version 2.4.2 starting Mar 7 22:07:15 localhost shepherd[1]: Service rpc.mountd has been disabled= .=20 Mar 7 22:07:15 localhost shepherd[1]: (Respawning too fast.) --8<---------------cut here---------------end--------------->8--- > Is rpc.statd running? herd status rpc.statd Status of rpc.statd: It is started. Running value is 348. It is enabled. Provides (rpc.statd). Requires (rpcbind-daemon). Conflicts with (). Will be respawned. root@hurd ~# pidof rpc.statd 348 So, yes :-) > Could it be that all these services need to depend on =E2=80=98loopback= =E2=80=99? I don't think so, because attempting to restart those services in a state where the network is live and a loopback interface exists (127.0.0.1 pings) doesn't change the outcome. Or am I misunderstanding something? An interesting fact is that every time 'herd restart rpc.mountd' is run, the number of running processes of rpc.mountd goes up: --8<---------------cut here---------------start------------->8--- herd enable rpc.mountd && herd start rpc.mountd && pidof rpc.mountd | wc -w Enabled service rpc.mountd. Service rpc.mountd has been started. 6 root@hurd ~# herd enable rpc.mountd && herd start rpc.mountd && pidof rpc.m= ountd | wc -w Enabled service rpc.mountd. Service rpc.mountd has been started. 12 root@hurd ~# herd enable rpc.mountd && herd start rpc.mountd && pidof rpc.m= ountd | wc -w Enabled service rpc.mountd. Service rpc.mountd has been started. 13 root@hurd ~# herd enable rpc.mountd && herd start rpc.mountd && pidof rpc.m= ountd | wc -w Enabled service rpc.mountd. Service rpc.mountd has been started. 19 root@hurd ~# herd enable rpc.mountd && herd start rpc.mountd && pidof rpc.m= ountd | wc -w Enabled service rpc.mountd. Service rpc.mountd has been started. 20 root@hurd ~# herd enable rpc.mountd && herd start rpc.mountd && pidof rpc.m= ountd | wc -w Enabled service rpc.mountd. Service rpc.mountd has been started. 26 --8<---------------cut here---------------end--------------->8--- So, to me it seems to be a problem with Shepherd: it erroneously thinks the process has died and restart it, while in reality it is still running fine. Running the rpc.mountd command manually doesn't exhibit any issue, as I mentioned in my original report. Thanks for the help! Maxim