TSCO Gateway Manager (BPA General Manager) Error codes and remediation suggestions

Version 8
    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:

    TrueSight Capacity Optimization (Gateway Server) 10.x, 11.x



    PROBLEM:

     

    The TrueSight Capacity Optimization (TSCO) Gateway Manager and BMC Performance Assurance (BPA) General Manager reports error codes and includes a brief description of the problem. This document provides some additional information on the most common error codes and references other documents where appropriate.  These error codes are visible in the udrCollectStat command output which is the command line interface into UDR Collection Manager (UCM).

    BMC TrueSight Capacity Optimization (Gateway Server) 11.5.01, 11.5, 11.3.1, 11.3, 11.0, 10.7, 10.5, 10.3, 10.0
     

     


    SOLUTION:

     

     

      

    General Manager Error Codes

                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  
    ID: IDSeverity: SEVERITYKEYWORDDESCRIPTION 
    SOLUTION
     
    ID: 0Severity: InformationTOKNormal Operation 
    No error
     
    ID: 1Severity: ErrorALERTNOCONDITIONSNo conditions in alert 
    User Error in setting up the Investigate Alert
     
    ID: 2Severity: InformationDRILLDOWNRECEIVEDDrill down request received 
     
     
    ID: 3Severity: InformationDRILLDOWNDELETEDDrill down request cleared 
     
     
    ID: 4Severity: ErrorSELECTORBADBad selector received in message 
    User Error in setting up the Investigate DrillDown
     
    ID: 5Severity: ErrorMETRICBADInvalid metric request received 
    Most likely a mismatch between OS of agent and OS of group
     
    ID: 6Severity: ErrorPOLICYBADPolicy file does not exist 
    User removed policy file
     
    ID: 7Severity: WarningALERTFAILEDCannot reach agent for alert 
    Make sure the agent specified valid and is on the network
     
    ID: 8Severity: WarningDELETEALERTFAILEDCannot reach agent for clear 
    Make sure the agent specified valid and is on the network
     
    ID: 9Severity: WarningDELETEGRAPHFAILEDCannot reach agent to clear graph 
    Make sure the agent specified valid and is on the network
     
    ID: 10Severity: WarningSUSPENDALERTFAILEDCannot reach agent for suspend 
    Make sure the agent specified valid and is on the network
     
    ID: 11Severity: WarningRESUMEALERTFAILEDCannot reach agent for resume 
    Make sure the agent specified valid and is on the network
     
    ID: 12Severity: WarningACKALERTFAILEDCannot reach agent for acknowledge 
    Make sure the agent specified valid and is on the network
     
    ID: 13Severity: WarningGRAPHALERTFAILEDCannot reach agent for graphing 
    Make sure the agent specified valid and is on the network
     
    ID: 14Severity: WarningMGBFAILEDCannot reach agent for drill down 
    Make sure the agent specified valid and is on the network
     
    ID: 15Severity: WarningUPDATEFAILEDCannot reach agent for update 
    Make sure the agent specified valid and is on the network
     
    ID: 16Severity: ErrorOLDVERSIONAgent version too old to handle message 
    Upgrade your agent to a supported version
     
    ID: 17Severity: InformationAGENTSTOPPEDAgent has been stopped 
     
     
    ID: 18Severity: ErrorAGENTNOTSTOPPEDCannot stop Agent 
    Agent Logs will provide information about why agent could not be stopped
     
    ID: 19Severity: ErrorMAXCOLLECTRESTARTSMaximum collector restarts exceeded - no data received 
    The 'Maximum collector restarts exceeded' typically indicates that the Perform collector is crashing or unable to run on the machine. In many instances this will be due to an OS version specific problem that may be fixed in the latest agent patch set.

    Debugging steps:      
           
    1. Revew the agent logs from the remote node. Error messages associated with this problem are typically available in the [hostname]-bgscollect-noInstance.log file.
    2.      
    3. Search the knowledgebase using this error, the Perform version, the OS version and vendor, and error messages identified in the collector log
    4.      
    5. Log an issue with Technical Support including a copy of the Perform agent log files
    6.     
     
    ID: 20Severity: ErrorCOLLECTREGFAILEDCollector registration failed 
    The 'Collector registration failed' message occurs when the Perform Agent is unable register the collection request for a metric group in the Collector Input Queue (CIQ). The most common causes for this problem are:      
           
    1. The CIQ wasn't properly closed resulting in the agent encountering a 'BaseQue::ReMap - Queue state left opened' error
    2.      
    3. Shared memory has been exhausted on the machine and the Perform Agent is unable to create the CIQ
    4.     
    Typical workaround options:      
           
    1. Stop and restart the Perform Agent on the remote node.
    2.      
    3. Stop the Perform Agent, clear shared memory using the 'MrStat' command, and restart the Perform agent
    4.     
     
    ID: 21Severity: ErrorUNAUTHORIZED_MESSAGEConsole user not authorized by agent to issue request 
    This error can occur if the user making the request from the Perform console is not authorized to access the remote agent based upon the BEST1_HOME/local/setup/Authorization.cfg file on the remote agent. The most common sources of this error are a missing or corrupt Authorization.cfg file on the remote agent.

    Debugging:      
           
    1. Validate that the BEST1_HOME/local/setup/Authorization.cfg file exists on the remote agent
    2.      
    3. Validate that the Authorization.cfg file is properly configured to allow the console user to access the remote agent
    4.     
     
    ID: 22Severity: ErrorSD_COMM_ERRORService Daemon communication error 
    Make sure the agent node specified is valid, and service daemon is running.
     
    ID: 23Severity: ErrorAGENT_START_ERRORCannot start agent 
    Make sure the bgsagent executable is located in $BEST1_HOME/bgs/bin/bgsagent, additional information can be found in service daemon logs.
     
    ID: 24Severity: WarningMETRICGROUP_NOT_SUPPORTEDMetric group not supported 
    The Perform collector supports data collection for metric groups that are not available on every remote agent. For example, the 'SRM Statistics' group will only be valid on Solaris machines running the Solaris Resource Manager but when the agent receives a collection request it will attempt to enable this group on the machine. The 'Metric group not supported' message indicates that the group happens to not be supported on this particular machine. In most cases this message can be ignored.
     
    ID: 25Severity: WarningMETRIC_NOT_SUPPORTEDMetric(s) not supported 
    The version of the operating system does not support the parameter
     
    ID: 26Severity: ErrorREQUEST_NOT_SUPPORTEDRequest not supported 
    Invalid request
     
    ID: 27Severity: ErrorNO_DISK_SPACENo disk space 
    Make sure you have enough disk space

    This messsage indicates that there is no disk space available in the target directory for the UDR data.  If this error occurs during the data transfer phase that is an indication that there is insufficient disk space in the console data repository directory.
     
    ID: 28Severity: ErrorSHMEM_GEN_ERRORShared memory error 
    Unable to allocate shared memory, memory exhausted or permission issue
     
    ID: 29Severity: ErrorSEM_GEN_ERRORSemaphore error 
    Unable to allocate semaphore, system out of semaphores or permission issue
     
    ID: 30Severity: ErrorMEMORY_VIOLATIONMemory violation 
    Collector crashed you might need to patch the collector
     
    ID: 31Severity: ErrorOUT_OF_MEMORYOut of memory 
    The system ran out of memory and the collector exited
     
    ID: 32Severity: WarningDB_SERVER_OFFLINEDatabase Server off-line 
    Deprecated
     
    ID: 33Severity: ErrorHISTORY_NOT_AVAILABLEHistory not available 
    Most likely a time range was specified outside of what is available in history
     
    ID: 34Severity: WarningMETRICGROUP_NOT_AVAILABLEMetric group not available 
    The Perform collector supports data collection for metric groups that are not available on every remote agent. For example, the 'SRM Statistics' group will only be valid on Solaris machines running the Solaris Resource Manager but when the agent receives a collection request it will attempt to enable this group on the machine. The 'Metric group not supported' message indicates that the group happens to not be supported on this particular machine. In most cases this message can be ignored.
     
    ID: 35Severity: ErrorPROXY_NOT_SUPPORTEDProxy not supported 
    Proxy can only be configured on Windows, it likely that the proxy configuration is not configured or enabled.
     
    ID: 36Severity: WarningREMOTE_COMPUTER_OFFLINERemote computer off-line 
    The computer specified was unplugged from the network
     
    ID: 37Severity: ErrorREMOTE_COMPUTER_NOT_FOUNDRemote computer not found 
    The network DNS server is not aware this computer is on the network
     
    ID: 38Severity: ErrorSLOW_NETWORK_SPEEDSlow network speed between proxy and remote computer 
    The network speed of the computer is below the threshold set in the proxy configuration
     
    ID: 39Severity: ErrorACCOUNT_UNAUTHORIZEDAccount unauthorized 
    The account specified in the proxy configuration does not have privileges to access this computer

    For additional information see KA 000095975: 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 (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000095975)
     
    ID: 40Severity: ErrorACCOUNT_UNDEFINEDAccount undefined 
    The account specified in the proxy configuration does not have configured on this computer
     
    ID: 41Severity: ErrorOS_UNMATCHEDOperating System mismatch 
    This error typically occurs when either (a) The OS of the machine has been upgraded but the Perform agent hasn't been reinstalled (since on most platforms the Perform collector binary is OS version specific and the installation deploys the correct binary) or (b) The OS on which the Perform product has been installed isn't supported.

    For additional information see KA 000088482: Perform data collection fails with error, "Operating System Mismatch - SYSTEM - Collector Information" (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000088482).
     
    ID: 42Severity: ErrorONESHOT_INVALID_REQUESTCollect Request - Invalid fields in request 
    The request has been corrupted most likely by the network
     
    ID: 43Severity: WarningONESHOT_DUPLICATE_REQUESTCollect Request - Duplicate request 
    Data is being requested multiple times by either different consoles or manager runs. Data corruption or loss can take place if this is not corrected.
     
    ID: 44Severity: ErrorONESHOT_NOLOCALREPOSITORYCollect Request - Agent Repository (Local Repository) does not exist 
    Either the default agent repository specified in the BEST1_HOME/bgs/mgroup/Repository.loc file doesn't exist or the agent data repository specified in the domain/policy file for this computer doesn't exist. See KA 000092704: Error: Perform Agent (3367080) MrHistory::populate - ERROR: Error accessing repository root directory /usr/local/bmc/perform/history (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000092704)
     
    ID: 45Severity: ErrorONESHOT_INVALID_TIMERANGECollect Request - Invalid time range 
    The time specified in the collection request is invalid
     
    ID: 46Severity: ErrorONESHOT_NO_METRIC_GROUPSCollect Request - No Metric groups enabled 
    This problem occurs when the Perform agent has invalidated the collection for all of the requested metric groups. The following document describes the most common reasons this happens and resolution options: KA 000094008: The remote node seems to accept Perform data collection requests but then data collection is never started. The Perform Agent log contains the error "ERROR: No Metric Groups Enabled". (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000094008)
     
    ID: 47Severity: InformationONESHOT_COLLECT_PENDINGCollect Request - Data Collection pending 
    Nothing to worry about, the collection request will take place at a later time.
     
    ID: 48Severity: InformationONESHOT_COLLECT_ACTIVECollect Request - Data Collection active 
    Collecting data without errors
     
    ID: 49Severity: InformationONESHOT_UDR_WRITE_ACTIVECollect Request - Agent repository write active 
    Collecting data without errors
     
    ID: 50Severity: InformationONESHOT_COLLECT_COMPLETECollect Request - Data Collection Complete 
    Collected data
     
    ID: 51Severity: ErrorONESHOT_TRANSFER_NODIRCollect Request - Agent transfer directory does not exist 
    Unable to find the specified data
     
    ID: 52Severity: InformationONESHOT_TRANSFER_LOCAL_SUCCESSCollect Request - Agent data transfer successful 
    Data transferred
     
    ID: 53Severity: ErrorONESHOT_TRANSFER_LOCAL_FAILURECollect Request - Agent data transfer failed 
    Data transfer failed, you may want to increase the data transfer window
     
    ID: 54Severity: InformationONESHOT_TRANSFER_SUCCESSCollect Request - Agent data transfer successful 
    Data transferred
     
    ID: 55Severity: ErrorONESHOT_TRANSFER_FAILURECollect Request - Agent data transfer failed 
    Data transfer failed, you may want to increase the data transfer window
     
    ID: 56Severity: InformationONESHOT_FILE_AUTO_DELETECollect Request - Data deletion in Agent repository pending 
    Data has been transferred
     
    ID: 57Severity: InformationONESHOT_REPOSITORY_DELETEDCollect Request - Data deleted in Agent repository 
    Data has been transferred
     
    ID: 58Severity: InformationONESHOT_REQUEST_COMPLETECollect Request - Processing complete 
    Data collected
     
    ID: 59Severity: InformationONESHOT_STOP_REQUESTCollect Request - Stop request received 
    Collection request has been stopped
     
    ID: 60Severity: ErrorGEN_FAILUREGeneral Failure 
    Unknown and unexpected error
     
    ID: 61Severity: ErrorREMOTE_COMPUTER_NO_OSCannot determine Operating System of remote computer 
    The proxy agent was not able to determine the operating system of the agentless computer
     
    ID: 62Severity: ErrorDB_ERRORDatabase Server error encountered 
    Deprecated
     
    ID: 63Severity: ErrorSHMEM_KEY_CREATE_ERRORError creating key for shared memory segment 
    Check shared memory permission
     
    ID: 64Severity: ErrorSHMEM_SIZE_LIMITShared memory size limit error 
    Shared memory limit reached, reconfigure shared memory
     
    ID: 65Severity: ErrorSHMEM_ACCESS_ERRORNo permission to access shared memory segment 
    No permission to create shared memory
     
    ID: 66Severity: ErrorSHMEM_NO_MEMShared memory size exceeds available memory 
    Shared memory limit reached, shared memory to be reconfigured
     
    ID: 67Severity: ErrorSHMEM_NO_SPACEError creating shared memory segment - No more IDs available 
    The most common cause of this error is that a system imposed limit on shared memory segments has been reached and the system needs to be reconfigured to allow additional shared memory segments to be created. See 
     
    ID: 68Severity: ErrorSHMEM_ATTACH_ERRORError attaching to shared memory segment 
    Most likely shared memory permission issue
     
    ID: 69Severity: ErrorSEM_FILE_CREATE_ERRORError creating file used for semaphore key 
    The Perform agent creates files in the BEST1_COLLECT_HOME/bgs/monitor/tmp directory that it uses to access shared memory. If this directory doesn't exist or the Perform Installation Owner account doesn't have write access to this directory this error will be generated.

    Remediation:      
           
    • Verify that the BEST1_COLLECT_HOME/bgs/monitor/tmp directory exists on the machine and that the Perform Installation Owner has access to write to it and the files that exist in it
    •     
     
    ID: 70Severity: ErrorSEM_FILE_OPEN_ERRORError opening file used for semaphore key 
    The Perform agent creates files in the BEST1_COLLECT_HOME/bgs/monitor/tmp directory that it uses to access shared memory. If this directory doesn't exist or the Perform Installation Owner account doesn't have write access to this directory this error will be generated.

    Remediation:      
           
    • Verify that the BEST1_COLLECT_HOME/bgs/monitor/tmp directory exists on the machine and that the Perform Installation Owner has access to write to it and the files that exist in it
    •     
     
    ID: 71Severity: ErrorSEM_ACCESS_ERRORNo permission to access semaphore 
    User does not have permission to access resource
     
    ID: 72Severity: ErrorSEM_NO_SPACEError creating semaphore - No more IDs available 
    The most common cause of this error is that a system imposed limit on semaphore creation has been reached and the system needs to be reconfigured to allow additional semaphores to be created. See 000087882: 'Error creating semaphore - No more IDs available' reported for groups failing to collect data via the BMC Performance Assurance collector. (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000087882)
     
    ID: 73Severity: ErrorSEM_CREATE_ERRORError creating semaphore 
    Reconfigure semaphore limits
     
    ID: 74Severity: ErrorSEM_LOCK_ERRORError creating lock using semaphore 
    Reconfigure system lock limits
     
    ID: 75Severity: ErrorONESHOT_NODESTREPOSITORYCollect Request - Console repository (Destination repository) does not exist 
    The console repository has been moved or deleted
     
    ID: 76Severity: ErrorONESHOT_NOBEST1COLLECTHOMECollect Request - Best1 collect home does not exist 
    The best1home specified is invalid
     
    ID: 77Severity: ErrorONESHOT_NOLOCALPERMISSIONCollect Request - No permission on Agent repository (Local repository) 
    This error occurs when either the default history repository specified in the BEST1_COLLECT_HOME/bgs/mgroup/Repository.loc file or the agent data repository specified in the domain/policy file for the computer doesnât exist or the Perform Installation Owner doesn't have write permissions to that directory.

    Remediation:      
           
    • Verify the path in the Repository.loc file specifies a valid directory to which the Perform Installation Owner has write access
    •      
    • If an agent repository has been specified in the domain or policy file for this computer validate that directory exists on the remote agent
    •     
     
    ID: 78Severity: ErrorONESHOT_NODESTPERMISSIONCollect Request - No permission on Console repository (Destination repository) 
    This error occurs when directory where UDR data should be transferred on the console does not have sufficient write permissions for the Perform Installation Owner.

    Remediation:      
           
    • Verify the Perform Installation Owner has sufficient permissions to write to the console data repository specified in the domain/policy for this computer
    •     
     
    ID: 79Severity: WarningONESHOT_DATA_NOT_COLLECTEDCollect Request - Data not collected for metric group 
    The collector does not support this group, or a collector patch might be required
     
    ID: 80Severity: WarningNO_DATA_AVAILABLEMetric group currently has no data available for collection 
    The collector does not support this group, or a collector patch might be required
     
    ID: 81Severity: ErrorPATROL_HOME_NOT_SPECIFIEDPatrol Home directory not specified 
    Deprecated
     
    ID: 82Severity: ErrorCOLLECT_METHOD_NOT_AVAILABLECollection method not available 
    Deprecated
     
    ID: 83Severity: ErrorCOLLECT_METHOD_FAILUREError executing collection method 
    Deprecated
     
    ID: 84Severity: ErrorMISSING_PARAMSNamespace parameter(s) missing from data source 
    Deprecated
     
    ID: 85Severity: ErrorONESHOT_NOLOCALPERMISSION_NODECollect Request - No data or permission on Agent repository (Local repository) for node 
    This message occurs when the specified agent repository exists, and either the hostname sub-directory for the collection request already exists but the Perform Installation Owner doesn't have write access or less commonly doesn't exist (since typically if it didn't exist the Perform Agent would just create it).

    Remediation:      
           
    • Validate that the specified data repository exists and the Perform Installation Owner has access to write to that directory
    •     
     
    ID: 86Severity: ErrorONESHOT_NOLOCALPERMISSION_INSTANCECollect Request - No data or permission on Agent repository (Local repository) for instance 
    This message occurs when the specified agent repository exists, the hostname sub-directory exists, and the 'noInstance' directory under that exists the Perform Installation Owner doesn't have write access or less commonly doesn't exist (since typically if it didn't exist the Perform Agent would just create it).

    Remediation:      
           
    • Validate that the [Data Repository]/hostname/noInstance directory exists and the Perform Installation Owner has access to write to that directory
    •     
     
    ID: 87Severity: ErrorONESHOT_NOLOCALPERMISSION_TIMECollect Request - No data or permission on Agent repository (Local repository) for time 
    This message means that the collection request was sent to the agent, it was accepted, and the agent was expected to be collecting the data but when the console made the data transfer request the data didn't exist in the Agent Repository.

    One common source of this error is the agent is part of multiple Manager runs (typically across different consoles) and one Manager run has transferred and deleted the data before the other Manager run has initiated the transfer.

    Check the [hostname]-bgSD.log for multiple consoles sending start collection or transfer requests.
     
    ID: 88Severity: ErrorONESHOT_NOLOCALPERMISSION_GROUPCollect Request - No data or permission on Agent repository (Local repository) for group 
    The agent repository group level does not exist or user does not have permission to access
     
    ID: 89Severity: ErrorONESHOT_DELETE_COLLECT_ACTIVECollect Request - Collect still active unable to delete 
    Possible time skew between console and agent node, make sure agent time and console time is synchronized
     
    ID: 90Severity: ErrorONESHOT_DELETE_NO_PERMISSIONCollect Request - No permission to delete Agent repository 
    Check agent repository permission
     
    ID: 91Severity: ErrorSD_COMM_BAD_HOSTService daemon invalid host name provided (can not find server or DNS error) 
    This typically means that the specified hostname for data collection isn't defined in DNS or doesn't exist on the network anymore. Verify that the hostname specified is correct and that the computer is accessible over the network using that hostname.

    Remediation:      
           
    • On the command line of the Perform console run 'nslookup [hostname]'. If the hostname can't be resolved it may be necessary to specify the Full Qualified Hostname, populate the 'Network Address' field in the domain/policy file with the IP Address of the remote host, or work with the network administration team to define the host in DNS
    •     
    TSCO Gateway Server version 10.5 and 10.7: Defect QM002309064 causes this error code to be used for any agent that is unreachable (so any agent where the TSCO Gateway Server can't access the Service Daemon on port 10128).  That problem has been fixed in Cumulative Hot Fix (CHF) package 10.5.00.01.C00010 and 10.7.01.00.C00002 and later.
     
    ID: 92Severity: ErrorSD_COMM_BAD_PORTService daemon not installed on the remote node (connection refused) 
    This message means that the Perform console was unable to initiate a connection to port 10128 on the remote node and the remote computer responded with a 'connection refused' message. This typically occurs when:      
           
    1. There isn't any process listening on port 10128 (The Perform product isn't installed on the machine, the Service daemon hasn't been configured to run on the machine, and so on)
    2.      
    3. A firewall betwen the Perform console and the remote agent is actively blocking the connection
    4.     

    For debugging suggestions see KA 000032141: Debugging Service Daemon connection problems (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000032141)
     
    ID: 93Severity: ErrorSD_COMM_BAD_PROTOCOLService daemon protocol terminated in the middle of session (network or disk timeout) 
    This error may occur due to network communication problems between the Perform console and the remote agent during the data transfer. Sometimes problems on the remote agent side itself (which will typically be more visible in the logs on the Perform agent machine itself) may also trigger this problem. See KA 000094547: UDR data transfer back to the Perform console is failing for some or all machines. Error, "Service daemon protocol terminated in the middle of session network or disk timeout)" (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000094547) for additional information.
     
    ID: 94Severity: ErrorSD_COMM_CONNECT_TIMEOUTService daemon connection timed out (node offline 
    The agent node is off the networkThis message means that the Perform console was unable to initiate a connection to port 10128 on the connection attempt timed out. This typically occurs when:      
           
    1. The remote computer is offline
    2.      
    3. A firewall betwen the Perform console and the remote agent is dropping the connection
    4.      
    5. In some cases this occurs when the hostname is not defined in DNS
    6.     

    For debugging suggestions see KA 000032141: Debugging Service Daemon connection problems (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000032141)
     
    ID: 95Severity: InformationONESHOT_COLREQ_SENTCollect request sent from console and received by the agent 
    No issues
     
    ID: 96Severity: ErrorONESHOT_COLREQ_PERIOD_TIMEOUTCollect request not successfully sent to the agent during the time period allowed 
    The time to sent the request has expired
     
    ID: 97Severity: ErrorONESHOT_DATA_DELETION_FAILEDRequest to delete data from agent repository failed after successful transfer 
    Manually remove the agent data from the agent repository
     
    ID: 98Severity: WarningONESHOT_MISSING_GROUPSNo data collected for some of the configured metric groups 
    Most likely the groups specified are not supported by the collector
     
    ID: 99Severity: ErrorONESHOT_QUERY_MISSING_REQUESTCollect request not scheduled in agent 
    The request has been sent by the agent, but has been removed.
     
    ID: 100Severity: ErrorONESHOT_NO_GROUPS_COLLECTEDNo data collected for all of the configured metric groups 
    The collector did not collect any groups, you might need a collector patch
     
    ID: 101Severity: ErrorONESHOT_PULL_COLLECT_ACTIVECollect Request - Collect still active unable to transfer 
    Most likely there is a time skew between the console and the agent. Make sure the agent and the console are synchronized.
     
    ID: 102Severity: ErrorONESHOT_TRANSFER_PERIOD_TIMEOUTCollected data not successfully transferred from agent computer during the time period allowed 
    You can increase the transfer time
     
    ID: 103Severity: ErrorONESHOT_DELETE_PERIOD_TIMEOUTCollected data not deleted from agent repository during the time period allowed 
    Manually remove the agent data from the agent repository
     
    ID: 104Severity: InformationONESHOT_STOP_REQUEST_SENTStop collection request sent from console and received by the agent 
    Collection has been stopped
     
    ID: 105Severity: InformationONESHOT_COLREQ_ALREADY_SCHEDULEDCollect request is already scheduled at the agent 
    Collection has been scheduled previously
     
    ID: 106Severity: ErrorONESHOT_TRANSFER_RENAME_FAILEDTransferred data _TMP start time directory could not be renamed 
    Manually rename the _TMP directory
     
    ID: 107Severity: ErrorSD_COMM_BAD_PROTOCOL_STARTService daemon protocol terminated in the start of session (no bgssd executable or another application using port) 
    This means that the Perform console was able to successfully connect to the Service Daemon port (10128) on the remote agent but received an unexpected response. Some common reasons for this to occur are:      
           
    1. Another process is listening on port 10128
    2.      
    3. On Unix, [x]inetd is initially accepting the connection by TCP Wrappers is closing the connection as unauthorized
    4.      
    5. The Service Daemon binary is failing in a way that generates output (for example, if a required library is missing)
    6.      
    7. [x]inetd is failing to properly pass the connection request onto the Service Daemon process
    8.     

    Typically the debugging steps in KA 000032141: Debugging Service Daemon connection problems (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000032141)
     
    ID: 108Severity: ErrorSD_CANNOT_REACH_AGENTService daemon unable to send message to agent (bgsagent is too busy) 
    This error typically means that the Perform Agent master thread is too busy to respond to the messages being sent by the Service Daemon. This error is most typically seen when communicating with a proxy host.

    Remediation:      
           
    • In many situations stopping and restarting the Perform Agent on the machine will resolve this problem
    •     

    If the problem persists open an issue with Technical Support and provide the Perform logs from the agent machine.
     
    ID: 109Severity: ErrorGROUP_DISABLEDMetric group has been disabled 
    Enable the metric group if you would like to get data for the group.
     
    ID: 110Severity: ErrorCOLLECTOR_CRASHEDCollector has crashed 
    You may need a patch for the collector.
     
    ID: 111Severity: ErrorOPENSSH_NOT_INSTALLEDSSH is not installed 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 112Severity: ErrorOPENSSH_MISSING_CONFIG_FILESSH could not find config file 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 113Severity: ErrorOPENSSH_MISSING_KEY_FILESSH could not find key file 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 114Severity: ErrorOPENSSH_MISSING_KNOWNHOSTS_FILESSH could not find known_hosts file 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 115Severity: ErrorOPENSSH_PASSWORD_AUTHENTICATIONSSH using password authentication 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 116Severity: ErrorOPENSSH_STRICT_HOST_KEY_CHECKINGSSH not using strict host key checking 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 117Severity: ErrorOPENSSH_KEY_MISCONFIGUREDSSH key file misconfigured 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 118Severity: ErrorOPENSSH_MISSING_REMOTEHOSTSSH remote host not found in known_hosts file 
    You may need to configure the parameter using /usr/adm/best1_V.V.VV/bgs/scripts/configure_openssh (where V.V.VV is the product version, for example, 10.3.00)
     
    ID: 119Severity: ErrorOPENSSH_REMOTE_COMMANDS_DISABLEDSSH could not execute command on remote host (remote commands disabled) 
     
     
    ID: 120Severity: ErrorOPENSSH_PERMISSION_DENIEDSSH could not execute command on remote host (permission denied) 
     
     
    ID: 121Severity: ErrorCOLLECTOR_TRANSIENT_TIMEOUTTransient collection timeout occurred (will try again next interval) 
    If this error persists you may need a collector patch
     
    ID: 122Severity: ErrorCOLLECTOR_UNRECOVERABLE_TIMEOUTUnrecoverable collection timeout occurred (will no longer try again) 
    Unable to collect group, you may need a collector patch
     
      
    Related Products:  
       
    1. TrueSight Capacity Optimization
    2.  
    3. BMC Capacity Management
       Legacy ID:KA373639

     


    Article Number:

    000097173


    Article Type:

    Solutions to a Product Problem



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