From: Phillip <phuang@plasmon.cn>
To: "William A. (Andy) Adamson" <andros@citi.umich.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: can not start NFSv4 with Kerberos 5
Date: Wed, 04 Apr 2007 16:43:40 +0800 [thread overview]
Message-ID: <1175676220.3572.21.camel@milan> (raw)
In-Reply-To: <89c397150704030446id0db9b1h30e20cfba0f5182a@mail.gmail.com>
Update,
In the NFS v4 server, I could start NFS server successful
[root@nfsv4 ~]# service nfs restart
Shutting down RPC svcgssd: [ OK ]
Shutting down NFS mountd: [ OK ]
Shutting down NFS daemon: [ OK ]
Shutting down NFS quotas: [ OK ]
Shutting down NFS services: [ OK ]
Starting RPC svcgssd: [ OK ]
Starting NFS services: [ OK ]
Starting NFS quotas: [ OK ]
Starting NFS daemon: [ OK ]
Starting NFS mountd: [ OK ]
[root@nfsv4 ~]# rpc.gssd -fvvv
Using keytab file '/etc/krb5.keytab'
Processing keytab entry for principal 'nfs/nfsv4@PLASMON.SIT'
We will use this entry (nfs/nfsv4@PLASMON.SIT)
Using (machine) credentials cache:
'FILE:/tmp/krb5cc_machine_PLASMON.SIT'
processing client list
[root@nfsv4 ~]# cat /etc/exports
#
/XFS/NFS4 gss/krb5
(fsid=0,insecure,no_root_squash,no_subtree_check)
It seems everything runs ok, but also in this NFSv4 server, mount
failed:
[root@nfsv4 ~]# mount -t nfs4 -o sec=krb5 192.168.123.63:/ /e
Warning: rpc.gssd appears not to be running.
mount: Broken pipe
I find that the rpc.gssd is running:
[root@nfsv4 ~]# ps -ef | grep rpc.gss
root 5053 4854 0 16:31 pts/2 00:00:00 rpc.gssd -fvvv
root 5065 4909 0 16:34 pts/3 00:00:00 grep rpc.gss
there's the following lines in /var/log/message:
Apr 4 11:11:00 nfsv4 rpc.svcgssd[4742]: WARNING: handle_nullreq: failed
parsing request
Apr 4 11:11:25 nfsv4 rpc.svcgssd[4742]: WARNING: handle_nullreq: failed
parsing request
I've searched for many resolutions, however, none can fix my issue.
Please give me some hints, thanks in advance.
Regards,
Phillip
On Tue, 2007-04-03 at 07:46 -0400, William A. (Andy) Adamson wrote:
>
>
> On 4/3/07, Phillip <phuang@plasmon.cn> wrote:
> Hi folks,
>
> Currently we plan to use NFSV4 with Kerberos:
> KDC: Windows 2K AD
>
> NFSv4 server: CentOS 4.4 with 2.6.20 kernel
> # cat /etc/exports
> /XFS/NFS4 gss/krb5
> (rw,fsid=0,insecure,no_root_squash,no_subtree_check,sync)
>
> Client: CentOS 4.4
>
> When I use Ktpass to create keytab:
>
> C:> Ktpass princ administrator/PLASMON.SIT@PLASMON.SIT mapuser
> administrator -pass admin out unixmachine.keytab
> C:> Ktpass princ root/PLAMONS.SIT@PLASMON.SIT mapuser root -
> pass admin
> out unixmachine_1.keytab
>
>
> and copy this output keytabs to NFSv4 server, and then export
> them with
> kinit well.
>
> However, when I attempt to start NFS service, the rpcsvcgssd
> failed.
>
> Then I try to execute these below commands
>
> [root@nfsv4 kevin]# rpc.svcgssd -fvvv
> ERROR: GSS-API: error in gss_import_name(): An invalid name
> was supplied
> - Hostname cannot be canonicalized
> unable to obtain root (machine) credentials
> do you have a keytab entry for nfs/<your.host>@<YOUR.REALM>
> in /etc/krb5.keytab?
>
> as the error message on the server said: you need a keytab of the
> form
>
> nfs/<your.host>@<YOUR.REALM>
>
> the root/<your.host>@<YOUR.REALM> or
> administrator/<your.host>@<YOUR.REALM> won/t work.
>
> -->Andy
>
>
> [root@nfsv4 kevin]# rpc.gssd -fvvv
> Using keytab file '/etc/krb5.keytab'
> Processing keytab entry for principal
> 'administrator/PLASMON.SIT@PLASMON.SIT'
> We will NOT use this entry
> (administrator/PLASMON.SIT@PLASMON.SIT)
> Processing keytab entry for principal
> 'root/PLASMON.SIT@PLASMON.SIT'
> We will NOT use this entry (root/PLASMON.SIT@PLASMON.SIT)
> ERROR: No usable keytab entries found in keytab
> '/etc/krb5.keytab'
> Do you have a valid keytab entry for
> nfs/<your.host>@<YOUR.REALM> in
> keytab file /etc/krb5.keytab ?
> Continuing without (machine) credentials - nfs4 mounts with
> Kerberos
> will fail
> processing client list
>
>
> Did I take mistakes in creating keytab?
>
>
> Please help me fix this issue.
> Thanks in advance.
>
> Regards,
> Phillip
>
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance
> to share your
> opinions on IT & business topics through brief surveys-and
> earn cash
> http://www.techsay.com/default.php?
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-04 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 10:10 can not start NFSv4 with Kerberos 5 Phillip
2007-04-03 11:46 ` William A. (Andy) Adamson
2007-04-03 12:13 ` Phillip
2007-04-03 13:18 ` William A. (Andy) Adamson
2007-04-03 14:21 ` Kevin Coffman
2007-04-04 2:17 ` Phillip
2007-04-04 15:30 ` Kevin Coffman
2007-04-04 8:43 ` Phillip [this message]
2007-04-04 15:47 ` Kevin Coffman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1175676220.3572.21.camel@milan \
--to=phuang@plasmon.cn \
--cc=andros@citi.umich.edu \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox