Print

Print

I suspect it's 3rd party copy coupled with checksum calculation. There is a known memory leak in that combination. That needs to be verified and can be done by looking at the log.
…
On Wed, 17 Mar 2021, Kenyi Hurtado wrote: Unfortunately, neither the user that found the issue nor I were able to reproduce this via e.g.: xrdcp, so it's something that happened under production load only. We got back to 4.11 before attempting to debug the issue further with 4.12 because it was affecting other users too. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #1430 (comment)

We can do that! What kind of message should we be looking at? I looked for "checksum" on the server side xrootd logfile and didn't find anything.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1430#issuecomment-801502037", "url": "https://github.com/xrootd/xrootd/issues/1430#issuecomment-801502037", "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