URL:
<http://savannah.cern.ch/bugs/?87887>
Summary: xrootdfs bug with sss in mount instructs
Project: XROOTD
Submitted by: bdouglas
Submitted on: 2011-10-18 07:51
Severity: 4 - Important
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: yangw
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Fixed by commit(s):
_______________________________________________________
Details:
On node ascint3.hep.anl.gov inside /etc/fstab I have these xrootdfs mount
instructions:
xrootdfs /atlas8/atlas fuse
rdr=root://atlas8.hep.anl.gov:1094//atlas,uid=10017,sss=/var/spool/xrootd/.xrd/sss.keytab
0 0
xrootdfs /atlas22/atlas fuse
rdr=root://atlas22.hep.anl.gov:1094//atlas,uid=10017,sss=/var/spool/xrootd/.xrd/sss.keytab
0 0
(mount from two remote machines their xrootd partitions)
Using this command -
[root@ascint3 ~]# mount -t fuse -a
XrdSec: No authentication protocols are available.
Yet, the libraries exist -
[root@ascint3 ~]# ldd /usr/bin/xrootdfs
linux-vdso.so.1 => (0x00007fff282f0000)
libXrdFfs.so.0 => /usr/lib64/libXrdFfs.so.0 (0x0000003d1f600000)
libfuse.so.2 => /lib64/libfuse.so.2 (0x0000003ee8200000)
libXrdPosix.so.0 => /usr/lib64/libXrdPosix.so.0 (0x0000003d1e600000)
libXrdClient.so.0 => /usr/lib64/libXrdClient.so.0
(0x0000003d1ea00000)
libXrdSecsss.so.0 => /usr/lib64/libXrdSecsss.so.0
(0x0000003d1ee00000)
libXrdCryptoLite.so.0 => /usr/lib64/libXrdCryptoLite.so.0
(0x0000003d1f200000)
libXrdUtils.so.0 => /usr/lib64/libXrdUtils.so.0 (0x0000003d1e200000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003fd4c00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003fd4800000)
librt.so.1 => /lib64/librt.so.1 (0x0000003fd5400000)
libssl.so.6 => /lib64/libssl.so.6 (0x0000003fe1200000)
libcrypto.so.6 => /lib64/libcrypto.so.6 (0x0000003fda800000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003fe6600000)
libm.so.6 => /lib64/libm.so.6 (0x0000003fd4400000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003fe2600000)
libc.so.6 => /lib64/libc.so.6 (0x0000003fd4000000)
/lib64/ld-linux-x86-64.so.2 (0x0000003fd3c00000)
libgssapi_krb5.so.2 => /usr/lib64/libgssapi_krb5.so.2
(0x0000003fe0200000)
libkrb5.so.3 => /usr/lib64/libkrb5.so.3 (0x0000003fdd600000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003fdb800000)
libk5crypto.so.3 => /usr/lib64/libk5crypto.so.3 (0x0000003fdfe00000)
libz.so.1 => /usr/lib64/libz.so.1 (0x0000003fd5000000)
libkrb5support.so.0 => /usr/lib64/libkrb5support.so.0
(0x0000003fde200000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003fde600000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003fd9c00000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003fd5800000)
libsepol.so.1 => /lib64/libsepol.so.1 (0x0000003fd5c00000)
[root@ascint3 ~]# ls -l /usr/lib64/libXrdSecsss.so.0
lrwxrwxrwx 1 root root 21 Oct 10 12:00 /usr/lib64/libXrdSecsss.so.0 ->
libXrdSecsss.so.0.0.1
and the keytab file has the proper ownership -
[root@ascint3 ~]# id xrootd
uid=10017(xrootd) gid=501(atlas) groups=501(atlas)
context=root:system_r:unconfined_t:SystemLow-SystemHigh
[root@ascint3 ~]# ls -l /var/spool/xrootd/.xrd/sss.keytab
-rw------- 1 xrootd atlas 138 Oct 11 07:41 /var/spool/xrootd/.xrd/sss.keytab
Note if I change the mount string to -
xrootdfs /atlas8/atlas fuse
rdr=root://atlas8.hep.anl.gov:1094//atlas,uid=10017 0 0
xrootdfs /atlas22/atlas fuse
rdr=root://atlas22.hep.anl.gov:1094//atlas,uid=10017 0 0
It works.
Any idea what further debugging I should do?
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?87887>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
