[Bug 1320658] Re: Kerberos NFSv4 mounts from FreeBSD server fails with "mount.nfs4: mount system call failed"

[Longina Przybyszewska]

I hit the same problem on Ubuntu 14.04
 uname -a
Linux yoda 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

handling gssd upcall (/run/rpc_pipefs/nfs/clnt12)
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 '
handling krb5 upcall (/run/rpc_pipefs/nfs/clnt12)
process_krb5_upcall: service is '<null>'
Full hostname for 'eta.nat.c.sdu.dk' is 'eta.nat.c.sdu.dk'
Full hostname for 'yoda.nat.c.sdu.dk' is 'yoda.nat.c.sdu.dk'
Success getting keytab entry for 'YODA$@'
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_NAT.C.SDU.DK' are good until 1404348760
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_NAT.C.SDU.DK' are good until 1404348760
using FILE:/tmp/krb5ccmachine_NAT.C.SDU.DK as credentials cache for machine creds
using environment variable to select krb5 ccache FILE:/tmp/krb5ccmachine_NAT.C.SDU.DK
creating context using fsuid 0 (save_uid 0)
creating tcp client for server eta.nat.c.sdu.dk
DEBUG: port already set to 2049
creating context with server nfs at eta.nat.c.sdu.dk
DEBUG: serialize_krb5_ctx: lucid version!
prepare_krb5_rfc4121_buffer: protocol 1
prepare_krb5_rfc4121_buffer: serializing key with enctype 18 and size 32
ERROR: GSS-API: error in gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been established) - Unknown error
WARN: failed to free lucid sec context
doing downcall lifetime_rec 36000
destroying client /run/rpc_pipefs/nfs/clnt13
Closing 'gssd' pipe for /run/rpc_pipefs/nfs/clnt12
destroying client /run/rpc_pipefs/nfs/clnt12

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1320658

Title:
  Kerberos NFSv4 mounts from FreeBSD server fails with "mount.nfs4:
  mount system call failed"

Status in “nfs-utils” package in Ubuntu:
  Confirmed

Bug description:
  This problem started to appear after upgrading to 13.10. After another
  upgrade to 14.4, the problem persists. I also tried a fresh
  installation of 14.4, with the same result. Anoter client, still on an
  older Ubuntu release can still successfully mount this partition, and
  OSX also has no problems with it.

  After the upgrade, attempting to mount an NFS partition using NFSv4,
  and the sec=krb5p option consistently yields the following message:

  mount.nfs4: mount system call failed

  The file /var/log/syslog shows the following:

  May 18 23:35:50 tiger rpc.gssd[31127]: ERROR: GSS-API: error in gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been established) - Unknown error
  May 18 23:35:50 tiger rpc.gssd[31127]: WARN: failed to free lucid sec context
  May 18 23:35:50 tiger kernel: [438617.037214] NFS: nfs4_discover_server_trunking unhandled error -121. Exiting with error EIO

  I found the following email thread on the NFS developers list that could possibly be related:
  http://www.spinics.net/lists/linux-nfs/msg37604.html

  The thread has 15 or so messages in it, and in the end they solve it
  with a small fix. Of course, I can't be sure that it's actually the
  same error, but there is lots of evidence in the thread that points to
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nfs-common 1:1.2.8-6ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 18 23:43:13 2014
  InstallationDate: Installed on 2010-07-23 (1394 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: nfs-utils
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1320658/+subscriptions