search for: handle_nullreq

I ran yum update on a CentOS 6.0 machine against the CR repository and noticed that the nfs-utils-lib update broke my rcp.idmap settings: rpc.idmapd: libnfsidmap: processing 'Method' list rpc.idmapd: libnfsidmap: Unable to get init function: /usr/lib64/libnfsidmap/umich_ldap.so: undefined symbol: libnfsidmap_plugin_init rpc.idmapd: libnfsidmap: requested translation method,

...m guessing that this happens because the nfsclient1 still has, and uses, the /tmp/krb5cc_machine_EXAMPLE.COM cache file? This file would have the ?old? Kerberos credentials?... On the NFS server in /var/log/messages this error message is displayed: "rpc.svcgssd[5983]: ERROR: GSS-API: error in handle_nullreq: gss_accept_sec_context(): GSS_S_FAILURE (Unspecified GSS failure. Minor code may provide more information) - Wrong principal in request" On the NFS client in /var/log/messages these messages are displayed: "creating context with server nfs at nfs1.example.com" "WARNING: Fail...

...pens because the nfsclient1 still has, and uses, > the /tmp/krb5cc_machine_EXAMPLE.COM cache file? > This file would have the ?old? Kerberos credentials?... > > On the NFS server in /var/log/messages this error message is displayed: > "rpc.svcgssd[5983]: ERROR: GSS-API: error in handle_nullreq: > gss_accept_sec_context(): GSS_S_FAILURE (Unspecified GSS failure. Minor > code may provide more information) - Wrong principal in request" > > On the NFS client in /var/log/messages these messages are displayed: > "creating context with server nfs at nfs1.example.com&qu...