Your message dated Sat, 14 Sep 2024 09:51:27 +0200 (CEST) with message-id <20240914075127.135c0be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #814918, regarding nfs-common: krb5 mounts not working at boot time 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.) -- 814918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: nfs-common Version: 1:1.2.8-9 Severity: important Out of the box on a fresh stretch install nfs mounts fail because portmap is unavailable. After adding fix from 806336 (DefaultDependencies=no) that problem is fixed and mounts can be performed manually, but the mounts still fail at boot time because the system doesn't start rpc.gssd until after attemping the nfs mounts. There should be some ordering to ensure that the mounts aren't attempted until after the nfs-common startup is complete. Mike Stone -- 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 39314 status 100024 1 tcp 59339 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- nfsserver.mathom.us:/home /home nfs sec=krb5 0 0 nfsserver.mathom.us:/scratch /scratch nfs sec=krb5 0 0 -- /proc/mounts -- nfsserver.mathom.us:/home /home nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=[ip],local_lock=none,addr=[ip] 0 0 nfsserver.mathom.us:/scratch /scratch nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=[ip],local_lock=none,addr=[ip] 0 0 -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59.2 ii libc6 2.21-7 ii libcap2 1:2.24-12 ii libcomerr2 1.42.13-1 ii libdevmapper1.02.1 2:1.02.115-2 ii libevent-2.0-5 2.0.21-stable-2+b1 ii libgssapi-krb5-2 1.13.2+dfsg-4 ii libk5crypto3 1.13.2+dfsg-4 ii libkeyutils1 1.5.9-8 ii libkrb5-3 1.13.2+dfsg-4 ii libmount1 2.27.1-3 ii libnfsidmap2 0.25-5 ii libtirpc1 0.2.5-1 ii libwrap0 7.6.q-25 ii lsb-base 9.20160110 ii rpcbind 0.2.3-0.2 ii ucf 3.0033 Versions of packages nfs-common recommends: ii python 2.7.11-1 Versions of packages nfs-common suggests: pn open-iscsi <none> pn watchdog <none> -- Configuration Files: /etc/default/nfs-common changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---Hi [This reply and bug closer is sent for doing BTS maintenance for src:nfs-utils bugs] This bug was reported against a very old nfs-utils version without much followups/triaging itself. If you can reproduce it with the current version in unstable/testing or stable at least, please reopen the bug, https://www.debian.org/Bugs/server-control for details. Regards, Salvatore
--- End Message ---
