- Welcome BMC Customer Support Site Guest User
Knowledge Article
TrueSight Capacity Optimization (TSCO) Agent data collection is never started with error "ERROR: No Metric Groups Enabled" even though the computer initially seems to accept the collection request
The remote node seems to accept TSCO Agent data collection requests but then data collection is never started. The TSCO Agent log contains the error "ERROR: No Metric Groups Enabled".
TrueSight Capacity Optimization
TrueSight Capacity Optimization 20.02, 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0 ; BMC Performance Assurance 9.5
The 'ERROR: No Metric Groups Enabled' message in the TrueSight Capacity Optimization (TSCO) agent log means that the TSCO Agent received the request but it wasn't able to determine which groups should be collected for that type of request. Since this is a default system data collection request that usually means that the Repository.loc file is missing or contains a bad path or that somehow the Repository.cfg file has been removed, become inaccessible, or corrupted.
|
Any underlying data collection problem that causes the collection request for all metric groups to be rejected will result in the error 46: 'Collect Request - No Metric groups enabled' collection error status. This means that for this error in particular it is often necessary to review the TSCO Collector and TSCO Agent log files to see if there is a more specific error message being reported. The most common problem is that the $BEST1_HOME/bgs/mgroup/Repository.loc file is missing or doesn't contain a valid default data repository path. Without a valid Repository.loc file data collection will fail. Information on that is documented in KA 000299047: TrueSight Capacity Optimization (TSCO) Agent error: MrHistory::populate - ERROR: Error accessing repository root directory /usr/local/bmc/perform/history (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000299047)
(B) Invalid or unreadable Repository.cfg file Another possible problem is generally associated with these errors in the $BEST1_HOME/bgs/log/[hostname]-bgsagent_6767.log: Perform Agent (17799) Error reading: /usr/adm/best1_V.V.VV/bgs/mgroup/Repository.cfg (notReadable)
Perform Agent (17799) Collect request (Mar-19-2007.16.29) ERROR: No Metric Groups Enabled That generally means either:
If the Repository.cfg file is owned by root, make it owned by the TSCO Agent Installation Owner (the user that owns the $BEST1_HOME/bgs/bin/bgsagent file on disk) and then restart the TSCO agent. If the file doesn't exist it will be necessary to obtain a copy of it from another machine running the same version of TSCO Agent and the same OS version. (C) The Collector OS Support Check is failing When the Operating System of the base OS doesn't match an Operating System version supported by the collector the collection of all of the metric groups will fail with "ERROR: UDR request terminated - collection halted - Operating System mismatch". Both the TSCO Collector and the TSCO Agent logs will report this error but it isn't propagated as the final collection error visible in the Gateway Manager or other reporting. This is because the OS support check failure causes all of the metric groups to stop collecting which is the reported as the Error 46: 'Collect Request - No Metric groups enabled'. See KA 000293396: TrueSight Capacity Optimization (TSCO) data collection fails with error, "Operating System Mismatch - SYSTEM - Collector Information" (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000293396) (D) On Windows, the OS directory version of the MetricTable.mgt is corrupt or missing On Microsoft Windows, you may see errors like these in the TSCO agent log: Tue Nov 04 10:08:30 2008 Perform Agent (1440:3572) Collect Request - Error: Core group 'NT Collector Information Configuration' not found
Tue Nov 04 10:08:30 2008 Perform Agent (1440:3572) Collect Request - Error: Core group 'NT System Configuration' not found Tue Nov 04 10:08:30 2008 Perform Agent (1440:3572) Collect Request - Error: Core group 'NT Physical Disk Configuration' not found <-- cut --> Tue Nov 04 10:08:30 2008 Perform Agent (1440:3572) Collect Request - Error: no core groups specified for request These error may indicate that the %BEST1_COLLECT_HOME%\bgs\mgroup\[OS]\MetricTable.mgt file has been corrupted, truncated, or removed. The "Collect Request - Error: Core group '[group]' not found" messages indicates that the group specified is listed in the %BEST1_COLLECT_HOME%\bgs\mgroup\Repository.cfg file but can't be found in the list of 'valid' groups loaded from the MetricTable.mgt file. On Microsoft Windows there is a MetricTable.mgt file exists in both the %BEST1_COLLECT_HOME%\bgs\mgroup and %BEST1_COLLECT_HOME%\bgs\mgroup\[OS] directories, but the one in the mgroup directory is basically empty, having just a 'This is a placeholder' comment, and all of the groups are listed in the [OS] level directory. Related Products:
|
Attachment(s):