Bug#850464: nfs-blkmap.service fails to start at boot
Control: tags -1 + pending Hello. On Mon, Mar 13, 2017 at 02:33:27PM -0700, Nye Liu wrote: > On Sat, Mar 11, 2017 at 08:15:02PM +0100, Andreas Henriksson wrote: > > Could you please test editing nfs-blkmap.service on your system > > and replace: > > PIDFile=/var/run/blkmapd.pid > > with: > > PIDFile=/run/blkmapd.pid > > .. and report back if that solves the issue or not? > > Yes, this fixes the issue. Thanks for the confirmation! I've pushed this fix to the (fubared) git packaging repo and uploaded a NMU to delayed/5. > > BTW, I am not sure who else to ask about this, but > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539201 > and > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738063 > > are somewhat related. Not really. These are issues about /etc/default integration which is really a question that needs to be decided by the maintainer(s). Use 'systemctl edit ' if you want to override the default settings under systemd. > > There are a lot of problems with the systemd migration, and > none of them are getting fixed. [...] You should help out! Apparently there's a lack of maintainers for nfs-utils in debian. Your golden opportunity to give something back for all the great gifts you've received from everyone else contributing to Debian. (Personally I'm not interested as I don't use nfs.) Hope the NMU helps. Regards, Andreas Henriksson
Bug#850464: nfs-blkmap.service fails to start at boot
On Sat, Mar 11, 2017 at 08:15:02PM +0100, Andreas Henriksson wrote: > Could you please test editing nfs-blkmap.service on your system > and replace: > PIDFile=/var/run/blkmapd.pid > with: > PIDFile=/run/blkmapd.pid > .. and report back if that solves the issue or not? Yes, this fixes the issue. BTW, I am not sure who else to ask about this, but https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539201 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738063 are somewhat related. There are a lot of problems with the systemd migration, and none of them are getting fixed. They're mostly related to nfs-common being disabled in systemd, and partly due to stuff missing in /etc/init.d/nfs-kernel-server If a user is expecting any of the following (due to their old configuration in /etc/default): enable nfs v2 disable nfs v3 disable nfs v4 statd idmapd blkmap etc. their system will be utterly broken, since each has to be manually enabled via systemctl enable, and/or both /etc/default/nfs-kernel-server and /etc/init.d/nfs-kernel-server have to be patched. In short, nfs-kernel-server is broken with systemd and nobody seems to be addressing any of the issues. I think there needs to a be a single unifying bug that summarizes all of the current systemd/nfs issues so they can be addressed in a coherent, multilateral manner. Thanks for your time and attention, hopefully someone can take over the mess... MRV Communications is a global supplier of packet and optical solutions that power the world’s largest networks. Our products combine innovative hardware with intelligent software to make networks smarter, faster and more efficient.
Bug#850464: nfs-blkmap.service fails to start at boot
Hello Nye Liu, Thanks for your feedback on this issue! On Wed, Feb 01, 2017 at 08:41:46PM -0800, Nye Liu wrote: > Same thing for me: > > -- Logs begin at Wed 2017-02-01 20:18:34 PST, end at Wed 2017-02-01 20:36:38 > PST. -- > Feb 01 20:18:35 jane systemd[1]: Starting pNFS block layout mapping daemon... > Feb 01 20:18:35 jane systemd[1]: nfs-blkmap.service: PID file > /var/run/blkmapd.pid not readable (yet?) after start: No such file or > directory > Feb 01 20:18:35 jane blkmapd[243]: open pipe file > /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory > --- note 2 minute delay here --- > Feb 01 20:20:05 jane systemd[1]: nfs-blkmap.service: Start operation timed > out. Terminating. > Feb 01 20:20:05 jane systemd[1]: Failed to start pNFS block layout mapping > daemon. > Feb 01 20:20:05 jane systemd[1]: nfs-blkmap.service: Unit entered failed > state. > Feb 01 20:20:05 jane systemd[1]: nfs-blkmap.service: Failed with result > 'timeout'. > > You can seem to start later by hand though: > > Feb 01 20:32:14 jane systemd[1]: Starting pNFS block layout mapping daemon... > Feb 01 20:32:14 jane blkmapd[6556]: open pipe file > /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory > Feb 01 20:32:14 jane systemd[1]: Started pNFS block layout mapping daemon. > > note that it has the same error. [...] Very useful information. Could you please test editing nfs-blkmap.service on your system and replace: PIDFile=/var/run/blkmapd.pid with: PIDFile=/run/blkmapd.pid .. and report back if that solves the issue or not? (It looks to me like debian/patches/21-no-more-var-run.patch needs to be updated to also cover systemd/nfs-blkmap.service ) Regards, Andreas Henriksson
Bug#850464: nfs-blkmap.service fails to start at boot
Same thing for me: -- Logs begin at Wed 2017-02-01 20:18:34 PST, end at Wed 2017-02-01 20:36:38 PST. -- Feb 01 20:18:35 jane systemd[1]: Starting pNFS block layout mapping daemon... Feb 01 20:18:35 jane systemd[1]: nfs-blkmap.service: PID file /var/run/blkmapd.pid not readable (yet?) after start: No such file or directory Feb 01 20:18:35 jane blkmapd[243]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory --- note 2 minute delay here --- Feb 01 20:20:05 jane systemd[1]: nfs-blkmap.service: Start operation timed out. Terminating. Feb 01 20:20:05 jane systemd[1]: Failed to start pNFS block layout mapping daemon. Feb 01 20:20:05 jane systemd[1]: nfs-blkmap.service: Unit entered failed state. Feb 01 20:20:05 jane systemd[1]: nfs-blkmap.service: Failed with result 'timeout'. You can seem to start later by hand though: Feb 01 20:32:14 jane systemd[1]: Starting pNFS block layout mapping daemon... Feb 01 20:32:14 jane blkmapd[6556]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory Feb 01 20:32:14 jane systemd[1]: Started pNFS block layout mapping daemon. note that it has the same error. Nevertheless: $ sudo systemctl status nfs-blkmap ● nfs-blkmap.service - pNFS block layout mapping daemon Loaded: loaded (/lib/systemd/system/nfs-blkmap.service; disabled; vendor preset: enabled) Active: active (running) since Wed 2017-02-01 20:32:14 PST; 7min ago Process: 6555 ExecStart=/usr/sbin/blkmapd $BLKMAPDARGS (code=exited, status=0/SUCCESS) Main PID: 6556 (blkmapd) Tasks: 1 (limit: 4915) CGroup: /system.slice/nfs-blkmap.service └─6556 /usr/sbin/blkmapd Feb 01 20:32:14 jane systemd[1]: Starting pNFS block layout mapping daemon... Feb 01 20:32:14 jane blkmapd[6556]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory Feb 01 20:32:14 jane systemd[1]: Started pNFS block layout mapping daemon. MRV Communications is a global supplier of packet and optical solutions that power the world’s largest networks. Our products combine innovative hardware with intelligent software to make networks smarter, faster and more efficient.
Bug#850464: nfs-blkmap.service fails to start at boot
package: nfs-kernel-server version: 1:1.3.4-2 severity: serious The blkmapd process looks for /run/rpc_pipefs/nfs/blocklayout It fails to find it and the system boot doesn't complete, it asks for an emergency login on the text console. I don't see anything under /run/rpc_pipefs/nfs Other NFS services appear to be running fine. The ArchLinux NFS wiki recommends masking the blkmapd service: systemctl mask nfs-blkmap.service https://wiki.archlinux.org/index.php/NFS Perhaps blkmapd could be split into a separate package so it is only installed for people who want it. blkmapd[278]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory blkmapd[278]: exit on signal(15) systemd[1]: Failed to start pNFS block layout mapping daemon. -- Subject: Unit nfs-blkmap.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nfs-blkmap.service has failed. -- -- The result is failed.
