Print

Print

Indeed! Otoh it seems to try for every operation (given the overall slowdown of the reading to >40 minutes, from originally 30 seconds), and I'd hope that the resilience could happen a bit faster than 2.5 minutes - but I do not know the details nor whether that's cause by our usage in ROOT or xrootd.

This seems to have been caused by broken ipv6 routing; renewing the ipv6 address resurrected things to a point where now ipv6 works on that machine. I could try with a hand-assigned, hopefully not routed ipv6 address to get more of a log dump of what happens after the initial connection should that be useful?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1779/1240503744@github.com>

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