Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #57111 > unrolled thread
| Started by | Rafael David Tinoco <rafael.tinoco@canonical.com> |
|---|---|
| First post | 2017-02-27 22:30 +0100 |
| Last post | 2018-01-04 08:30 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
Bug#856328: Fix nfs-mountd dependency on rpcbind Rafael David Tinoco <rafael.tinoco@canonical.com> - 2017-02-27 22:30 +0100
Bug#856328: Fixed upstream in release 2.2.1 Jochen Hein <jochen@jochen.org> - 2018-01-04 08:30 +0100
| From | Rafael David Tinoco <rafael.tinoco@canonical.com> |
|---|---|
| Date | 2017-02-27 22:30 +0100 |
| Subject | Bug#856328: Fix nfs-mountd dependency on rpcbind |
| Message-ID | <tfB1M-2XP-11@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Jochen Hein <jochen@jochen.org> |
|---|---|
| Date | 2018-01-04 08:30 +0100 |
| Subject | Bug#856328: Fixed upstream in release 2.2.1 |
| Message-ID | <v488p-2fX-1@gated-at.bofh.it> |
| In reply to | #57111 |
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.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web