linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Mamalakis <mamalos@eng.auth.gr>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfsv3 gssapi client?
Date: Mon, 20 Sep 2010 12:47:31 +0300	[thread overview]
Message-ID: <4C972DB3.2050405@eng.auth.gr> (raw)
In-Reply-To: <20100917174328.GC25515@fieldses.org>

  Hi Bruce and thanx for the reply,

to your questions now:

On 17/09/2010 20:43, J. Bruce Fields wrote:
>
>> # mount -t nfs -o sec=krb5 fbsdserver:/exports /mnt
>>
> Was there supposed to be some error output there?  Or did the mount just
> hang?
>
The mount command stalls and no output is presented; only the messages 
on /var/log/messages.
>> Sep 17 16:06:01 linuxclient kernel: svc: failed to register lockdv1
>> RPC service (errno 111).
> 111 is ECONNREFUSED.  I'm not sure why that's failing.  (Should failure
> to register lockd fail the whole mount?  I thought it would at worst
> result in ENOLCK on lock requests?) Do you get better results if you
> mount with nolock?
>
Now this is peculiar. If run mount -o nolock then gssd segfaults. This 
is because it creates a /tmp/krb5cc_machine_REALM ticket, and when it 
access it, it segfaults. To overcome this issue I deleted the temporary 
file, and ran gssd manually to see its output. So, mount returned the 
following:

[root@linuxclient ~]# mount -t nfs -o sec=krb5,nolock 
fbsdserver:/exports /mnt
mount.nfs: access denied by server while mounting fbsdserver:/exports

and gssd console output read:

destroying client /var/lib/nfs/rpc_pipefs/nfs/clnt110
handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt112)
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 '
handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt112)
process_krb5_upcall: service is '<null>'
getting credentials for client with uid 0 for server fbsdserver
WARNING: Failed to create krb5 context for user with uid 0 for server 
fbsdserver
doing error downcall
destroying client /var/lib/nfs/rpc_pipefs/nfs/clnt113
handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt112)
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 '
handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt112)
process_krb5_upcall: service is '<null>'
getting credentials for client with uid 0 for server fbsdserver
WARNING: Failed to create krb5 context for user with uid 0 for server 
fbsdserver
doing error downcall
handling gssd upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt112)
handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2 '
handling krb5 upcall (/var/lib/nfs/rpc_pipefs/nfs/clnt112)
process_krb5_upcall: service is '<null>'
getting credentials for client with uid 0 for server fbsdclient.ee.auth.gr
WARNING: Failed to create krb5 context for user with uid 0 for server 
fbsdserver
doing error downcall
destroying client /var/lib/nfs/rpc_pipefs/nfs/clnt112
destroying client /var/lib/nfs/rpc_pipefs/nfs/clnt111

/var/log/messages shows nothing.


I think that's all regarding your questions.

Thanx again,

mamalos.

-- 
George Mamalakis

IT Officer
Electrical and Computer Engineer (Aristotle Un. of Thessaloniki),
MSc (Imperial College of London)

Department of Electrical and Computer Engineering
Faculty of Engineering
Aristotle University of Thessaloniki

phone number : +30 (2310) 994379


  parent reply	other threads:[~2010-09-20  9:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-17 15:54 nfsv3 gssapi client? George Mamalakis
2010-09-17 17:43 ` J. Bruce Fields
2010-09-17 18:35   ` Jeff Layton
2010-09-20  9:54     ` George Mamalakis
2010-09-17 18:39   ` Chuck Lever
2010-09-20  9:47   ` George Mamalakis [this message]
2010-09-20 14:56     ` J. Bruce Fields
2010-09-20 15:38       ` George Mamalakis
2010-09-20 16:06         ` Kevin Coffman
2010-09-20 16:07         ` J. Bruce Fields
2010-09-21  8:36           ` George Mamalakis
2010-09-21 13:51             ` J. Bruce Fields
2010-09-21 14:40               ` George Mamalakis
  -- strict thread matches above, loose matches on Subject: below --
2010-09-21 14:19 George Mamalakis

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=4C972DB3.2050405@eng.auth.gr \
    --to=mamalos@eng.auth.gr \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).