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
--
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
