Print

Print


After exchanging configs, we removed the xrd.tls and xrd.tlsca from the redirector and replaced them with the http.cadir, http.cert, and http.key settings.
This seems to have decreased our FTS transfer failure rate from ≈94% to ≈38% (in the last two hours).
The mentions of fts-cms in /var/log/clustered/xrootd.log in redirector vs server have improved as well (more getting through).

So the updated config seems to be a step in the right direction.

I still see 15 min timeouts (FTS logs) after a successful transfer (checksum request):

TRANSFER [112] DESTINATION CHECKSUM (Neon): Could not read status line: Connection timed out

and I see (send failure) and (link SSL read error) in the redirector and server logs respectively.
But I also see them for requests that I know went well (e.g. ETF tests for CMS).

I've now also updated to Xrootd 5.5.0 (after confirming config change went into the right direction)


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: <xrootd/xrootd/issues/1736/1240805964@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1736#issuecomment-1240805964", "url": "https://github.com/xrootd/xrootd/issues/1736#issuecomment-1240805964", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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