Dear Andy,
I appreciate your attention, thank you. For this issue, I have not done any testing with HTTPS so far, just roots://
and xrdfs ... query
.
When I'd mentioned issue 1736, I should have said it more carefully. Issue 1736 mentioned a similar issue to this one in the discussion (error_syscall), but the overall problem indeed seemed different (and related to https rather than root). It was the only issue I could find that was remotely similar.
We still need the TLS tracing enabled and what the log says when a failure occurs.
I'd turned all the knobs I could find--xrootd.trace all
and xrd.trace all
--on the server for the log output shared above. I'd be happy to make further changes and repeat.
Regards,
John
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
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