 |
 |
First, could you tell me what the error was that prevented the file from being deleted? I am looking at the log snippet posted above but it does not appear to be related to the error encountered during initialization. However, it does seem to imply that the multi-user plugin is being used. If so, it is incompatible with POSC and the only solution is to turn off POSC:
ofs.persist off
https://xrootd.slac.stanford.edu/doc/dev54/ofs_config.htm#_Toc89982386
I should note that multi-user is incompatible with checkpointing as well and that needs to be turned off as well:
ofs.chkpnt disable
https://xrootd.slac.stanford.edu/doc/dev54/ofs_config.htm#_Toc89982374
The next question is what do you mean by 'unresponsive state'? For any kind of initialization failure the xrootd daemon simply exits. So, clients connecting to the daemon will get an error (i.e. unable to connect). The cmsd will continue but will tell the redirectors that it is connected to that server operation has been suspended (i.e. there is no xrootd daemon running) and no clients should be sent to that server. This would be the case whether or not the cmsd there was running.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
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