Print

Print

hi @bbockelm I was wondering if have any other traces from other occurrences of deadlocks, e.g. 3 or 4 more, and if you could also attach them.

Unfortunately, there's only one container where I have CAP_SYS_PTRACE enabled (working on this for the others) and it's the current deadlocked one. If we think we've got enough from this example, I can bounce the container and hopefully catch it happening again.

While this is open, we deployed an auto-restart when the process deadlocks -- we'll be able to check from the event log how frequently things are occurring.

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

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