TrueSight Capacity Optimization (TSCO) Agent error: MrHistory::populate - ERROR: Error accessing repository root directory /usr/local/bmc/perform/history

Manage Support IDs

Use checkboxes to 'Remove support IDs/Users' or 'Allow to create Cases'
Support IDs for BMC Customer Support Site Guest User
Profiles Which Include    Back to All Support IDs
 

Knowledge Article

TrueSight Capacity Optimization (TSCO) Agent error: MrHistory::populate - ERROR: Error accessing repository root directory /usr/local/bmc/perform/history
Error: TSCO Agent (3367080) MrHistory::populate - ERROR: Error accessing repository root directory /usr/local/bmc/perform/history
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
Although the TrueSight Capacity Optimization (TSCO) agent process (bgsagent) is running data is not being collected. There is an error towards the beginning of the [hostname]-bgsagent_6767.log file that states something like:
Perform Agent (3367080) MrHistory::populate - ERROR: Error accessing repository root directory /usr/local/bmc/perform/history

The following error may also be reported in the UDR Collection Manager (UCM) status reports on the console:
[Agent-Error] Collect Request - Agent Repository (Local Repository) does not exist
 
  • 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
  • Unix

This message means that there is a problem with the Investigate History directory specified in the $BEST1_HOME/bgs/mgroup/Repository.loc file on the TrueSight Capacity Optimization (TSCO) Agent. It is a requirement that the directory path specified in the Repository.loc file be a valid directory that is accessible by the TSCO Agent Installation Owner (the owner of the bgsagent file). If the directory specified in the Repository.loc file does not exist or is not accessible all data collection will fail on the machine.

To resolve this issue verify the path specified in the Repository.loc file to ensure that:
  1. The full path specified exists
  2. The TSCO Agent Installation Owner has full access to the directory.
To check the directory permissions it is necessary to check the permissions of all directories that make up the path. So, for the /usr/local/bmc/perform/history directory you'd want to run:
 
> ls -ld /usr
> ls -ld /usr/local
> ls -ld /usr/local/bmc
> ls -ld /usr/local/bmc/perform
> ls -ld /usr/local/bmc/perform/history

It is important that the TSCO Agent Installation Owner have read and execute permissions (either through owner, group, or world access) on all directories up to the last one. The TSCO Agent Installation Owner will need full access (rwx) to the final directory (/usr/local/bmc/perform/history in this example).

If the specified path did not exist and was created or the permissions on any component of the directory were insufficient the TSCO Agent must be restarted after making the necessary changes. The agent only checks the directory on startup.

To stop the TSCO Agent:
 
> /usr/adm/best1_default/bgs/scripts/best1agent_stop -b /usr/adm/best1_default -a

To restart the TSCO Agent:
 
> /usr/adm/best1_default/bgs/scripts/best1collect -B /usr/adm/best1_default -q

Related Products:
  1. TrueSight Capacity Optimization
  2. BMC Performance Assurance

Legacy ID:KA310041
 
NOTE: This document was originally published as Solution SLN000000174546.
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
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
Attachment(s):