'Error creating semaphore - No more IDs available' reported for groups failing to collect data via the TrueSight Capacity Optimization (TSCO) Capacity Agent

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

'Error creating semaphore - No more IDs available' reported for groups failing to collect data via the TrueSight Capacity Optimization (TSCO) Capacity Agent
'Error creating semaphore - No more IDs available' reported for groups failing to collect data via the TSCO Capacity Agent
TrueSight Capacity Optimization
TrueSight Capacity Optimization 20.02, 11.5, 11.3, 11.0, 10.7, 10.5, 10.3, 10.0 ; BMC Performance Assurance 9.5
Although data is being collected and transferred to the TSCO Gateway Server some of the metric groups are missing. Looking at the UDR Collection Manager (UCM) Status Reports some groups are reported in Terminated No Data' status and report the error:
  Error creating semaphore - No more IDs available

This error message is also visible in the $BEST1_HOME/bgs/log/[hostname]-bgsagent_6767.log on the remote node.

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
  • Typically Solaris machines although this message is possible for HP-UX and Linux as well.

This message indicates that server on which the TrueSight Capacity Optimization (TSCO) Agent is running has run out of semaphores so it can't allocate the metric groups.

These messages should be visible in the UDR Collection Manager (UCM) status reports for the TSCO Capacity Agent machine.

The following output would be useful to identify why this machine has run out of available semaphores:
  • The output from 'ipcs -a'
  • The output from 'sysdef'
  • A copy of the /etc/system file (for Solaris)
  • The entire contents of the /usr/adm/best1_default/bgs/log directory.  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)
The typical source of the problem is that the shared memory limits on that machine are somewhat low and either another shared memory consuming application has started on that machine and it is using up some of the IPC shared memory or some of the TSCO Agent shared memory segments have been orphaned and there isn't sufficient additional shared memory configured for a second allocation of segments.

The long term solution will likely be to increase the shared memory settings on the machine and reboot to get those settings applied. In the short term it may be possible to manually clear some segments if the TSCO Agent has orphaned them.

The recommended shared memory and semaphore settings for TSCO Agent data collection are documented in the product documentation  For example, for TSCO version 20.02, Configuring the shared memory and semaphores: https://docs.bmc.com/docs/display/btco2002/Configuring+the+shared+memory+and+semaphores
 
Related Products:
  1. TrueSight Capacity Optimization
  2. BMC Performance Assurance
Legacy ID:KA318067
 
NOTE: This document was originally published as Solution SLN000000226648.
TrueSight Capacity Optimization
TrueSight Capacity Optimization 20.02, 11.5, 11.3, 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, 11.0, 10.7, 10.5, 10.3, 10.0 ; BMC Performance Assurance 9.5
Attachment(s):