Trying to mount NFS4 export results in libgssglue segfault

English Network/Internet
1

While trying to mount an exported directory from Debian Wheezy over nfs4 with sec=krb5; libgssglue is segfaulting on me.

The line from /var/log/messages

2014-02-04T6:15:33.221657+01:00 myhostname kernel:  2338.344221] rpc.gssd[3251]: segfault at 1 ip 00007f031b1a9be5 sp00007fff0815f810 error 4 in libgssglue.so.1.0.0
[7f031b1a6000+9000]

Does anyone have nfs4 with krb5 security working on openSUSE 13.1 as a client?

2

Please, saying “While trying to mount…” is a nice introduction. But you should also show what you do. E.g. the mount command, the fstab entry if there is one involved, etc How can anybody assess your problem when there is no info about what you do except from a lone log entry?

3

This is the mount command I use, but actually I don’t really see why it would matter. An erronous mount command should never ever lead to a segfault imho

sudo mount -t nfs4 -o sec=krb5 myserver.mydomain.net:/shared /mnt

This mount command works fine from a client running Debian Wheezy so I don’t think there is an issue on the servers side. I can get kerberos tickets using kinit without a problem and my /etc/krb5.keytab has the same nfs/nfsclienthostname.mydomain.net@MYDOMAIN.NET entries as the Debian host.

4

And to be complete

/etc/sysconfig/nfs


USE_KERNEL_NFSD_NUMBER="4"
MOUNTD_PORT=""
NFS_SECURITY_GSS="yes"
NFS3_SERVER_SUPPORT="yes"
NFS4_SUPPORT="yes"
SM_NOTIFY_OPTIONS=""
NFS_START_SERVICES="yes"
STATD_OPTIONS=""
NFSV4LEASETIME=""
RPC_PIPEFS_DIR=""
SVCGSSD_OPTIONS=""
NFSD_OPTIONS=""
GSSD_OPTIONS="-vvv"
NFS4_SERVER_MINOR_VERSION="0"
MOUNTD_OPTIONS=""
NFS_GSSD_AVOID_DNS="yes"

/etc/krb5.conf


[libdefaults]
        default_realm = MYDOMAIN.NET

[realms]
MYDOMAIN.NET = {
        kdc = auth0.mydomain.net
        admin_server = auth0.mydomain.net
}

[domain_realm]
        .mydomain.net = MYDOMAIN.NET

[login]
        krb4_convert = true
        krb4_get_tickets = false

[logging]
        default = SYSLOG:NOTICE:DAEMON

/etc/idmapd.conf


[General]

Verbosity = 5
Pipefs-Directory = /var/lib/nfs/rpc_pipefs
Domain = mydomain.net

[Mapping]

Nobody-User = nobody
Nobody-Group = nogroup

ktutil


ktutil:  rkt /etc/krb5.keytab
ktutil:  list
slot KVNO Principal
---- ---- ---------------------------------------------------------------------
   1   12    nfs/nfsclienthostname.mydomain.net@MYDOMAIN.NET
   2   12    nfs/nfsclienthostname.mydomain.net@MYDOMAIN.NET
   3   12    nfs/nfsclienthostname.mydomain.net@MYDOMAIN.NET
   4   12    nfs/nfsclienthostname.mydomain.net@MYDOMAIN.NET
ktutil:
5

Did you compare the Debian nfs config file to the openSUSE one?
How about the firewall?
How did you setup the NFS client? Through Yast or by manual file editting?
Mind, I still use NFS3, not much experience with NFS4.

6

No, nothing should segfault ever. But when you throw such a case on the desk of your fellow openSUSE users with the words: “Hey, look a segfault”, you won’t get much help I am afraid.

Thus either you try to communicate with other people here by providing information and getting suggestions, or you go straight to openSUSE:Submitting bug reports - openSUSE Wiki
to file a bug report.

That said, I hope the information you provided now, will trigger people to join this thread.

7

Yep, I compared /etc/sysconfig/nfs with Debian’s /etc/default/nfs-common. I used the same values where possible.
A firewall is not involved
Created it by manual editing the config file first, later on by Yast.