Well, it would either be that the server that has the chuck is improperly configured or just isn't there. Who prints that message and what pieces of information are used? The "(delayed)" part is mysterious to me. Anyway, can we see the redirector cmsd log for the cluster? That will give us more insight as what is happening. Andy -----Original Message----- From: Jacek Becla Sent: Friday, May 08, 2015 10:06 PM To: Serge Monkewitz Cc: qserv-l Subject: Re: [QSERV-L] next steps I wonder if that has anything to do with Fabrice's problems: Resource(/chk/LSST/1234567890): 20150507-14:24:01, Error accessing resource (delayed), 2, No servers are available to write the file.) Perhaps the special chunk 1234567890 has not been registered in the system? J. On 05/07/2015 11:24 PM, Serge Monkewitz wrote: > See /home/smm/in2p3_logs (@NCSA) for a copy of var/log from the in2p3 > master run directory. > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1