Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Tools/Manuals/TS109

From EGIWiki
< Tools
Revision as of 15:08, 15 September 2011 by Aesch (talk | contribs) (Created page with '{{TOC_right}} Category:FAQ ------ Back to Troubleshooting Guide ------ = gstat2 Cores format is wrong = == Error == All or some of: …')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Back to Troubleshooting Guide


gstat2 Cores format is wrong

Error

All or some of:

ERROR: some-ce.some-domain, The Cores format is wrong, Cores not set
ERROR: some-ce.some-domain, The Benchmark format is wrong, Benchmark not set
ERROR: some-ce.some-domain, The Cores format is wrong, Unspecified number of cores

Diagnosis

Each GlueSubCluster object should contain a value for the GlueHostProcessorOtherDescription attribute indicating at least the average number of logical cores per WN and possibly the corresponding HEP-SPEC06 benchmark value per core. At least WLCG sites should run that benchmark and publish the resulting value(s). Example:

GlueHostProcessorOtherDescription: Cores=4,Benchmark=8.15-HEP-SPEC06

Note that the number of cores need not be an integer when the subcluster is somewhat inhomogeneous:

GlueHostProcessorOtherDescription: Cores=5.0502,Benchmark=14.5626-HEP-SPEC06

Solution

Run the benchmark (if applicable) and define a YAIM site-info.def variable in the corresponding format:

CE_OTHERDESCR="Cores=N.M,Benchmark=X.Y-HEP-SPEC06"

or just

CE_OTHERDESCR="Cores=N.M"