Ok, sounds like that we can rule the 'standing queue' out as a possibility! Since I don't use checksum scripts, I never debugged that on my own -- @wyang007 might have more insight.

In that case, I'm a bit befuddled where to turn next. I assume that you have already eliminated various standard network problems? Are there any idle timeouts in the server you've set that might be terminating the connection unexpectedly?

It's not really a step toward solution but, in terms of having fewer moving parts, can you reproduce in a data-server-only setup? Always hard to track the back and forth between the data server and redirector; would be nice to have the logs in one place.

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

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