** Description changed: + [Test Case] + See comment #5. + After upgrading from precise to trusty, I started seeing the following error messages in the logs whenever there was Kerberized NFS activity: - Jun 17 08:02:43 hostname rpc.gssd[1021]: ERROR: GSS-API: error in gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been established) - Unknown error - Jun 17 08:02:43 hostname rpc.gssd[1021]: WARN: failed to free lucid sec context + Jun 17 08:02:43 hostname rpc.gssd[1021]: ERROR: GSS-API: error in + gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT (No context has been + established) - Unknown errorJun 17 08:02:43 hostname rpc.gssd[1021]: + WARN: failed to free lucid sec context I've determined this to be a regression introduced (into upstream release 1.2.8) by commit 051eb4863cf880f0349a1de44517f9c99a9c5bd4. The bug is still present in upstream release 1.3.0. I've successfully tested the attached, obvious patch.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331201 Title: rpc.gssd: ERROR: GSS-API: error in gss_free_lucid_sec_context(): GSS_S_NO_CONTEXT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1331201/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
