Setting status for [metric group] to ACCOUNT_UNAUTHORIZED' messages exist in the BPA bgscollect log file and data is not being collected for some groups

Version 4
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Performance Assurance for Servers


    APPLIES TO:

    TrueSight Capacity Optimization 11.3.01, 11.0, 10.x



    PROBLEM:

     

       

    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:

       

    Wed Apr 23 13:59:47 2003 bgscollect (22631) Checking for platform support
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Running on SunOS 5.8 (sun4u, 64 bits)
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Collector supports SunOS 5.8 (64 bits)
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Collector support check passed
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Privileges are not possible
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Initial ids: uid = 9999, gid = 10 euid = 9999, egid = 10
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Kernel is readable to group id = 3 (requires privileges)

       

    Further down in the log file, there are authorization errors for every metric group:

       

    Wed Apr 23 13:59:47 2003 bgscollect (22631) Setting status for Disk Configuration to ACCOUNT_UNAUTHORIZED
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Setting status for Disk Ctrl Configuration to ACCOUNT_UNAUTHORIZED
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Setting status for Logical Volume Configuration to ACCOUNT_UNAUTHORIZED
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Setting status for Network Statistics to ACCOUNT_UNAUTHORIZED
    Wed Apr 23 13:59:47 2003 bgscollect (22631) Setting status for Process Statistics to ACCOUNT_UNAUTHORIZED

    You may also see errors in the log like this:

      Tue Oct 25 12:25:59 2016 bgscollect (17182) Error in [group]: Privilege::Manager::set: invalid EUID: Not owner

       
        
        NOTE: This document was originally published as Solution SLN000000144354.   
       
      
      
       
        
    • 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
    •  
      
      
       
        
    • Unix
    •  
      

     


    SOLUTION:

     

    Legacy ID:KA310090

      
       

    The most common cause of the problem is that the Capacity 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:

       

    bgscollect (27322) Installation info for ../../bin/bgscollect: 4128   -r-sr-sr-x     perform     perfgroup 2104024 Jan 12 18:18:06 2010 bgscollect

    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.  
     
    For example:  
        
       # cd /[Installation Directory]   
    # ./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.  
     
      Step 1   
          
    Check the permissions of the $BEST1_HOME/bgs/bin/bgscollect executable to make sure that it is owned by root with 6555 permissions:  
        
         > cd $BEST1_HOME/bgs/bin   
      > 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:   
         > chown root bgscollect   
      > 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:   
       Tue Feb  9 14:43:47 2010 bgscollect (5755) Installation info for ../../bin/bgscollect: 4092   -r-sr-sr-x       root       root 2094584 Jun 12 10:11:43 2008 bgscollect  
       
      Step 2 
     
    If the permissions and ownership of $BEST1_HOME/bgs/bin/bgscollect are set properly (per the instructions in Step 1) and ACCOUNT_UNAUTHORIZED errors are still being generated in the [nodename]-bgscollect-noInstance.log file, check /etc/mnttab on the node for the filesystem where the Perform product is installed. The /etc/mnttab file will have entries similar to the following:   
       /proc   /proc   proc    rw,suid,dev=2a00000     1049401868    
       
    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:   
       /dev/vx/dsk/grpspc_share_dg/perf-vol     /opt/perform    vxfs    rw,nosuid,delaylog,largefiles,cluster,ioerror=mdisable,crw,dev=4586593  1260730664  
       
      Step 3 
     
    Sometimes the permissions on bgscollect have been corrected on the file system, but the running bgscollect process was started before the bgscollect binary was made setuid root.  
     
    To address that issue stop and restart the Perform Agent.  
     
    To stop the bgsagent run the command:   
         > /usr/adm/best1_default/bgs/scripts/best1agent_stop -b /usr/adm/best1_default -a  
       
    Wait about 10 seconds, and then check 'ps' output to ensure the bgsagent  
    and bgscollect processes are not running.   
         > ps -ef | grep bgs  
       
    To restart the Perform Agent:   
         > /usr/adm/best1_default/bgs/scripts/best1collect -B /usr/adm/best1_default -q  
      
      

    Additional Log Messages

      

    The following message will also be generated to the $BEST1_HOME/bgs/log/[hostname]-bgsagent_6767.log:

      

      Perform Agent (14968) UDR Collect Request - ERROR: UDR request terminated - collection halted - Account unauthorized (hostname:noInstance:Aug-02-2006.00.05:'[group]')

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

     


    Article Number:

    000095975


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles