LISTSERV 16.5 - XROOTD-DEV Archives

It is not something going on with a specific machine: it's every CMS XrootD instance at INFN Tier1.
It's not something recent, we have been restarting the service from time to time following thread saturation for one year.
We started debugging this together with colleagues from CERN one year ago (I mean thread saturation, no traffic and so on).
They suggested we installed 4.12.4 release, therefore we upgraded to this version.
Now I've asked CMS whether it's fine to upgrade futher; which version would you suggest?
While waiting for a reply from CMS, we would be very happy to run with additional tracing enabled and produce a core file. If you provide instructions, we are happy to try.
Thank you very much for your help,
lucia

—
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/1799#issuecomment-1311657587", "url": "https://github.com/xrootd/xrootd/issues/1799#issuecomment-1311657587", "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