@amadio As far as I know, this happened frequently in previous versions. The xrootd server is a server that provides a proxy connection to the dCache XRootD door for CMS AAA response. Therefore, restarting the server in the middle does not affect the service itself. That's why I didn't report it until now. However, there were cases where the core dump files generated by leaving the core dump size unlimited on that server ran out of /var space and affected the postgresql server in dCache. As a workaround, adjusting the core dump size to 0 is enough for us. However, we're making this request to fix the issue in the first place.

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

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