is a tool to validate GLUE 1 and GLUE 2 information published in the BDII. It also validates GLUE 2 information against the
.
.
In case you want to report an incident or you need help for glue-validator errors, please use
in CC.
The tables in the following sections contain tips on what can be done to get rid of the corresponding error, warning or info messages. Tips are classified in:
The Information System team is working very closely with middleware developers to fix bugs in the information providers. This activity is tracked
. Sys admins should not be bothered by information provider errors. The glue-validator contains an option called
to be able to exclude tests for attributes that are known to be wrongly published by the information providers.
A list of known issues is available in glue-validator >= 2.0.19. The relevant known issues are marked as
column in the tables below.
Please, note that computing related attributes are still under investigation and new known issues may be added in the nest version of glue-validator that will be validated by EGI to become a production Nagios probe.
There is a general type checking test performed by the glue-validator. This test is not done per attribute but it's the same test for all attributes. For this reason, even if a type automatically published by any of the information providers is wrong, it cannot be included in the known issues, because removing the type checking test would imply removing it for all attributes.
For the type errors, the sys admin will have to look into more details to the glue-validator output to understand what it is actually wrong. In particular, the following attributes can be manually configured by the sys admin and in case their type is wrong, they should be fixed in the site configuration:
For more details on the types defined in the EGI profile implementation of the glue-validator, please check:
Error message number |
Description |
Associated test |
Tips |
Known Issues |
E001 |
Creation time in the future |
test_GLUE2EntityCreationTime_OK |
Site misconfiguration: The test fails when the published time is two minutes more than the time of the machine where the test is run. Check the times in your machines to make sure they are correct |
NO |
E002 |
Obsolete entry |
test_GLUE2EntityValidity_OK |
Site misconfiguration: For non static entries (static entries come from static LDIF files and have no GLUE2EntityValidity published) this could be related to BUG:101237 . Update the bdii to version >= 5.2.20 to get rid of this bug |
NO |
E003 |
Wrong share percentage |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: The Share information is defined in the YAIM variable CE_CAPABILITY . Check the YAIM guide for more details on how to define this variable. The percentage for a share should be > 0 and < 100. Make sure the percentages are correctly defined in CE_CAPABILITY |
NO |
E004 |
VO appears more than once in share |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: The Share information is defined in the YAIM variable CE_CAPABILITY . Check the YAIM guide for more details on how to define this variable. Make sure a VO appears only once in CE_CAPABILITY |
NO |
E005 |
Wrong share format |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: The Share information is defined in the YAIM variable CE_CAPABILITY . Check the YAIM guide for more details on how to define this variable. Make sure your variable syntax is correct |
NO |
E006 |
Wrong attribute format |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: GLUE2EntityOtherInfo is an attribute published by both information providers in an automatic way, and values taken from the site configuration. If you get this error, please check exactly which information is wrong, review your site configuration if applicable or otherwise report it in GGUS and put project-grid-info-support@cern.ch in CC |
NO |
E007 |
Total published shares > 100% |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: The Share information is defined in the YAIM variable CE_CAPABILITY . Check the YAIM guide for more details on how to define this variable. Make sure all the share percentages defined in this variable sum up <= 100 |
NO |
E008 |
Longitude out of range |
test_GLUE2LocationLongitude_OK |
Site misconfiguration: The longitude information is defined in the YAIM variable SITE_LONG . Make sure the longitude is withing the range [-180,180] |
NO |
E009 |
Latitude out of range |
test_GLUE2LocationLatitude_OK |
Site misconfiguration: The longitude information is defined in the YAIM variable SITE_LAT . Make sure the longitude is withing the range [-90,90] |
NO |
E010 |
Start time in the future |
test_GLUE2EndpointStartTime_OK |
Site misconfiguration: The test fails when the published time is two minutes more than the time of the machine where the test is run. Check the time in your machines to make sure they are correct |
NO |
E011 |
Downtime announcement in the future |
test_GLUE2EndpointDowntimeAnnounce_OK |
This attribute currently publishes no .This attribute is not used at the moment since downtimes are currently taken from GOCDB. This test is for the time being included in the Known Issues . |
YES |
E012 |
Downtime start time is older than end time |
test_GLUE2EndpointDowntimeStart_OK |
Not published. This test is for the time being included in the Known Issues . |
YES |
E013 |
Downtime end time is published without a start time |
test_GLUE2EndpointDowntimeEnd_OK |
E014 |
Incoherent number of total capacity |
test_GLUE2StorageServiceCapacityTotalSize_OK |
SE bug: It checks whether this attribute matches the sum of total capacity in the different capacity states |
YES |
E015 |
Incoherent attribute range |
test_GLUE2StorageServiceCapacityFreeSize_OK |
SE bug: It checks whether the free capacity is lower than the total capacity |
YES |
E016 |
Incoherent attribute range |
test_GLUE2StorageServiceCapacityUsedSize_OK |
SE bug: It checks whether the used capacity is lower than the total capacity |
YES |
E017 |
Incoherent attribute range |
test_GLUE2StorageServiceCapacityReservedSize_OK |
SE bug: It checks whether the reserved capacity is lower than the total capacity |
YES |
E018 |
Incoherent number of total share capacity |
test_GLUE2StorageShareCapacityTotalSize_OK |
SE bug: It checks whether this attribute matches the sum of total share capacity in the different share capacity states |
YES |
E019 |
Incoherent attribute range |
test_GLUE2StorageShareCapacityFreeSize_OK |
SE bug: It checks whether the free share capacity is lower than the total share capacity |
YES |
E020 |
Incoherent attribute range |
test_GLUE2StorageShareCapacityUsedSize_OK |
SE bug: It checks whether the used share capacity is lower than the total share capacity |
YES |
E021 |
The object class is not valid |
test_object_class |
BDII bug The LDAP tree is built automatically by the different information providers |
NO |
E022 |
Default value published |
test_GLUE2ComputingShareWaitingJobs_default |
Site misconfiguration: It checks whether a default value of 444444 is published. Check 444444 waiting jobs manual for more details on how to fix this problem |
NO |
E023 |
Default value published |
test_GLUE2ComputingShareEstimatedAverageWaitingTime_default |
Site misconfiguration: It checks whether a default value of 2146660842 is published. This attribute is automatically calculated by the dynamic scheduler information provider and relies on the underlying batch system configuration. Please, check the batch system configuration and make sure everything is properly defined. |
NO |
E024 |
Default value published |
test_GLUE2ComputingShareEstimatedWorstWaitingTime_default |
E025 |
GLUE Schema object hierarchy violation |
test_mandatory_object_class |
NEW as of glue-validator 2.0.24 Site misconfiguration : It checks whether all mandatory object Classes are present. If this is not the case, for YAIM configurations, make sure no error is reported and the configuration run fine. Otherwise, open a GGUS ticket for further support from the Information System team. |
NO |
E026 |
Domain Foreign Key not matching GLUE2DomainID in the dn |
DomainForeignKey attribute |
NEW as of glue-validator 2.0.24 Site misconfiguration : it checks whether the Domain ID specified in the DN matches the domain foreign key attributes present in the DN |
There is a known issue in StoRM info provider (GGUS:108556 ) publishing this attribute incorrectly. For this reason, in version glue-validator 2.0.25, this test is not executed for StoRM services |
Warning message number |
Description |
Associated test |
Comments |
Known Issues |
W001 |
Creation time more than one year old |
test_GLUE2EntityCreationTime_OK |
See the comments in E002 |
NO |
W002 |
GLUE2EntityValidity published when GLUE2EntityCreationTime is not published |
test_GLUE2EntityValidity_OK |
BDII bug: information providers may be wrong |
NO |
W003 |
Unknown profile name |
test_GLUE2EntityOtherInfo_OK |
BDII bug: value automatically generated |
NO |
W004 |
Incorrect profile version |
test_GLUE2EntityOtherInfo_OK |
BDII bug: value automatically generated |
NO |
W005 |
Incoherent number of total jobs |
test_GLUE2ComputingServiceTotalJobs_OK |
CE bug: It checks whether this attribute matches the sum of total jobs in the different job states |
NO |
W006 |
Start time more than two years old |
test_GLUE2EndpointStartTime_OK |
Site misconfiguration: services that run for two years with no upgrade or restart are very uncommon. The site should check why this could be the case |
NO |
W007 |
Downtime announce more than one year old |
test_GLUE2EndpointDowntimeAnnounce_OK |
Downtime attributes are either not published or published but not used at the moment since downtimes are currently taken from GOCDB. These tests are for the time being included in the Known Issues . |
YES |
W008 |
Downtime announcement with no Downtime start published |
test_GLUE2EndpointDowntimeAnnounce_checkStart |
W009 |
Downtime start time is scheduled more than one year ahead |
test_GLUE2EndpointDowntimeStart_OK |
W010 |
Downtime start time more than one year old |
test_GLUE2EndpointDowntimeStart_OK |
W011 |
Downtime end time is scheduled more than one year ahead |
test_GLUE2EndpointDowntimeEnd_OK |
W012 |
Downtime end time is more than one week old |
test_GLUE2EndpointDowntimeEnd_OK |
W013 |
Incoherent number of total jobs |
test_GLUE2ComputingEndpointTotalJobs_OK |
CE bug: It checks whether this attribute matches the sum of total jobs in the different job states |
NO |
W014 |
Incoherent attribute range |
test_GLUE2ComputingShareMinWallTime_OK |
Site misconfiguration: It checks whether the minimum wall time is lower than the maximum wall time. Check your batch system configuration settings |
NO |
W015 |
Attribute out of predefined range |
test_GLUE2ComputingShareDefaultWallTime_MaxRange |
Site misconfiguration: It checks whether the default wall time is lower or equal than the maximum wall time. Check your batch system configuration settings |
NO |
W016 |
Attribute out of predefined range |
test_GLUE2ComputingShareDefaultWallTime_MinRange |
Site misconfiguration: It checks whether the default wall time is higher than the minimum wall time. Check your batch system configuration settings |
NO |
W017 |
Incoherent attribute range |
test_GLUE2ComputingShareMinCPUTime_OK |
Site misconfiguration: It checks whether the minimum CPU time is lower or equal than the maximum CPU time. Check your batch system configuration settings |
NO |
W018 |
Attribute out of predefined range |
test_GLUE2ComputingShareDefaultCPUTime_MaxRange |
Site misconfiguration: It checks whether the default CPU time is lower or equal than the maximum CPU time. Check your batch system configuration settings |
NO |
W019 |
Attribute out of predefined range |
test_GLUE2ComputingShareDefaultCPUTime_MinRange |
Site misconfiguration: It checks whether the default CPU time is higher than the minimum CPU time. Check your batch system configuration settings |
NO |
W020 |
Number of total jobs is zero |
test_GLUE2ComputingShareMaxTotalJobs_zero |
Site misconfiguration: It checks whether the maximum number of total jobs is zero. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
W021 |
Attribute out of predefined range |
test_GLUE2ComputingShareMaxTotalJobs_OK |
Site misconfiguration: It checks whether the maximum total jobs is higher than the maximum running jobs or the maximum waiting jobs. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
W022 |
Number of jobs is zero |
test_GLUE2ComputingShareMaxUserRunningJobs_zero |
Site misconfiguration: It checks whether the maximum number of user running jobs is zero. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
W023 |
Incoherent attribute range |
test_GLUE2ComputingShareMaxUserRunningJobs_OK |
Site misconfiguration: it checks whether the maximum user running jobs is lower than the maximum running jobs. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
W024 |
Number of maximum slots per job is zero |
test_GLUE2ComputingShareMaxSlotsPerJob_zero |
Site misconfiguration: It checks whether the maximum slots per jobs is zero. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
|
Incoherent number of total jobs |
test_GLUE2ComputingShareTotalJobs_OK |
Site misconfiguration: It checks whether this attribute matches the sum of total jobs in the different job states. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. Note that you may get this warning if you get E022. Fix E022 first |
NO |
W026 |
Memory lower than 100 MB |
test_GLUE2ComputingShareMaxMainMemory_MinRange |
Site misconfiguration: It checks whether the maximum main memory is less or equal than 100MB. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
W027 |
Incoherent attribute range |
test_GLUE2ComputingShareGuaranteedMainMemory_MinRange |
Site misconfiguration: It checks whether the guaranteed main memory is higher than the maximum main memory. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
W028 |
Incoherent attribute range |
test_GLUE2ComputingShareMaxVirtualMemory_MinRange |
Site misconfiguration: It checks whether the maximum virtual memory is less than the maximum main memory. It uses the underlying batch system configuration. Make sure it is correct and this value is defined. |
NO |
W029 |
Incoherent attribute range |
test_GLUE2ComputingShareGuaranteedVirtualMemory_MinRange |
Site misconfiguration: It checks whether the guaranteed virtual memory is higher than the maximum virtual memory. Make sure it is correct and this value is defined. |
NO |
W030 |
Incoherent attribute range |
test_GLUE2ComputingManagerTotalPhysicalCPUs_OK |
CE bug: Note that this is currently not published by the CREAM CE but it is a mandatory attribute. It checks whether the total physical CPUs is lower than the total logical CPUs |
NO |
W031 |
Incoherent attribute range |
test_GLUE2ComputingManagerTotalSlots_OK |
CE bug: Note that this is currently not published by the CREAM CE but it is a recommended attribute. It checks whether the total slots is higher than twice the number of logical CPUs |
NO |
W032 |
Incoherent attribute range |
test_GLUE2ComputingManagerSlotsUsedByLocalJobs_OK |
CE bug: Note that this is currently not published by the CREAM CE but it is optional attribute. It checks whether the slots used by local jobs are lower than the total number of slots |
NO |
W033 |
Incoherent attribute range |
test_GLUE2ComputingManagerSlotsUsedByGridJobs_OK |
CE bug: Note that this is currently not published by the CREAM CE but it is a recommended attribute. It checks whether the slots used by grid jobs are lower than the total number of slots |
NO |
W034 |
Mandatory attribute not present |
test_mandatory_attributes |
BDII bug: Information providers may be wrong |
YES |
W035 |
Undesirable attribute is present |
test_mandatory_attributes |
BDII bug: Information providers may be wrong |
YES |
W036 |
Single valued attribute with more than one value |
test_single_valued |
BDII bug: Information providers may be wrong |
NO |
W037 |
Wrong type |
test_data_types |
BDII bug: Information providers may be wrong |
YES |
W038 |
Empty attribute |
test_empty_attributes |
Site misconfiguration: Review your configuration and make sure all the necessary variables are defined. |
NO |
W039 |
Wrong Service ID starting with _ |
test_GLUE2ServiceID_OK |
Site misconfiguration: This is a known issue with the service information provider fixed in BUG:101562 . Please, upgrade to the latest EMI version. |
NO |
W040 |
Wrong Endpoint ID starting with _ |
test_GLUE2EndpointID_ OK |
W041 |
Rpm used to publish implementation version does not exist |
test_GLUE2EndpointImplementationVersion_OK |
BDII bug: This is due to the fact that the service information provider tries to find the version of an rpm that does not longer exist. |
YES |
W042 |
Wrong platform type |
test_GLUE2ExecutionEnvironmentPlatform_OK |
Site misconfiguration: The platform is defined in the YAIM variable CE_OS_ARCH . Check the YAIM guide for more details on how to define this variable and make sure it matches the Platform type |
NO |
W043 |
Wrong OS family |
test_GLUE2ExecutionEnvironmentOSFamily_OK |
CE bug: The OS family is defined in the YAIM variable CE_OS_FAMILY . Check the YAIM guide for more details on how to define this variable. This variable is currently defined by the CREAM yaim module and the default is linux . If you manually change this variable, make sure it matches the OS Family type |
NO |
W044 |
Wrong OS name |
test_GLUE2ExecutionEnvironmentOSName_OK |
Site misconfiguration: The OS name is defined in the YAIM variable CE_OS . Check the YAIM guide for more details on how to define this variable. Follow the How to publish OS name - EGI guidelines for more details |
NO |
Info message number |
Description |
Associated test |
Comments |
Known Issues |
I001 |
Unknown Grid Infrastructure name |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: check How to publish site information for more details |
NO |
I002 |
Unknown configuration tool |
test_GLUE2EntityOtherInfo_OK |
NO |
I003 |
Unknown EGI NGI |
test_GLUE2EntityOtherInfo_OK |
NO |
I004 |
Incorrect blog URL |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: Check that you have provided a correct URL |
NO |
I005 |
Incorrect icon URL |
test_GLUE2EntityOtherInfo_OK |
NO |
I006 |
Unknown WLCG Tier |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: Check How to publish site information for more details |
NO |
I007 |
Unknown WLCG Name |
test_GLUE2EntityOtherInfo_OK |
DEPRECATED as of glue-validator 2.0.23 |
NO |
I008 |
Incorrect icon WLCG name icon URL |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: Check that you have provided a correct URL |
NO |
I009 |
Unknown middleware name |
test_GLUE2EntityOtherInfo_OK |
BDII bug: Value automatically generated |
NO |
I010 |
Incorrect middleware version |
test_GLUE2EntityOtherInfo_OK |
BDII bug: Value automatically generated. Note there is a known issue in FTS tracked in 704 . Despite of this, this test has not been marked for known issues as it affects all services. Dismiss this error if it applies to FTS. |
I011 |
Incorrect DN syntax |
test_GLUE2EntityOtherInfo_OK |
BDII bug: It checks the Host DN syntax. Value automatically generated |
NO |
I012 |
Unknown VO name in share |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: Check that the VO name is correct |
NO |
I013 |
Unknown benchmark name in share |
test_GLUE2EntityOtherInfo_OK |
Site misconfiguration: Check that the benchmark name is HEP-SPEC06 |
NO |
I014 |
Number of jobs higher than 1 million |
test_GLUE2ComputingServiceRunningJobs_OK |
CE bug: this is a recommended attribute that it is currently not published by the CREAM CE |
NO |
I015 |
Number of jobs higher than 1 million |
test_GLUE2ComputingServiceWaitingJobs_OK |
I016 |
Number of jobs higher than 1 million |
test_GLUE2ComputingServiceStagingJobs_OK |
I017 |
Number of jobs higher than 1 million |
test_GLUE2ComputingServiceSuspendedJobs_OK |
I018 |
Number of jobs higher than 1 million |
test_GLUE2ComputingServicePreLRMSWaitingJobs_OK |
I019 |
Issuer CA published as 'unknown' |
test_GLUE2EndpointIssuerCA_OK |
I020 |
Trusted CA published as 'unknown' |
test_GLUE2EndpointTrustedCA_OK |
I021 |
Number of jobs higher than 1 million |
test_GLUE2ComputingEndpointRunningJobs_OK |
CE bug: this is an optional attribute that it is currently not published by the CREAM CE |
NO |
I022 |
Number of jobs higher than 1 million |
test_GLUE2ComputingEndpointWaitingJobs_OK |
I023 |
Number of jobs higher than 1 million |
test_GLUE2ComputingEndpointStagingJobs_OK |
I024 |
Number of jobs higher than 1 million |
test_GLUE2ComputingEndpointSuspendedJobs_OK |
I025 |
Number of jobs higher than 1 million |
test_GLUE2ComputingEndpointPreLRMSWaitingJobs_OK |
I026 |
Default value published |
test_GLUE2ComputingShareMaxWallTime_OK |
Site misconfiguration: It checks whether it publishes a default value of 999999999. This value is OK if you do not want to define a limit for your queues and therefore you can ignore this message. Otherwise, if you want to define a limit, check your batch system configuration settings to make sure a proper value is defined. |
NO |
I027 |
Default value published |
test_GLUE2ComputingShareMaxMultiSlotWallTime_OK |
I028 |
Default value published |
test_GLUE2ComputingShareDefaultWallTime_OK |
I029 |
Default value published |
test_GLUE2ComputingShareMaxCPUTime_OK |
I030 |
Default value published |
test_GLUE2ComputingShareMaxTotalCPUTime_OK |
I031 |
Default value published |
test_GLUE2ComputingShareDefaultCPUTime_OK |
I032 |
Default value published |
test_GLUE2ComputingShareMaxTotalJobs_default |
I033 |
Default value published |
test_GLUE2ComputingShareMaxRunningJobs_OK |
I034 |
Default value published |
test_GLUE2ComputingShareMaxWaitingJobs_OK |
I035 |
Number of jobs higher than 1 million |
test_GLUE2ComputingShareRunningJobs_OK |
Site misconfiguration: It checks jobs and memory limits. If your site publishes values beyond these limits, check whether it is actually correct or not. The glue-validator performs these sanity checks but maybe values are correct so you can ignore this message. |
NO |
I036 |
Number of jobs higher than 1 million |
test_GLUE2ComputingShareLocalRunningJobs_OK |
I037 |
Number of jobs higher than 1 million |
test_GLUE2ComputingShareWaitingJobs_OK |
I038 |
Number of jobs higher than 1 million |
test_GLUE2ComputingShareLocalWaitingJobs_OK |
I039 |
Number of jobs higher than 1 million |
test_GLUE2ComputingShareSuspendedJobs_OK |
I040 |
Number of jobs higher than 1 million |
test_GLUE2ComputingShareLocalSuspendedJobs_OK |
I041 |
Number of jobs higher than 1 million |
test_GLUE2ComputingShareStagingJobs_OK |
I042 |
Number of jobs higher than 1 million |
test_GLUE2ComputingSharePreLRMSWaitingJobs_OK |
I043 |
Memory higher than 100,000 MB |
test_GLUE2ComputingShareMaxMainMemory_MaxRange |
I044 |
Memory higher than 100,000 MB |
test_GLUE2ComputingShareGuaranteedMainMemory_MaxRange |
I045 |
Memory higher than 100,000 MB |
test_GLUE2ComputingShareMaxVirtualMemory_MaxRange |
I046 |
Number of seconds higher than 1 million |
test_GLUE2ComputingShareEstimatedAverageWaitingTime_OK |
Site misconfiguration: This value is automatically calculated by the dynamic scheduler information provider using the underlying batch system configuration. The glue-validator performs these sanity checks but maybe values are correct so you can ignore this message. Ignore these message also if you are getting E023 or E024. |
NO |
I047 |
Number of seconds higher than 1 million |
test_GLUE2ComputingShareEstimatedWorstWaitingTime_OK |
NO |
I048 |
Number of slots higher than 1 million |
test_GLUE2ComputingShareFreeSlots_OK |
I049 |
Number of slots higher than 1 million |
test_GLUE2ComputingShareUsedSlots_OK |
CE bug: this is a mandatory attribute that it is currently not published by the CREAM CE |
NO |
I050 |
Number of slots higher than 1 million |
test_GLUE2ComputingShareRequestedSlots_OK |
I051 |
Number of logical CPUs lower than 10 |
test_GLUE2ComputingManagerTotalLogicalCPUs_MinRange |
CE bug: this is a mandatory attribute that it is currently not published by the CREAM CE |
NO |
I052 |
Number of logical CPUs greater than 1 million |
test_GLUE2ComputingManagerTotalLogicalCPUs_MaxRange |
I053 |
Number of physical CPUs lower than 10 |
test_GLUE2ComputingManagerTotalPhysicalCPUs_MinRange |
I054 |
Number of logical CPUs greater than 1 million |
test_GLUE2ComputingManagerTotalPhysicalCPUs_MaxRange |
I055 |
Number of total slots lower than 10 |
test_GLUE2ComputingManagerTotalSlots_MinRange |
CE bug: this is a recommended attribute that it is currently not published by the CREAM CE |
NO |
I056 |
Number of total slots greater than 1 million |
test_GLUE2ComputingManagerTotalSlots_MaxRange |
I057 |
Total working area greater than 1 million GB |
test_GLUE2ComputingManagerWorkingAreaTotal_OK |
CE bug: this is a desirable attribute that it is currently not published by the CREAM CE |
NO |
I058 |
Free working area greater than 1 million GB |
test_GLUE2ComputingManagerWorkingAreaFree_OK |
I059 |
Multi slot working area greater than 1 million GB |
test_GLUE2ComputingManagerWorkingAreaMultiSlotTotal_OK |
I060 |
Multi slot free working area greater than 1 million GB |
test_GLUE2ComputingManagerWorkingAreaMultiSlotFree_OK |
I061 |
Total cache greater than 1 million GB |
test_GLUE2ComputingManagerCacheTotal_OK |
I062 |
Free cache greater than 1 million GB |
test_GLUE2ComputingManagerCacheFree_OK |
I063 |
Total instances less than 10 |
test_GLUE2ExecutionEnvironmentTotalInstances_MinRange |
CE bug: It checks whether the total instances are less than 10. Total instances are calculated with YAIM variables in the following way: CE_LOGCPU/CE_SMPSIZE . However CE_LOGCPU has a different meaning in GLUE 1 and GLUE 2 and the same variable is used to publish both GLUE 1 and GLUE 2. |
YES |
I064 |
Total instances more than 1 million |
test_GLUE2ExecutionEnvironmentTotalInstances_MaxRange |
I065 |
Incoherent attribute range |
test_GLUE2ExecutionEnvironmentUsedInstances_OK |
CE bug: this is an optional attribute that it is currently not published by the CREAM CE |
NO |
I066 |
Incoherent attribute range |
test_GLUE2ExecutionEnvironmentUnavailableInstances_OK |
I067 |
Number of physical CPUs greater than 10 |
test_GLUE2ExecutionEnvironmentPhysicalCPUs_MaxRange |
CE bug: Physical CPUs are defined using the YAIM variable CE_PHYSCPU . However this variable has a different meaning in GLUE 1 and GLUE 2 and the same variable is used to publish both GLUE 1 and GLUE 2. |
YES |
I068 |
Number of logical CPUs greater than 1000 |
test_GLUE2ExecutionEnvironmentLogicalCPUs_MaxRange |
CE bug: Logical CPUs are defined using the YAIM variable CE_LOGCPU . However this variable has a different meaning in GLUE 1 and GLUE 2 and the same variable is used to publish both GLUE 1 and GLUE 2. |
YES |
I069 |
CPU clock speed greater than 1000 |
test_GLUE2ExecutionEnvironmentCPUClockSpeed_MaxRange |
Site misconfiguration: CPU lock Speed defined using the YAIM variable CE_CPU_SPEED . Check the YAIM guide for more details on how to define this variable. Make sure this variable actually reflects the right CPU speed |
NO |
I070 |
CPU clock speed less than 100 |
test_GLUE2ExecutionEnvironmentCPUClockSpeed_MinRange |
I071 |
CPU time scaling factor greater than 1 |
test_GLUE2ExecutionEnvironmentCPUTimeScalingFactor_MaxRange |
CE bug: this value is currently hardcoded by the CREAM information providers to 1 |
YES |
I072 |
CPU time scaling factor less than 0.1 |
test_GLUE2ExecutionEnvironmentCPUTimeScalingFactor_MinRange |
I073 |
Wall time scaling factor greater than 1 |
test_GLUE2ExecutionEnvironmentWallTimeScalingFactor_MaxRange |
CE bug: this is a mandatory attribute that it is currently not published by the CREAM CE |
NO |
I074 |
Wall time scaling factor less than 0.1 |
test_GLUE2ExecutionEnvironmentWallTimeScalingFactor_MinRange |
I075 |
Main memory size greater than 1 million MB |
test_GLUE2ExecutionEnvironmentMainMemorySize_MaxRange |
Site misconfiguration: The RAM size is defined using the YAIM variable CE_MINPHYSMEM . Check the YAIM guide for more details on how to define this variable. Make sure this variable actually reflects the right memory size |
NO |
I076 |
Main memory size less than 100 MB |
test_GLUE2ExecutionEnvironmentMainMemorySize_MinRange |
I077 |
Virtual memory size greater than 1 million MB |
test_GLUE2ExecutionEnvironmentVirtualMemorySize_MaxRange |
Site misconfiguration: The virtual memory size is defined using the YAIM variable CE_MINVIRTMEM . Check the YAIM guide for more details on how to define this variable. Make sure this variable actually reflects the right virtual memory size |
NO |
I078 |
Virtual memory size less than 100 MB |
test_GLUE2ExecutionEnvironmentVirtualMemorySize_MinRange |
I079 |
Removal date in the past |
test_GLUE2ApplicationEnvironmentRemovalDate_OK |
CE bug: this is an optional attribute that it is currently not published by the CREAM CE |
NO |
I080 |
Number of maximum slots is zero |
test_GLUE2ApplicationEnvironmentMaxSlots_OK |
I081 |
Number of maximum jobs is zero |
test_GLUE2ApplicationEnvironmentMaxJobs_OK |
I082 |
Number of maximum user seats is zero |
test_GLUE2ApplicationEnvironmentMaxUserSeats_OK |
I083 |
Incoherent attribute range |
test_GLUE2ApplicationEnvironmentFreeSlots_OK |
I084 |
Incoherent attribute range |
test_GLUE2ApplicationEnvironmentFreeJobs_OK |
I085 |
Incoherent attribute range |
test_GLUE2ApplicationEnvironmentFreeUserSeats_OK |
I086 |
Total capacity size less than 1000 GB |
test_GLUE2StorageServiceCapacityTotalSize_MinRange |
Site configuration : This value is automatically generated by the storage services information providers. The glue-validator performs these sanity checks but maybe values are correct so you can ignore this message |
NO |
I087 |
Total capacity size greater than 1 billion GB |
test_GLUE2StorageServiceCapacityTotalSize_MaxRange |
I088 |
Access latency is 'offline' |
test_GLUE2StorageShareAccessLatency_OK |
I089 |
Default life time less than 100000 seconds |
test_GLUE2StorageShareDefaultLifeTime_OK |
SE bug: attribute either not published by most storage services or wrongly hardcoded to -1 |
YES |
I090 |
Maximum life time less than 100000 seconds |
test_GLUE2StorageShareMaximumLifeTime_OK |
I091 |
Total share capacity size less than 1000 GB |
test_GLUE2StorageShareCapacityTotalSize_MinRange |
I092 |
Total share capacity size greater than 1 billion GB |
test_GLUE2StorageShareCapacityTotalSize_MaxRange |
I093 |
Bandwidth less than 100 |
test_GLUE2ToComputingServiceBandwidth_MinRange |
SE bug : this is a mandatory attribute that it is currently not published by the storage services |
NO |
I094 |
Bandwidth greater than 100000 |
test_GLUE2ToComputingServiceBandwidth_MaxRange |
I095 |
Recommended attribute not present |
test_mandatory_attributes |
BDII bug: Information providers may be wrong |
YES |
I096 |
Default value published |
test_GLUE2ComputingShareMaxMainMemory_Default |
Site misconfiguration: It checks whether it publishes a default value of 444444. This value is OK if you do not want to define a limit for memory and therefore you can ignore this message. Otherwise, if you want to define a limit, make sure a proper value is defined in the batch system configuration |
NO |
I097 |
Default value published |
test_GLUE2ComputingShareMaxVirtualMemory_Default |