From: Steve Dickson <SteveD@redhat.com>
To: Vladimir Elisseev <vovan@vovan.nl>
Cc: NFS list <linux-nfs@vger.kernel.org>
Subject: Re: rpc.svcgssd problem after updating client 1.2.2->1.2.3
Date: Mon, 21 Mar 2011 10:30:49 -0400 [thread overview]
Message-ID: <4D876119.3090007@RedHat.com> (raw)
In-Reply-To: <1300685799.18075.7.camel@vovan.net.home>
On 03/21/2011 01:36 AM, Vladimir Elisseev wrote:
> Steve,
>
> The segfault on the client side is gone after client reboot. This
> segfault occurs when nfs-utils has been updated and then I just restart
> corresponding services (rpcbind, rpc.idmapd, rpc.gssd) without rebooting
> the client. Now client simply exits with the lines below (as I described
> initially in my first mail):
> mount.nfs: mount(2): Permission denied
> mount.nfs: access denied by server while mounting ...
Ok.. to find out where rpc.gssd is segfaulting do the following:
# debuginfo-install nfs-utils
(assuming Fedora)
# gdb /usr/sbin/rpc.gssd
gdb> run -f -vvv
(When the segfault happens)
gdb> bt
(which will show the backtrace)
steved.
>
> Regards,
> Vladimir.
>
> On Sat, 2011-03-19 at 22:19 -0400, Steve Dickson wrote:
>>
>> On 03/19/2011 03:56 AM, Vladimir Elisseev wrote:
>>> Kevin,
>>>
>>> I have some updates. I recompiled nfs-utils and dependencies (libgssglue
>>> keyutils librpcsecgss libtirpc) on the server and on the test client.
>>> Nevertheless, while on the server side I see the same error:
>>> rpc.svcgssd[8390]: qword_eol: fflush failed: errno 22 (Invalid argument)
>>> on the client side rpc.gssd segfault(!):
>>> kernel: rpc.gssd[2107] segfault at 4 ip 0000003ef9430805 sp 00007fff655cdd10 error 4 in libgssapi_krb5.so.2.2[3ef9400000+3e000]
>>> Reverting back to nfs-utils 1.2.2 on the client and everything is fine.
>>> Below are relevant log entries from KDC when using nfs-utils 1.2.2 and 1.2.3 on the client:
>>>
>>> ****** nfs-utils 1.2.2 *******
>>> Mar 19 07:56:27 srv2 krb5kdc[7945]: AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.1.8: ISSUE: authtime 1300517787, etypes {rep=18 tkt=18 ses=18}, host/vbox.xxx.xxx@X.X for krbtgt/X.X@X.X
>>> Mar 19 07:56:28 srv2 krb5kdc[7945]: TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.1.8: ISSUE: authtime 1300517787, etypes {rep=18 tkt=18 ses=18}, host/vbox.xxx.xxx@X.X for nfs/nfs.xxx.xxx@X.X
>>> Mar 19 07:56:28 srv2 krb5kdc[7945]: TGS_REQ (3 etypes {1 3 2}) 192.168.1.8: ISSUE: authtime 1300517787, etypes {rep=18 tkt=18 ses=1}, host/vbox.xxx.xxx@X.X for nfs/nfs.xxx.xxx@X.X
>>>
>>> ****** nfs-utils 1.2.3 *******
>>> Mar 19 08:22:22 srv2 krb5kdc[7945]: AS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.1.2: ISSUE: authtime 1300519342, etypes {rep=18 tkt=18 ses=18}, host/x.x.x@X.X for krbtgt/X.X@X.X
>>> Mar 19 08:22:22 srv2 krb5kdc[7945]: TGS_REQ (7 etypes {18 17 16 23 1 3 2}) 192.168.1.2: ISSUE: authtime 1300519342, etypes {rep=18 tkt=18 ses=18}, host/x.x.x@X.X for nfs/nfs.x.x@X.X
>>> then
>>> rpc.svcgssd[8390]: qword_eol: fflush failed: errno 22 (Invalid argument)
>>> and segfault on the client side.
>> Would it be possible to get a back trace from the core?
>>
>> steved.
>
prev parent reply other threads:[~2011-03-21 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 18:48 rpc.svcgssd problem after updating client 1.2.2->1.2.3 Vladimir Elisseev
2011-03-17 20:57 ` Steve Dickson
2011-03-18 5:49 ` Vladimir Elisseev
2011-03-17 22:13 ` Kevin Coffman
2011-03-18 5:43 ` Vladimir Elisseev
2011-03-18 13:35 ` Kevin Coffman
2011-03-18 13:54 ` Vladimir Elisseev
[not found] ` <20110318145204.20621su4mostcrk4@vovan.nl>
2011-03-18 15:19 ` Kevin Coffman
2011-03-18 15:48 ` Vladimir Elisseev
2011-03-18 16:36 ` Kevin Coffman
2011-03-19 7:56 ` Vladimir Elisseev
2011-03-20 2:19 ` Steve Dickson
2011-03-21 5:36 ` Vladimir Elisseev
2011-03-21 14:30 ` Steve Dickson [this message]
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=4D876119.3090007@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=vovan@vovan.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.