@abh3 Concerning the unresponsive state, it is just that. `xrootd` continues to run. It does not terminate. It just does nothing and doesn't respond. It is confusing for our monitoring because `xrootd` appears to be running even though it is effectively dead. The data node becomes a black hole that receives requests and ignores them. The way I found to recognize this problem is to check the `xrootd.log`. If it ends with "initialization failed.", that indicates the problem. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1721#issuecomment-1184968766 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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