cms-sw / cmssw

CMS Offline Software
http://cms-sw.github.io/
Apache License 2.0
1.09k stars 4.33k forks source link

Failed to use local-connect in site-local-config.xml #37615

Open hernand opened 2 years ago

hernand commented 2 years ago

In https://github.com/cms-sw/cmssw/issues/29558 a mechanism was implemented in CMSSW to load the conditions data corresponding to a global tag from a file located in a directory specified in the site-local-config.xml file ( section). In the validation process to integrate the Barcelona Supercomputing Center into CMS operations, one of the steps (the HLT step) of a test workflow (see attached pset), using CMSSW_12_2_1, fails to run with the following error message:

export SCRAM_ARCH=slc7_amd64_gcc900 source /cvmfs/cms.cern.ch/cmsset_default.sh scram p CMSSW CMSSW_12_2_1 cd CMSSW_12_2_1/src eval scramv1 runtime -sh cmsRun configFile-HLT.py

%MSG-i ThreadStreamSetup: (NoModuleName) 19-Apr-2022 11:18:47 CEST pre-events setting # threads 4 setting # streams 4 %MSG ----- Begin Fatal Exception 19-Apr-2022 11:19:33 CEST----------------------- An exception of category 'Incomplete configuration' occurred while [0] Constructing the EventProcessor [1] Constructing ESSource: class=PoolDBESSource label='l1conddb' Exception Message: Did not find frontier-connect in calib-data section in /gpfs/projects/cie12/cms.conf/SITECONF/local/JobConfig/site-local-config.xml ----- End Fatal Exception -------------------------------------------------

It seems the application does not use the configured local-connect section of the site-local-config.xml file (see the attached file).

The mechanism was implemented from CMSSW version 11_2. It should be present in the version used for the test (CMSSW_12_2_1)

configFile-HLT.py.txt site-local-config.xml.txt

cmsbuild commented 2 years ago

A new Issue was created by @hernand Jose Hernandez.

@Dr15Jones, @perrotta, @dpiparo, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

davidlange6 commented 2 years ago

Likely due to https://github.com/cms-sw/cmssw/issues/27393 (So maybe 12_3_0 is better?)

On Apr 19, 2022, at 11:48 AM, Jose Hernandez @.***> wrote:

In #29558 a mechanism was implemented in CMSSW to load the conditions data corresponding to a global tag from a file located in a directory specified in the site-local-config.xml file ( section). In the validation process to integrate the Barcelona Supercomputing Center into CMS operations, one of the steps (the HLT step) of a test workflow (see attached pset), using CMSSW_12_2_1, fails to run with the following error message:

export SCRAM_ARCH=slc7_amd64_gcc900 source /cvmfs/cms.cern.ch/cmsset_default.sh scram p CMSSW CMSSW_12_2_1 cd CMSSW_12_2_1/src eval scramv1 runtime -sh cmsRun configFile-HLT.py

%MSG-i ThreadStreamSetup: (NoModuleName) 19-Apr-2022 11:18:47 CEST pre-events setting # threads 4 setting # streams 4 %MSG ----- Begin Fatal Exception 19-Apr-2022 11:19:33 CEST----------------------- An exception of category 'Incomplete configuration' occurred while [0] Constructing the EventProcessor [1] Constructing ESSource: class=PoolDBESSource label='l1conddb' Exception Message: Did not find frontier-connect in calib-data section in /gpfs/projects/cie12/cms.conf/SITECONF/local/JobConfig/site-local-config.xml ----- End Fatal Exception -------------------------------------------------

It seems the application does not use the configured local-connect section of the site-local-config.xml file (see the attached file).

The mechanism was implemented from CMSSW version 11_2. It should be present in the version used for the test (CMSSW_12_2_1)

configFile-HLT.py.txt site-local-config.xml.txt

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

hernand commented 2 years ago

I have tried with CMSSW_12_3_0_pre2 and I get the same error. I am not sure if the pset being used corresponds to a production workflow, but I think the point here is that it should be guaranteed that all conditions data are read from the global tag for a production workflow. Is that the case?