On Mon, 7 Mar 2016, Mark Valites wrote: > On 03/07/2016 11:00 AM, Benjamin Coddington wrote: > > > Hey Mark, could it be this one? > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1313090 > > > > Ben > > > > Doesn't look like it: > > $ sudo restorecon -v /etc/krb5.keytab > <no output> > $ ls -laZ /etc/krb5.keytab > -rw-------. root root unconfined_u:object_r:krb5_keytab_t:s0 /etc/krb5.keytab > > I'd only had selinux in permissive mode, so I tried disabling it as well, but > that too unfortunately made no difference. That bug was only tickled in my case if the normal host principals were not found in the keytab. In that specific case, selinux prohibited access to the keytab, causing the host keys to be unable to be looked up, and the bug was hit. Best bet would be to attache a debugger to rpc.gssd and get a stack trace of it when it crashes. That will give us something to work from. You can do that with gdb -p <pid of gssd>. Something like `gdb -p $(pidof rpc.gssd)` will work -- then type "continue" to let the process continue to run. When it fails you can enter "bt" to emit a back trace. That information would be very helpful. Ben -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
