TSCO Capacity Agent - Perform data collection is failing and the Perform Agent log reports, "BaseQue::ReMap - Queue state left opened" for all groups

Version 3
    Share This:

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


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TSCO Capacity Agent All Versions



    PROBLEM:

     

    The Perform Collector (bgscollect) process isn't running on the machine and the Perform Agent is reporting the following set of messages for each group it attempts to register for collection:

      

      Perform Agent (801) BaseQue::ReMap - Queue state left opened
      Perform Agent (801) BaseQue::WriteGrab() ReMap() failed
      Perform Agent (801) CIQ::Insert() - WriteGrab failed
      Perform Agent (801) MrPoolEntry::Register - ERROR: Failed to insert ([GROUP]) at interval (10) in CIQ  (bgscollect:noInstance)
      Perform Agent (801) UDR History : UDR request terminated - MrPool registration failed - Collector registration failed(:noInstance:'[GROUP]')


    Another message you could find in the bgsagent log is when the collector process is failing to start:
    TrueSight Agent (29760) MrPoolEntry::Register - ERROR: Failed to start collector bgscollect with instance noInstance
    TrueSight Agent (29760) UDR History : UDR request terminated - MrPool registration failed - Collector registration faile
    d(:noInstance:'Cpu Statistics')
    TrueSight Agent (29760) BaseQue::ReMap - Queue state left opened
    TrueSight Agent (29760) BaseQue::WriteGrab() ReMap() failed
    TrueSight Agent (29760) CRQ::KeepClean - WriteGrab failed
    TrueSight Agent (29760) BaseQue::ReMap - Queue state left opened
    TrueSight Agent (29760) BaseQue::WriteGrab() ReMap() failed
    TrueSight Agent (29760) CRQ::Insert - WriteGrab failed (bgscollect:noInstance)

    All Capacity Agent versions 

     


    CAUSE:

    Shared memory segments problems or permission issues


    SOLUTION:

     

    Legacy ID:KA293666

      

    Typically, stopping and restarting the Perform Agent would cause the Collector Input Queue (CIQ) to be recreated which would fix data collection and stop these errors. However, these errors were visible in the agent log created by multiple agent PIDs indicating something more forceful was needed.

    1) Stop the running Capacity Agent instance
            >$BEST1_HOME/bgs/scripts/best1agent_stop
    2) Now that the agent and collector processes are stopped, the Perform shared memory segments can be cleared, This is done using the MrStat utility located under the $BEST1_HOME/bgs/bin directory; The following command must be run as root to be effective:
            > $BEST1_HOME/bgs/bin/MrStat -b $BEST1_HOME -k

      

    3) Now that the shared memory has been cleared, the Capacity agent and collector processes can be restarted:
         >$BEST1_HOME/bgs/scripts/best1collect -Q

    Does the Capacity Collector is properly starting now on the machine? If so, has the "BaseQue::ReMap - Queue state left opened" errors stopped?

    If that doesn't resolve the issue, try the following test:
    A) Run the following command:
         > $BEST1_HOME/bgs/bin/bgscollect -I test -m -z
    B) Let that run for a couple of minutes. Then, press CTRL-C to stop it.
    C) Send Technical Support the following:

      
       
    • The output of '$BEST1_HOME/bgs/bin/Look -b $BEST1_HOME -f'
    •  
    • The entire contents of the $BEST1_HOME/bgs/log directory
    •  
    • The output of 'ipcs -a'
    •  
    • The output of 'ipcs -l'

     


    Article Number:

    000094591


    Article Type:

    Solutions to a Product Problem



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