It has been suggested that this could be a malloc related problem, unfortunately on both machines there are several Gb of free RAM and no anomalously high load which could suggest the RAM being constantly allocated/deallocated.

Luckily, there is about a 0% chance this is the issue. That reference to out-of-memory happens for any error generated by the prior function. This is the real issue:

200727 18:39:31 8213 XrdLink: attempt to reuse active link

Your hint about the TCP probe is perhaps a good place to start. What's the maximum number of file descriptors set for xrootd (look at /proc/$PID/limits)? I wonder if something is churning through FDs rapidly...

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