 |
 |
@simonmichal : I could grant you access to the existing setup if you had an X509 cert registered with the ATLAS VO (I did not find you in VOMS; so I guess you don't have one). `-R` for `xrdfs ls` worked fine, no issues there. Only `xrdcp -r` has problems. So I followed up with the debug logs. The logs are only slightly obfuscated (IP addresses, hostnames). The redirector is `xrootd.example.com`, the nodes with access to the shared FS are all `xrootdXXX.example.com` with XXX being a three-digit number. There are nodes from 001 to 007. Here you go: - Log from `xrdfs ... ls -ul ...` [xrdfs-lsul.log](https://github.com/xrootd/xrootd/files/3040780/xrdfs-lsul.log) - Log from `xrdfs ... ls -R ...` [xrdfs-lsR.log](https://github.com/xrootd/xrootd/files/3040784/xrdfs-lsR.log) - Log from `xrdcp -r ... ...` [xrdcp-r.log](https://github.com/xrootd/xrootd/files/3040789/xrdcp-r.log) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/954#issuecomment-479664494 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1