Crash in HCAL DQM for Data relvals in 9-4-14-UL

[fabiocos]

From @prebello

PdmV would like to report a crash in 9-4-14-UL release (only observed after jobs injection in the system, not locally) related with Module: DigiPhase1Task:digiPhase1Task in HCAL DQM, the same of the issue reported in 10-2-0-pre3 below

#23259

Could you please inform if the fix #23262 proposed in this issue was backported to 9-4-X?

Any other suggestion, apart to remove @hcal from the DQM sequence, to fix it?

A link for the log of the recent crash (all new Data relvals in 9-4-14-UL affected)

https://cms-unified.web.cern.ch/cms-unified/report/prebello_RVCMSSW_9_4_14_ULRunDoubleMuon2017C_UL2017__RelVal_2017C_190702_233947_1928

[cmsbuild]

A new Issue was created by @fabiocos Fabio Cossutti.

@davidlange6, @Dr15Jones, @smuzaffar, @fabiocos, @kpedro88 can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[fabiocos]

assign dqm

@DryRun FYI

[cmsbuild]

New categories assigned: dqm

@jfernan2,@andrius-k,@schneiml,@fioriNTU,@kmaeshima you have been requested to review this Pull request/Issue and eventually sign? Thanks

[fabiocos]

@prebello @zhenhu do you have a tarball that allows us to reproduce the crash? I wonder why this crash is seen just now, as that code seems stable since long time, no data RelVal injected since last spring I would imagine?

[prebello]

@fabiocos @fioriNTU

the 2017B era has not crashed but from 2017C to 2017F
https://dmytro.web.cern.ch/dmytro/cmsprodmon/workflows.php?prep_id=CMSSW_9_4_14_UL__dataUL2017B-1562097746-RunDoubleMuon2017B_UL2017

Latest data rereco and relvals were done with 9-4-0.

Relvals were injected based on new implementation from prebello@2769090
using the standard commands runTheMatrix.py --what standard -l .... accordingly

My local test for 2017C is at /afs/cern.ch/user/p/prebello/prebello/public/PDMV/UL2017Tracker/CMSSW_9_4_14_UL/src/2017C
Actually, the local test is fine for all, although few HLT error msgs. Therefore I don't know how we could reproduce the crash.

[DryRun]

Hi all,

I created a PR to solve the crash at #27470. I was able to run the cmsDriver command from @franzoni on JetHT 2017C [1], but as @prebello says, it's possible that a successful local test doesn't reflect the crash.

cmsDriver.py Configuration/GenProduction/python/superfragment_cfi.py --fileout file:HiggsLLP_test.GENSIM.root --mc --eventcontent RAWSIM --datatier GEN-SIM --conditions 102X_upgrade2018_realistic_v11 --beamspot Realistic25ns13TeVEarly2018Collision --customise_commands="process.source.numberEventsInLuminosityBlock = cms.untracked.uint32(10)" --step GEN,SIM --nThreads 8 --geometry DB:Extended --era Run2_2018 --python_filename superfragment_cfg.py --no_exec --customise Configuration/DataProcessing/Utils.addMonitoring -n 100

[fabiocos]

#27470 has been merged