Skip to contentSkip to conversation

linux-image: on nfs4 server: RPC: AUTH_GSS upcall timed out Please check user daemon is running

DISCUSSION Daniel Kahn Gillmor 3 participants 7 messages Dec 8, 2011 – Aug 11, 2013

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hello Linux-NFS folks--

I've got an nfs4 server running linux kernel 3.1.1 with nfs-utils 1.2.4.

When an NFSv4 client connects to the server using sec=krb5p, the kernel emits:

[ 3505.754807] RPC: AUTH_GSS upcall timed out.
[ 3505.754810] Please check user daemon is running.

It's true, i don't have rpc.gssd running on the server (though i do have rpc.svcgssd running).

But the client can go ahead and mount the filesystem anyway, and users with the appropriate krb5 credentials on the clients can access files on the server based on their credentials.

So it's not clear to me what this warning is about. Should i be
running rpc.gssd on the nfs server? If so, what functionality am i losing out on by not running it? If i don't need to run it, why is the kernel emitting this message?

       --dkg
#1 lore raw
Quoted 13 lines · Daniel Kahn Gillmor

Hello Linux-NFS folks--

I've got an nfs4 server running linux kernel 3.1.1 with nfs-utils 1.2.4.

When an NFSv4 client connects to the server using sec=krb5p, the kernel emits:

[ 3505.754807] RPC: AUTH_GSS upcall timed out.
[ 3505.754810] Please check user daemon is running.

It's true, i don't have rpc.gssd running on the server (though i do have rpc.svcgssd running).

Quoted 6 lines

But the client can go ahead and mount the filesystem anyway, and users with the appropriate krb5 credentials on the clients can access files on the server based on their credentials.

So it's not clear to me what this warning is about. Should i be
running rpc.gssd on the nfs server?

Yes, if you're using NFSv4 then the client and server should each run both daemons.

Quoted 1 line

If so, what functionality am i losing out on by not running it?

You lose NFSv4.0 delegations, which depend on the ability for the server to contact the client to send delegation recalls. Delegations are optional, so you won't lose correctness, but you may lose some performance.

If you're using only v2, v3, or v4.1, that doesn't matter. (v2 and v3 lack delegations, and v4.1 sends callbacks over existing client-established connections).

Quoted 1 line

If i don't need to run it, why is the kernel emitting this message?

Nevertheless I have seen that message even on machines that were running both daemons, so I suspect there's a bug here; I haven't made it a priority to track it down since I haven't seen it cause any actual problems.

--b.

#2 lore raw
Quoted 2 lines · J. Bruce Fields

Yes, if you're using NFSv4 then the client and server should each run both daemons.

ah, thanks.

Quoted 6 lines
Quoted 1 line

If so, what functionality am i losing out on by not running it?

You lose NFSv4.0 delegations, which depend on the ability for the server to contact the client to send delegation recalls. Delegations are optional, so you won't lose correctness, but you may lose some performance.

Thanks, that's useful. Do the clients need to run cachefilesd as well to take advantage of delegation? Is there a document where i could find this sort of information without adding noise to the list?

Quoted 3 lines

If you're using only v2, v3, or v4.1, that doesn't matter. (v2 and v3 lack delegations, and v4.1 sends callbacks over existing client-established connections).

OK, gotcha. Is it possible to use 4.1 with linux kernel 3.1 and nfs-utils 1.2.5, or would i need to pull a more recent version?

Thanks, and sorry for the basic questions,

	--dkg
#3 lore raw
Quoted 8 lines · Daniel Kahn Gillmor
Quoted 2 lines · J. Bruce Fields

Yes, if you're using NFSv4 then the client and server should each run both daemons.

ah, thanks.

Quoted 2 lines
Quoted 1 line

If so, what functionality am i losing out on by not running it?

Quoted 7 lines
Quoted 4 lines

You lose NFSv4.0 delegations, which depend on the ability for the server to contact the client to send delegation recalls. Delegations are optional, so you won't lose correctness, but you may lose some performance.

Thanks, that's useful. Do the clients need to run cachefilesd as well to take advantage of delegation?

No.

Quoted 2 lines

Is there a document where i could find
this sort of information without adding noise to the list?

Hm, it should probably be in the FAQ. I think we want to make

	http://wiki.linux-nfs.org/

the place to go for Linux NFS information, so if you can't find this under there somewhere, let's think about where to put it. Suggestions welcomed.

Quoted 6 lines
Quoted 3 lines

If you're using only v2, v3, or v4.1, that doesn't matter. (v2 and v3 lack delegations, and v4.1 sends callbacks over existing client-established connections).

OK, gotcha. Is it possible to use 4.1 with linux kernel 3.1 and nfs-utils 1.2.5, or would i need to pull a more recent version?

It should be possible. 4.1 is somewhat new, though.

--b.

#4 lore raw
Quoted 5 lines · J. Bruce Fields
Quoted 2 lines · Daniel Kahn Gillmor

Thanks, that's useful. Do the clients need to run cachefilesd as well to take advantage of delegation?

No.

Is there a way that i can check to be sure that delegations are actually happening? What kind of performance improvement would you expect to see with delegatons happening on, say, a standard desktop user's homedir workload?

         --dkg
#5 lore raw
Quoted 9 lines · Daniel Kahn Gillmor
Quoted 5 lines · J. Bruce Fields
Quoted 2 lines · Daniel Kahn Gillmor

Thanks, that's useful. Do the clients need to run cachefilesd as well to take advantage of delegation?

No.

Is there a way that i can check to be sure that delegations are actually happening?

On the client I suppose you'll eventually start seeing DELEG_RETURN calls in /proc/self/mountstats. On the server side the nfsd4_delegations line of /proc/slabinfo should give a hint.

Quoted 3 lines

What kind of performance improvement would you expect to see with delegatons happening on, say, a standard desktop user's homedir workload?

I don't know. If you get any test results that would be interesting.

--b.