Several ULegacy signal samples are no longer available on DAS!

[kjaffel]

Hello,

I am encountering an issue with several signal samples that were centrally produced. Previously, these files were readily available, but now I am noticing a concerning message indicating Dataset size: 0 (0.0) for many samples. For instance, the files associated with this sample ( see attached picture ) were previously accessible on T2_BE_UCL, and I had been working with them until today.

/storage/data/cms/store/mc/RunIISummer20UL16NanoAODv9/HToZATo2L2B_MH-379p00_MA-80p99_tb-20p00_TuneCP5_bbH4F_13TeV-madgraph-pythia8/NANOAODSIM/106X_mcRun2_asymptotic_v17-v1/40000/F54A9B20-4FF7-B443-A080-920AFAB8CEC2.root
/storage/data/cms/store/mc/RunIISummer20UL16NanoAODv9/HToZATo2L2B_MH-379p00_MA-80p99_tb-20p00_TuneCP5_bbH4F_13TeV-madgraph-pythia8/NANOAODSIM/106X_mcRun2_asymptotic_v17-v1/40000/EDEFFFB4-298D-EB4B-AA8D-4B4D78CB4F26.root
/storage/data/cms/store/mc/RunIISummer20UL16NanoAODv9/HToZATo2L2B_MH-379p00_MA-80p99_tb-20p00_TuneCP5_bbH4F_13TeV-madgraph-pythia8/NANOAODSIM/106X_mcRun2_asymptotic_v17-v1/2430000/76012D51-4B97-7A48-94B5-FA6EE27100F2.root
/storage/data/cms/store/mc/RunIISummer20UL16NanoAODv9/HToZATo2L2B_MH-379p00_MA-80p99_tb-20p00_TuneCP5_bbH4F_13TeV-madgraph-pythia8/NANOAODSIM/106X_mcRun2_asymptotic_v17-v1/40000/4FCB119C-A81B-8844-8EBD-2E3C9292EC3E.root
/storage/data/cms/store/mc/RunIISummer20UL16NanoAODv9/HToZATo2L2B_MH-379p00_MA-80p99_tb-20p00_TuneCP5_bbH4F_13TeV-madgraph-pythia8/NANOAODSIM/106X_mcRun2_asymptotic_v17-v1/40000/018EEDF7-989F-C344-A31A-61B7DBF51385.root
/storage/data/cms/store/mc/RunIISummer20UL16NanoAODv9/HToZATo2L2B_MH-379p00_MA-80p99_tb-20p00_TuneCP5_bbH4F_13TeV-madgraph-pythia8/NANOAODSIM/106X_mcRun2_asymptotic_v17-v1/40000/600622C3-0719-F745-B23A-BD86DE79F563.root

Any feedback will be very much appreciated.
Thanks!

[vkuznet]

DAS is not the place to ask these questions. DAS does not hold any data, when you place your query DAS on your behalf ask other CMS services like DBS/Rucio about the data you are looking for and present you results. If there is no data upstream DAS has nothing to do with it. You need to investigate with DBS/Rucio team where is your files and why their are disappear.

To debug your issue you may use your query with dasgoclient and use --verbose 3 flag to see actual HTTP calls DAS is doing to upstream services.

[kjaffel]

Thanks a lot for the quick respond. I forward the issue to DBS. Rucio team indicated that they are not the appropriate contacts for this matter either.
--verbose 3 it doesn't provide much insight, or perhaps I'm unsure what exactly I should be looking for
dasgo.log

But I see the files when I do: dasgoclient -query 'file dataset=/HToZATo2L2B_MH-379p00_MA-80p99_tb-20p00_TuneCP5_bbH4F_13TeV-madgraph-pythia8/RunIISummer20UL16NanoAODv9-106X_mcRun2_asymptotic_v17-v1/NANOAODSIM status=*'
I thought this invalid status affect only private samples in prod/phys03 and not centrally produced one as was mentioned here: https://cms-talk.web.cern.ch/t/dbs-phys03-files-wrongly-invalidated/31152

I will keep looking. Thanks again!