This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Performance Assurance for Servers
TrueSight Capacity Optimization 11.3.01, 11.0, 10.x
In TSCO data isn't being collected for several metric groups and the [hostname]-bgscollect-noInstance.log, [hostname]-bgsagent_6767.log, and the UCM Status Reports indicate that groups are in ACCOUNT_UNAUTHORIZED state and not being collected.
The "Setting status for [metric group] to ACCOUNT_UNAUTHORIZED" messages indicate the collector is failing to collect data due to a permissions problem. Errors can be seen in the $BEST1_HOME/bgs/log/[nodename]-bgscollect-noInstance.log file on the node that is failing to collect data similar to the following:
Further down in the log file, there are authorization errors for every metric group:
Tue Oct 25 12:25:59 2016 bgscollect (17182) Error in [group]: Privilege::Manager::set: invalid EUID: Not owner
- TrueSight Capacity Optimization Agent 11.3.01, 11.0 10.x
- BMC Performance Assurance for Virtual Servers 9.5, 9.0, 7.5.10, 7.5.00, 7.4.10, 7.4.00, 7.3.00, 7.2.10, 7.2.00
- BMC Performance Assurance for Servers 9.5, 9.0, 7.5.10, 7.5.00, 7.4.10, 7.4.00, 7.3.00, 7.2.10, 7.2.00
The most common cause of the problem is that the TSCO Agent bgscollect binary is not owned by root, setuid root.
That can typically be most easily seen in the $BEST1_HOME/bgs/log/[hostname]-bgscollect-noInstance.log file:
If the permissions on the file are not '-r-sr-sr-x' or the owner of the file is not 'root' then the best way to resolve this problem is to re-run the [Installation Directory]/b1configVVVVV.sh script (where VVVVV is the product version, such as 11500) as root. This will correct the permissions of the bgscollect binary and correct any other permissions problem that might exist with the key binaries in the Perform installation.
# ./b1configVVVV.sh (Where VVVVV is the Agent version (i.e. b1config11500.sh)
Alternately, if you don't want to re-run the b1configVVVVV.sh script or the problem still persists, other possible causes and solutions are discussed below.
> ls -la bgscollect
-r-sr-sr-x 1 root root 2367640 Apr 22 12:32 bgscollect
If bgscollect is not owned by root and the permissions are not set properly, run the following commands:
> chgrp root bgscollect
> chmod 6555 bgscollect
You can also see the permissions of the bgscollect binary in the $BEST1_HOME/bgs/log/[hostname]-bgscollect-noInstance.log file:
If the filesystem where Perform is installed has the "nosuid" option set the collector will fail to gather data. Change the "nosuid" to "suid" for the Perform filesystem, and retry the data collection.
For example, here is the /etc/mnttab entry for a Perform file system where the nosuid flag has been specified:
To address that issue stop and restart the Perform Agent.
To stop the bgsagent run the command:
Wait about 10 seconds, and then check 'ps' output to ensure the bgsagent
and bgscollect processes are not running.
To restart the Perform Agent:
Additional Log Messages
The following message will also be generated to the $BEST1_HOME/bgs/log/[hostname]-bgsagent_6767.log:
- TrueSight Capacity Optimization
- BMC Performance Assurance for Servers