* Kerberized NFS failure with 3.9.0-rc1 (and later)
@ 2013-06-08 20:15 richard
2013-06-09 7:59 ` richard
0 siblings, 1 reply; 3+ messages in thread
From: richard @ 2013-06-08 20:15 UTC (permalink / raw)
To: linux-nfs
Hi All,
I'm succesfully running a kerberized NFS system on a machine with linux
kernel 3.8.0 and 3.8.13. However when upgrading to 3.9, it's either giving
an access denied upon mount, or completely locking up.
Some details:
Client: debian unstable "Sid", kernel 3.9.0 (nfs-common=1.2.8-4)
Server: debian 7.0 "Wheezy", nfs-common=1.2.6-3
When upgrading the server to 3.9.0-rc1, it's giving access denied
When upgrading the server to 3.9.0 or 3.9.5, it's locking
There is no error on the server, but the logfile on the client mentions
the following:
rpc.gssd[1930]: ERROR: GSS-API: error in gss_free_lucid_sec_context():
GSS_S_NO_CONTEXT (No context has been established) - Unknown error
Jun 8 21:22:42 dell rpc.gssd[1930]: WARN: failed to free lucid sec context
Can anyone help out with this? Is there anything that needed to be
configured in the newer kernels? All crypto stuff and kerberos
configuration files are unchanged.
Thanks alot,
Richard van den Toorn
(The Netherlands)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Kerberized NFS failure with 3.9.0-rc1 (and later)
2013-06-08 20:15 Kerberized NFS failure with 3.9.0-rc1 (and later) richard
@ 2013-06-09 7:59 ` richard
2013-06-10 9:16 ` Sven Geggus
0 siblings, 1 reply; 3+ messages in thread
From: richard @ 2013-06-09 7:59 UTC (permalink / raw)
To: linux-nfs
Replying to myself, this looks to be the same problem as was reported by
Sven earlier this week:
http://www.spinics.net/lists/linux-nfs/msg37454.html
Happy to assist in debugging and getting this resolved.
Richard
> Some details:
>
> Client: debian unstable "Sid", kernel 3.9.0 (nfs-common=1.2.8-4)
> Server: debian 7.0 "Wheezy", nfs-common=1.2.6-3
>
> When upgrading the server to 3.9.0-rc1, it's giving access denied
> When upgrading the server to 3.9.0 or 3.9.5, it's locking
>
> There is no error on the server, but the logfile on the client mentions
> the following:
>
> rpc.gssd[1930]: ERROR: GSS-API: error in gss_free_lucid_sec_context():
> GSS_S_NO_CONTEXT (No context has been established) - Unknown error
> Jun 8 21:22:42 dell rpc.gssd[1930]: WARN: failed to free lucid sec
> context
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Kerberized NFS failure with 3.9.0-rc1 (and later)
2013-06-09 7:59 ` richard
@ 2013-06-10 9:16 ` Sven Geggus
0 siblings, 0 replies; 3+ messages in thread
From: Sven Geggus @ 2013-06-10 9:16 UTC (permalink / raw)
To: linux-nfs
richard@vdtoorn.nl wrote:
> Replying to myself, this looks to be the same problem as was reported by
> Sven earlier this week:
Jepp, I think so. Unfortunately I'm a bit stuck in debugging this, as
git-bisect just led me to another variant of broken behaviour (permission
denied instead of infinite hang during mount).
Wireshark output of Kernel 3.9.4 does not look all that interesting either
(10.1.7.30=client, 10.1.7.111=server):
No. Time Source Destination Protocol Length Info
1 0.000000 10.1.7.30 10.1.7.111 TCP 74 997 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1 TSval=1518792 TSecr=0 WS=128
2 0.000224 10.1.7.111 10.1.7.30 TCP 74 nfs > 997 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=18228 TSecr=1518792 WS=64
3 0.000250 10.1.7.30 10.1.7.111 TCP 66 997 > nfs [ACK] Seq=1 Ack=1 Win=14720 Len=0 TSval=1518793 TSecr=18228
4 0.000273 10.1.7.30 10.1.7.111 NFS 110 V4 NULL Call (Reply In 6)
5 0.000389 10.1.7.111 10.1.7.30 TCP 66 nfs > 997 [ACK] Seq=1 Ack=45 Win=14528 Len=0 TSval=18228 TSecr=1518793
6 0.000554 10.1.7.111 10.1.7.30 NFS 94 V4 NULL Reply (Call In 4)
7 0.000564 10.1.7.30 10.1.7.111 TCP 66 997 > nfs [ACK] Seq=45 Ack=29 Win=14720 Len=0 TSval=1518793 TSecr=18228
8 0.005250 10.1.7.30 10.1.7.111 TCP 74 60072 > nfs [SYN] Seq=0 Win=14600 Len=0 MSS=1460 SACK_PERM=1 TSval=1518794 TSecr=0 WS=128
9 0.005393 10.1.7.111 10.1.7.30 TCP 74 nfs > 60072 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460 SACK_PERM=1 TSval=18229 TSecr=1518794 WS=64
10 0.005409 10.1.7.30 10.1.7.111 TCP 66 60072 > nfs [ACK] Seq=1 Ack=1 Win=14720 Len=0 TSval=1518794 TSecr=18229
11 0.006228 10.1.7.30 10.1.7.111 NFS 1450 V4 NULL Call (Reply In 13)
12 0.006393 10.1.7.111 10.1.7.30 TCP 66 nfs > 60072 [ACK] Seq=1 Ack=1385 Win=17408 Len=0 TSval=18230 TSecr=1518794
13 0.016922 10.1.7.111 10.1.7.30 NFS 298 V4 NULL Reply (Call In 11)
14 0.016938 10.1.7.30 10.1.7.111 TCP 66 60072 > nfs [ACK] Seq=1385 Ack=233 Win=15744 Len=0 TSval=1518797 TSecr=18232
15 0.017931 10.1.7.30 10.1.7.111 NFS 126 V4 NULL Call
16 0.017950 10.1.7.30 10.1.7.111 NFS 270 V4 Call SETCLIENTID
17 0.017956 10.1.7.30 10.1.7.111 TCP 66 60072 > nfs [FIN, ACK] Seq=1445 Ack=233 Win=15744 Len=0 TSval=1518797 TSecr=18232
18 0.018916 10.1.7.111 10.1.7.30 TCP 66 nfs > 60072 [FIN, ACK] Seq=233 Ack=1446 Win=17408 Len=0 TSval=18233 TSecr=1518797
19 0.018935 10.1.7.30 10.1.7.111 TCP 66 60072 > nfs [ACK] Seq=1446 Ack=234 Win=15744 Len=0 TSval=1518797 TSecr=18233
20 0.056246 10.1.7.111 10.1.7.30 TCP 66 nfs > 997 [ACK] Seq=29 Ack=249 Win=15552 Len=0 TSval=18242 TSecr=1518797
Communication stalls here..
Sven
--
"Those who do not understand Unix are condemned to reinvent it, poorly"
(Henry Spencer)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-06-10 9:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-06-08 20:15 Kerberized NFS failure with 3.9.0-rc1 (and later) richard
2013-06-09 7:59 ` richard
2013-06-10 9:16 ` Sven Geggus
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).