 |
 |
Hi Adrian, The issue is not with the redirector but with the data servers. Whatever the client is looking for cannot be accessed at one or more data servers. The typical recovery for this problem is to go back to the redirector asking for a different data server. If the error persists the client eventually rejects all possible data servers and the redirector has no choice but to say you rejected all the ones that could possibly have teh file so there is nothing more I can do. I would suggest setting XRD_LOGLEVEL to Debug (probably Error would work as well) and see what is actually happening in tghe client. Andy On Mon, 13 Dec 2021, Adrian Sevcenco wrote: > Hi! In the experiment writing tests i have for almost a day complete failures > with: > > xrdcp exited with exit code 54: [ERROR] Server responded with an error: > [3011] Unable to access file; eligible servers shunned. (destination) > > The problem is that the cluster is not loaded: http://cern.ch/go/VM7N > and at least 20% free space on any available partitions.. > > How can i pinpoint the exact cause of "shunning" > The redirector configuration is: https://codimd.web.cern.ch/s/ghqyZXrQa > > Only the redirector is involved in the shunning operation isn't? > > Thanks a lot! > Adrian > > > > > > ######################################################################## > Use REPLY-ALL to reply to list > > To unsubscribe from the XROOTD-L list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1 > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1