From: Simo Sorce <simo@redhat.com>
To: Rohit Mehta <rohitm@engr.uconn.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Trouble with kerberized NFS client after upgrading from nfs-utils 1.2.0 to 1.2.5
Date: Thu, 01 Aug 2013 22:33:22 -0400 [thread overview]
Message-ID: <1375410802.15733.216.camel@willson.li.ssimo.org> (raw)
In-Reply-To: <51FB0946.5020505@engr.uconn.edu>
On Thu, 2013-08-01 at 21:20 -0400, Rohit Mehta wrote:
> Thanks Simo, it doesn't look like libtirpc was available in previous
> (10.04) release of Ubuntu.
> root@c27-00:~# ldd /usr/sbin/
I assume this had ^^ rpc.gssd at the end and is just a copy&paste error.
> linux-vdso.so.1 => (0x00007fffeedff000)
> libgssglue.so.1 => /lib/libgssglue.so.1 (0x00007fb06778e000)
> libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3
> (0x00007fb0674c0000)
> libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2
> (0x00007fb0672bb000)
> libtirpc.so.1 => /lib/x86_64-linux-gnu/libtirpc.so.1
> (0x00007fb067093000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb066cd4000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb066acf000)
> libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3
> (0x00007fb0668a7000)
> libkrb5support.so.0 =>
> /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007fb06669f000)
> libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1
> (0x00007fb06649a000)
> libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
> (0x00007fb06627e000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x00007fb066061000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fb0679b8000)
> root@c27-00:~# locate libtirpc.so
> /lib/x86_64-linux-gnu/libtirpc.so.1
> /lib/x86_64-linux-gnu/libtirpc.so.1.0.10
> root@c27-00:~# ldd /lib/x86_64-linux-gnu/libtirpc.so.1
> linux-vdso.so.1 => (0x00007fff01dc1000)
> libgssglue.so.1 => /lib/libgssglue.so.1 (0x00007fb701d54000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x00007fb701b37000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb701777000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb701573000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fb7021a6000)
> root@c27-00:~#
Both are built against libgssglue so at least they are consistent, and
that is not the source of the problem as I suspected.
More information on the actual error would help.
Simo.
> On 08/01/2013 05:06 PM, Simo Sorce wrote:
> >
> > Rohit
> > Was libtirpc also updated ?
> > There has beena change recently where we eliminated the use of
> > libgssglue and you will get issues if both nfs-utils and libtirpc are
> > not compiled to use the same gssapi library.
> >
> > Please post ldd output on rpc.gssd and libtirpc.so to verify if this is
> > the issue.
> >
> > Simo.
> >
>
>
--
Simo Sorce * Red Hat, Inc * New York
next prev parent reply other threads:[~2013-08-02 2:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 20:46 Trouble with kerberized NFS client after upgrading from nfs-utils 1.2.0 to 1.2.5 Rohit Kumar Mehta
2013-08-01 21:06 ` Simo Sorce
2013-08-02 1:20 ` Rohit Mehta
2013-08-02 2:33 ` Simo Sorce [this message]
2013-08-02 12:15 ` Rohit Mehta
2013-08-02 14:23 ` Simo Sorce
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=1375410802.15733.216.camel@willson.li.ssimo.org \
--to=simo@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rohitm@engr.uconn.edu \
/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 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).