 |
 |
Hi @IgorPelevanyuk. Thanks a lot for your report and debug logs. I think there's been progress in understanding the underlying issue and there are now a couple of PR which aim to solve the problem. (Those are PR #1824 & PR #1829). Those will go through some more internal discussion or review and then I hope we'll be able to get the problem fixed. There was another issue reported which is likely the same - in that case against xrdcp 5.5.0, but I've looked at your logs and as far as I understand it is the same problem: Two issues; the hang of the transfer and subsequently the expected recovery of the transfer. As you reported, having certain parameters appears to change whether the recovery happens or not (with eventual timeout in case of no recovery). This is not because to the what the parameter itself is supposed to do, but rather an indirect consequence of the handling of certain options inside the xrootd client library. (In this case when xrd.gsiusrpxy is present I believe the recovery doesn't happen; the option xrd.wantprot does not impact the recovery in this way). -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1813#issuecomment-1317228883 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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