[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#850464: marked as done (nfs-blkmap.service fails to start at boot)

Your message dated Sat, 25 Mar 2017 16:03:42 +0000
with message-id <E1croAI-000Ikn-DT@fasolo.debian.org>
and subject line Bug#850464: fixed in nfs-utils 1:1.3.4-2.1
has caused the Debian Bug report #850464,
regarding nfs-blkmap.service fails to start at boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
850464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850464
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

--- End Message ---
--- Begin Message --- 
Source: nfs-utils
Source-Version: 1:1.3.4-2.1

We believe that the bug you reported is fixed in the latest version of
nfs-utils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 850464@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Henriksson <andreas@fatal.se> (supplier of updated nfs-utils package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 20 Mar 2017 16:07:55 +0100
Source: nfs-utils
Binary: nfs-kernel-server nfs-common
Architecture: source
Version: 1:1.3.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian kernel team <debian-kernel@lists.debian.org>
Changed-By: Andreas Henriksson <andreas@fatal.se>
Description:
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - support for NFS kernel server
Closes: 850464
Changes:
 nfs-utils (1:1.3.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix patch to also change pidfile path in service file (Closes: #850464)
Checksums-Sha1:
 15e8dff425eb3bc009520116870e5572476d17e1 2360 nfs-utils_1.3.4-2.1.dsc
 3bcbe2f83f18577befbc6ca40f40b4a9bf0ee3e3 40882 nfs-utils_1.3.4-2.1.debian.tar.bz2
Checksums-Sha256:
 d533fb1a6bda9986b0f7e323af9493dc912131d655885d5c94388eb211193d4e 2360 nfs-utils_1.3.4-2.1.dsc
 63b0fdead8e46cd4e3576ae0e557a3ba27f3d41367b61beead9659c3cdeca11f 40882 nfs-utils_1.3.4-2.1.debian.tar.bz2
Files:
 0d6d899a75bdf8155c02ecc3ca17d5f9 2360 net standard nfs-utils_1.3.4-2.1.dsc
 e17b1f3b74324ce888bd4b98fd053954 40882 net standard nfs-utils_1.3.4-2.1.debian.tar.bz2

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAljP9WQACgkQC8R9xk0T
Uwbb6RAAo6xnIrpdSWhV53oablwfvvjVjyNPDGTqKtZFvoSVb+0Gamftmad0kok/
+EA2Dl1umkLYsmYDPglT300EPp/Pc/VBJF4iDkY+rayZgWCPOQlwpBUUJcxMwz6K
DmIauq7b/444jrejUv2GHaCPexzscTT3h5PUl780dBCbUbUp4cGoYAVLhk2GwxlP
HU2wyM9aes6nEo6gH/pG7Jhg3T+umZ6jMWFXv6SjLrz/uejG9BB9PJuJPtGKuXt6
v3LpHIZ/eAJwa1EfTfKIfyIpMd9ZcAWeXx6EeMLO8aLsCSlpoKSG5yVVHlushP1D
GzkQ8IVJRJ1M3BkJylrmDuyfuG9Aph8ZIXZwWVY1U6I8GoaBP3qJiWBMd3GubK76
xECw0PDCmNTjIkrjwyuc5vJXlrPNvLdSC2cxUhYXEL4MPNgJFokq/PzQ2CXqZEmc
FGXm1Ku90OgHnjPmcYFxtaFgE1r4cwRTdS09K7qFEmxcPsjD1dxm1Jr2MJsdPXYR
OBPAA3Y/y0BaIS68k4JKqtK7v76tGM+4ly1yPaJSa4fsenTqbR5Di21McmpM1Tmb
Wcul5BfODMYAYa5AN1uKcsEv3WvZbHqF/0MllISsBL547e9DPiWKAbW18PT229FB
joWzj7XEABgSwX4UFo/i9YddLzJ6u4THIFgPfH/WQOKKvPd47bE=
=Jvcv
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: