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

Bug#856328: marked as done (Fix nfs-mountd dependency on rpcbind)

Your message dated Thu, 9 Sep 2021 00:25:54 +1000
with message-id <YTjH8h/TpebPkPMq@master.debian.org>
and subject line Re: Fixed upstream in release 2.2.1
has caused the Debian Bug report #856328,
regarding Fix nfs-mountd dependency on rpcbind
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.)


-- 
856328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856328
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: nfs-utils
Version: 1:1.3.4-2
Severity: important
Tags: patch, fixed-upstream, sid,

Hello maintainer,

I'm fixing this behavior in Ubuntu and I think fixing it in Debian is needed:

https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799

You can follow the upstream discussion for this fix:

https://www.spinics.net/lists/linux-nfs/msg62022.html

"""
Following commit 91da135f - it replaced "rpcbind.target" by "rpcbind.socket" in
some unit files - "rpcbind.socket" should also be added to "nfs-mountd.service"
as a dependency to avoid race conditions.

Usually "rpcbind.socket" is either started as a "sockets.target" dependency, or
as a dependency for "nfs-server.service", when unit files include it in
"BindsTo" or "After". Unfortunately there is a possilibility to have
"nfs-mountd.service" started when the rpcbind socket is not yet created:

systemd[1]: Starting NFS Mount Daemon...
systemd[1]: nfs-mountd.service: Control process exited, code=exited status=1
systemd[1]: Failed to start NFS Mount Daemon.
systemd[1]: nfs-mountd.service: Unit entered failed state.
systemd[1]: nfs-mountd.service: Failed with result 'exit-code'.

Nowadays "nfs-mountd.service" uses "BindTo" directive to "nfs-server.service".
That, per se, doesn't guarantee ordering for NFS server to start rpcbind and for
nfs-mountd to depend on it.

https://bugs.launchpad.net/bugs/1590799

Signed-off-by: Rafael David Tinoco <rafael.tinoco@xxxxxxxxxxxxx>
"""

These comments show the problem when nfs-kernel-server starts before
rpcbind.service is brought online (by rpcbind.socket):

https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/comments/24

Explanation:

https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/comments/25
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/comments/30

--- End Message ---
--- Begin Message --- 
On Thu, 2018-01-04 08:14:05 +0100, Jochen Hein wrote:
> 
> This seems to be fixed upstream:
> http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commit;h=907426b00bdcd69d9a56ac1870990e8ae8c6fe9f
> 
> -- 
> This space is intentionally left blank.
> 
>

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: