Thanks Simo, I apologize for the copy and paste error. You are
correct about it being "ldd /usr/sbin/rpc.gssd" command.
The actual error message we get is from the mount command:
mount.nfs: access denied by server while mounting
hnas.engr.uconn.edu:/EngrUser/users/rohitm
I got a little more output with mount -v
root@c27-00:~# mount -vvv hnas.engr.uconn.edu:/EngrUser/users/rohitm
/foo -o sec=krb5
mount: fstab path: "/etc/fstab"
mount: mtab path: "/etc/mtab"
mount: lock path: "/etc/mtab~"
mount: temp path: "/etc/mtab.tmp"
mount: UID: 0
mount: eUID: 0
mount: no type was given - I'll assume nfs because of the colon
mount: spec: "hnas.engr.uconn.edu:/EngrUser/users/rohitm"
mount: node: "/foo"
mount: types: "nfs"
mount: opts: "sec=krb5"
mount: external mount: argv[0] = "/sbin/mount.nfs"
mount: external mount: argv[1] =
"hnas.engr.uconn.edu:/EngrUser/users/rohitm"
mount: external mount: argv[2] = "/foo"
mount: external mount: argv[3] = "-v"
mount: external mount: argv[4] = "-o"
mount: external mount: argv[5] = "rw,sec=krb5"
mount.nfs: timeout set for Fri Aug 2 08:04:08 2013
mount.nfs: trying text-based options
'sec=krb5,vers=4,addr=137.99.203.4,clientaddr=137.99.2.29'
mount.nfs: mount(2): Permission denied
mount.nfs: access denied by server while mounting
hnas.engr.uconn.edu:/EngrUser/users/rohitm
So there is unfortunately no more info available from mount command and
rpc.gssd output did not have any red flags for me. I'm trying to find
out if there is a way to get more information from the NFS server
itself, but as of now I'm not sure how to do that.
Thanks,
Rohit
On 08/01/2013 10:33 PM, Simo Sorce wrote:
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.
--
Rohit Mehta
Computer Engineer
University of Connecticut
Engineering Computing Services
371 Fairfield Road Unit 2031
Storrs, CT 06269-2031
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
