Closed cfgamboa closed 3 months ago
From
DEBUG Initial TURLs: gsiftp;https;root
DEBUG Reordered TURLs: https;gsiftp;root
DEBUG Service endpoint resolution, resolved from FULL SURL srm://dcblsrm.sdcc.bnl.gov:8443/srm/managerv2?SFN=/pnfs/sdcc.bnl.gov/tape/belle/Raw/e0030/physics/r02279/sub00/test.door05.nc.10 -> httpg://dcblsrm.sdcc.bnl.gov:8443/srm/managerv2
DEBUG SRM context recycled for httpg://dcblsrm.sdcc.bnl.gov:8443/srm/managerv2
SRM uses HTTPS to instantiate the transfer. It seems that DAVs uses /etc/hosts to Resolve IP/Hostname. Only one door had the internal IPV6 hostname enabled.
The issue seems to be now cositently addressed by including all internal IPV6 component in the other 2 doors.
After that my test did not failed. I see similar FTS jobs successfully finishing in the last 2 hours.
Hello,
This transfer is failing with error
DNS name not found [response code 3]
, this is not persistent in some cases the same transfer succeeded.The resolution of the doors on the srm is working as usual.
The dcache version is dcache-8.2.26-1.noarch
Could you please advise.
All the best, Carlos
Bellow the entire trace