2013-10-12 17:27:48

by hanasaki

[permalink] [raw]
Subject: nfs RPC: AUTH_GSS upcall timed out and running nfs v4 without full kerberos : how?

1. Below appears to require krb for auth. Is this correct? How can nfs
v4 be setup and used over tcp? udp? and not require a full kerberos
server setup?

2. The stat issue is ok. It takes a long time to timeout which is
causing problems. Using the full directory path locally on the nfs
server works ok without stat issue or long timeouts.

3. the user daemon does appear to be running fine.

Oct 12 00:49:07 host-01 kernel: [ 1775.106615] RPC: AUTH_GSS upcall
timed out.
Oct 12 00:49:07 host-01 kernel: [ 1775.106615] Please check user daemon
is running.
Oct 12 00:49:07 host-01 rpc.mountd[3097]: authenticated mount request
from 10.1.1.30:762 for /storage/data-01/dist-export/pom.xml
(/storage/data-01)
Oct 12 00:49:07 host-01 rpc.mountd[3097]: can't stat exported dir
/storage/data-01/dist-export/pom.xml: No such file or directory

[email protected]


2013-10-12 17:53:33

by Chuck Lever

[permalink] [raw]
Subject: Re: nfs RPC: AUTH_GSS upcall timed out and running nfs v4 without full kerberos : how?


On Oct 12, 2013, at 1:27 PM, hanasaki <[email protected]> wrote:

> 1. Below appears to require krb for auth. Is this correct? How can nfs v4 be setup and used over tcp? udp? and not require a full kerberos server setup?

Simply ensure that rpc.gssd is running on your NFS clients. The exact procedure varies among Linux distributions. There is no need to perform any other configuration.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com