Your message dated Sat, 26 Apr 2025 22:40:19 +0200 with message-id <aa1eswpigeucu...@eldamar.lan> and subject line Re: Bug#1104096: nfsdctl: lockd configuration failure reported after updating to nfs-utils-2.8.3 has caused the Debian Bug report #1104096, regarding nfs-kernel-server: exports file is not parsed or nfsdctl: lockd configuration failure is reported when parsing 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 ow...@bugs.debian.org immediately.) -- 1104096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: nfs-kernel-server Version: 1:2.8.3-1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: patrickjrdunf...@gmail.com -- Package-specific info: -- rpcinfo -- program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 50501 status 100024 1 tcp 51701 status 100005 1 udp 37504 mountd 100005 1 tcp 57573 mountd 100005 2 udp 52838 mountd 100005 2 tcp 49829 mountd 100005 3 udp 55115 mountd 100005 3 tcp 38111 mountd 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100021 1 udp 56162 nlockmgr 100021 3 udp 56162 nlockmgr 100021 4 udp 56162 nlockmgr 100021 1 tcp 41149 nlockmgr 100021 3 tcp 41149 nlockmgr 100021 4 tcp 41149 nlockmgr -- /etc/default/nfs-kernel-server -- RPCNFSDPRIORITY=0 NEED_SVCGSSD="" -- /etc/nfs.conf -- [general] pipefs-directory=/run/rpc_pipefs [nfsrahead] [exports] [exportfs] [gssd] [lockd] [exportd] [mountd] manage-gids=y [nfsdcld] [nfsd] [statd] [sm-notify] [svcgssd] -- /etc/nfs.conf.d/*.conf -- -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.21-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nfs-kernel-server depends on: ii keyutils 1.6.3-6 ii libblkid1 2.41-4 ii libc6 2.41-7 ii libcap2 1:2.75-6 ii libevent-core-2.1-7t64 2.1.12-stable-10+b1 ii libnl-3-200 3.7.0-2 ii libnl-genl-3-200 3.7.0-2 ii libreadline8t64 8.2-6 ii libsqlite3-0 3.46.1-3 ii libtirpc3t64 1.3.6+ds-1 ii libuuid1 2.41-4 ii libwrap0 7.6.q-36 ii libxml2 2.12.7+dfsg+really2.9.14-0.4 ii netbase 6.5 ii nfs-common 1:2.8.3-1 ii ucf 3.0051 Versions of packages nfs-kernel-server recommends: ii python3 3.13.2-2 ii python3-yaml 6.0.2-1+b2 Versions of packages nfs-kernel-server suggests: ii procps 2:4.0.4-8 -- no debconf information
--- End Message ---
--- Begin Message ---Hi So conclusive, as explained by upstream: 1. the nfsdctl error is harmless, and if nfs-utils used with kernel which does not support the netlink control interfaces for knfsd then falls back to start the server with rpc.nfsd and this is indeed the case. 2. the previous starting with nfsdctl autostart was actually a regression now fixed with 2.8.3, since older nfsdctl just ingored the lockd parameters in nfs.conf nd would not have configured it properly so technically a regression from 1:2.6.2-4+deb12u1 in bookworm to the 2.8.2 based version previously, and now fixed in 2.8.3. Closing thus the issue. Regards, Salvatore
--- End Message ---
