Your message dated Sat, 14 Sep 2024 09:52:32 +0200 (CEST) with message-id <20240914075232.21b16be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #711421, regarding nfs-common: NFS4 mount with kerberos hangs forewer 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.) -- 711421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: nfs-common Version: 1:1.2.8-4 Severity: normal Dear Maintainer, After last update that should solve 705507 the rpc.gssd no longer crashes, but mounting NFS share hangs forewer with syslog messages: NFS: Registering the id_resolver key type Key type id_resolver registered Key type id_legacy registered rpc.gssd[2059]: ERROR: GSS-API: error in gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been established) - Unknown error rpc.gssd[2059]: WARN: failed to free lucid sec context followed by: nfs: server servername not responding, timed out I use NFS4 with sec=krb5. Everything worked fine until Sid unfreeze, after which I was hit by 705507. -- 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 32765 status 100024 1 tcp 32765 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS="--port 32765 --outgoing-port 32766" NEED_IDMAPD=yes NEED_GSSD=yes -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (650, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-41 ii libc6 2.17-5 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.5-1.1 ii libdevmapper1.02.1 2:1.02.77-1 ii libevent-2.0-5 2.0.21-stable-1 ii libgssglue1 0.4-2 ii libk5crypto3 1.10.1+dfsg-5 ii libkeyutils1 1.5.5-7 ii libkrb5-3 1.10.1+dfsg-5 ii libmount1 2.20.1-5.4 ii libnfsidmap2 0.25-5 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-24 ii lsb-base 4.1+Debian12 ii rpcbind 0.2.0-8 ii ucf 3.0027 Versions of packages nfs-common recommends: ii python 2.7.3-5 Versions of packages nfs-common suggests: pn open-iscsi <none> pn watchdog <none> -- 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 ---
