Re: nfs4 with sec=krb5, mount times out

[Julius <commercials@gmx.net>]

On Mon, 2009-01-26 at 14:39 -0500, Kevin Coffman wrote:
> On Mon, Jan 26, 2009 at 2:22 PM, Julius <commercials@gmx.net> wrote:
> > On Mon, 2009-01-26 at 13:59 -0500, Kevin Coffman wrote:
> >> On Mon, Jan 26, 2009 at 1:24 PM, Julius <commercials@gmx.net> wrote:
> >> > Hi,
> >> >
> >> >
> >> > i can mount my nfsv4 share without kerberos security without
> >> > problems.../etc/fstab:
> >> >
> >> > night_crawler.localdomain.de:/music /home/metalfan/nfs4-mount   nfs4    user
> >> > 0       0
> >> >
> >> >
> >> > but adding "sec=krb5" to the options list results in:
> >> >
> >> >
> >> > mount -v nfs4-mount/
> >> > mount.nfs4: timeout set for Mon Jan 26 15:44:05 2009
> >> > mount.nfs4: text-based options:
> >> > 'sec=krb5,clientaddr=141.x.x.x,addr=141.x.x.x
> >> > mount.nfs4: mount(2): Connection timed out
> >> >
> >> >
> >> > I read somewhere on the mailing list that only des-cbc-crc is supported
> >> > for nfs4, its the only keytype for my user metalfan.
> >> > "kinit metalfan" was run before attempting to mount.
> >> > i can use gssapi to connect to night_crawlers sshd with my local user,
> >> > which also does the nfs4 mount.
> >> >
> >> > krb5-kdc.log and krb5-default.log do not show any connections.
> >> > Where do you start troubleshooting?
> >>
> >> First step would be to verify that rpc.gssd is running on your client
> >> machine, and rpc.svcgssd is running on your server machine.
> >> You need to generate a keytab for your server (with only a des-cbc-crc
> >> key).  (nfs/<f.q.h.n>@<REALM>)
> >> You likely need to generate a keytab for your client as well.
> >>
> >> If all those are done, send output of rpc.gssd and rpc.svcgssd
> >> (running with option -vvv).
> >>
> >> I would point you at our FAQ page, but the web server is sadly still
> >> down at the moment.
> >>
> >> K.C.
> >
> > the nfs/... entry was missing, so i added:
> > nfs/night_crawler.localdomain.de-jgXV7fHVA4Rbjp6DLoyPiQ@public.gmane.org
> > with the des-cbc-crc as only enc type.
> >
> > but still rpc.svcgssd fails with:
> > ERROR: GSS-API: error in gss_acquire_cred():  No credentials were
> > supplied, or the credentials were unavailable or inaccessible. - unknown
> > mech-code 0 for mech unknown
> > Unable to obtain credentials for 'nfs'
> > unable to obtain root (machine) credentials
> > do you have a keytab entry for nfs/<your.host>@<YOUR.REALM>
> > in /etc/krb5.keytab?
> 
> I think there should be more messages with "-vvv" enabled?
> Do you have /etc/gssapi_mech.conf configured for kerberos?
> 
> What distribution is this?
> 
> K.C.


Distribution: archlinux, nfs4-utils is currently unmaintained.

/etc/gssapi.conf
/usr/lib/libgssapi.so            mechglue_internal_krb5_init


oops, typo.
I added....-jgXV7fHVA4Rbjp6DLoyPiQ@public.gmane.org

Now rpc.svcgssd starts and prints: 
rpc.svcgssd -vvvf
entering pool

rpc.gssd -vvvf
beginning poll


mount -v nfs4-mount/
mount.nfs4: timeout set for Mon Jan 26 21:55:13 2009
mount.nfs4: text-based options:
'sec=krb5,clientaddr=141.x.x.x,addr=141.x.x.x'
mount.nfs4: mount(2): Connection timed out


Hm, not quite yet.


Julius