 |
 |
Hi Tom, Indeed that is not the expected behaviour with the patch I gave to Brian. He said he would include the backported 3.2 patch in the CMS software suite. Without the patch, you will indeed see that a retry is not performed. Andy On Mon, 8 Sep 2014, Tommaso Boccali wrote: > Ciao, in CMS we just moved out SAM tests to a newer version, in order to solve issues we had previously with a 3_1 xrootd version. > > Now we use: > > Tool info as configured in location /tmp/tboccali/CMSSW_7_1_7 > +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > Name : xrootd > Version : 3.2.4-cms2 > ++++++++++++++++++++ > > what we see is that after a connection to a broken server (certifica problems, most probably), a retry does not see to be issued: > > http://dashb-cms-sum.cern.ch/dashboard/request.py/getMetricResultDetails?hostName=cmsrm-cream03.roma1.infn.it&flavour=CREAM-CE&metric=org.cms.WN-xrootd-fallback&timeStamp=2014-09-08T08:25:41Z > > is this expected? Brian told me we had a patch from you for a similar problem, so I wanted to make sure this is NOT the expected behavior. > > thanks a lot > > tom > > --- > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/138 --- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/138#issuecomment-54904117 ######################################################################## 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