TrueSight Capacity Optimization (TSCO) data collection fails with message "Collect request - Error: duplicate collect request not scheduled ([nodename]:noInstance)" in the agent log file.

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) data collection fails with message "Collect request - Error: duplicate collect request not scheduled ([nodename]:noInstance)" in the agent log file.
TrueSight Capacity Optimization (TSCO) data collection fails with message "Collect request - Error: duplicate collect request not scheduled ([nodename]:noInstance)" in perform agent log file.
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
The attempt to collect the data from the machine fails with the message "Collect request - Error: duplicate collect request not scheduled ([nodename]:noInstance)" in the [hostname]-bgsagent_6767.log file.

Also UDR Collection Manager (UCM) status reports will indicate the problem with messages like,
 
Thu May 22 23:31:29 2008 [Agent-Warning] Collect Request - Duplicate request  
Thu May 22 23:33:41 2008 [UCM-Information] Collect request sent from console and received by the agent  
Thu May 22 23:33:41 2008 [Agent-Warning] Collect Request - Duplicate request  
Fri May 23 00:32:56 2008 [UCM-Warning] Collect request not scheduled in agent  

Applies To:
  • TrueSight Capacity Optimization 20.02, 11.5, 11.3.01, 11.0, 10.7, 10.5, 10.3, 10.0
  • BMC Performance Assurance for Servers  9.5
  • Windows
  • Unix

The most common reason this message will be reported in the TrueSight Capacity Optimization (TSCO) Agent logs are:

  1. The computer exists in more than one domain (or policy) file used in an active scheduled Manager run on the TSCO Gateway Server.
  2. More than one TSCO Gateway Server is attempting to start data collection on the same remote computer with the same collection start time
  3. A computer is listed in the same policy file using the same name in a different case. For example 'computer1' versus 'COMPUTER1'. Manager treats them as unique entries but the TSCO Agent does a case insensitive hostname check which results in the requests being seen as duplicates.

Symptoms of having duplicate collection requests issued include:
  • Data transfer for one instance of the machine may be listed as having failed if the other instance of the machine has been able to successfully complete the transfer (and delete the data from the TSCO Agent machine that has duplicate requests) before the 2nd TSCO Gateway Server manager run containing the computer attempts its transfer.
  • If the request is being sent from different TSCO Gateway Servers, one TSCO Gateway Server may receive incomplete or no data from the machine (since the first transfer to complete successfully will result in the data being deleted from the remote node).
  • If the request is being sent from the same console, the UDR data transferred to the console may be corrupt because both transfer requests will be independently trying to update the same UDR files in the console repository.  This is uncommon in modern releases of the TSCO Gateway Server as the dataProcessing.cfg TRANSFER_USE_FILE_LOCKS property is set to '1' by default which uses file locking during transfer to prevent this.

To begin debugging, send the following logs files to BMC Technical Support.
  • The TSCO Agent log files (See KA 000090065: Truesight Capacity Otimization (TSCO) : Capturing the Capacity Agent collection log files from the remote node - INCLUDES VIDEO (https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000090065)
  • A copy of UCM Status Reports directory ($BEST1_HOME/local/manager/status) from the TSCO Gateway Server, if this directory is very large just the TSCO Agent logs are generally sufficient to begin debugging.

Related Products:
  1. TrueSight Capacity Optimization
  2. BMC Performance Assurance
Legacy ID:KA294789
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):