This space contains documentation for TrueSight Server Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Server Automation 8.9.

Troubleshooting virtualization configuration objects issues

Certain virtualization configuration objects running on a Red Hat Linux computer might encounter the following error: any action that you try to perform through the TrueSight Server Automation Console for the management of the Citrix XenServer server assets results in an error message, "Unable to start CO Server." 

This problem arises when resource usage by the configuration object exceeds the defined OS limitations for the allocation of shared memory segments or message queues.


The configuration objects might load properly for the first few users that connect to the RSCD agent. After OS limitations have been reached, all additional user connections will experience the problem.

To prevent this issue from occurring, TrueSight Server Automation provides a shell script ( ) that you can use to update the IPC configuration parameters in the Red Hat kernel so that the TrueSight Server Automation configuration object can run. This script updates the /etc/sysctl.conf file, which controls system parameters.
You must execute the script on any machine running a Red Hat Linux agent that has the Citrix XenServer TrueSight Server Automation configuration object installed.

To run the script for modifying IPC parameters, complete the following steps:

  1. Log on to the Red Hat Linux computer as root.
    If you are not permitted to log on as root, use the su or sudo command to gain sufficient permissions.
  2. Use the cd command to navigate to the installationDirectory/NSH/sbin directory.
  3. Stop the RSCD agent using the agentctl stop command.
  4. Run the script using the -options command, where options can be any of the parameters described in the following table.




    Use this option to perform a dry run of the script, to verify the potential updates that the script makes to the /etc/sysctl.conf file and the IPC values in the kernel. Each listed update displays the key, the current system value, and the new value.


    Use this option to update the current IPC values in the kernel and in the /etc/sysctl.conf file. The script creates a backup file named /etc/sysctl.conf.beforeBMCScriptUpdate before updating the /etc/sysctl.conf file. Note: If you also use the -d option with the -w option, only a dry run is performed.


    Use this option with the -w option to create a sysctl.conf file in the current directory, instead of updating the /etc/sysctl.conf file. This option can be helpful for testing. The /etc/sysctl.conf file and the system are not updated.


    Use this option to run the script in verbose mode, which displays detailed messages. You can use this option with all other options except for -h.


    Use this option to display the usage message.

    As the script runs (with the -w option), the /etc/system.conf file is updated with new values for IPC parameters, within a new BMC BladeLogic section. Old values are commented out, as shown in the following figure, an example of an updated system.conf file.

    ### The line below is commented out by BMC script
    ### kernel.shmmax = 4294
    # Controls the maximum number of shared memory segments, in pages
    ### The line below is commented out by BMC script
    ### kernel.shmall = 26842
    ### BMC Bladelogic Section - Start
    kernel.sem=250 32000 32 1024
    ### BMC Bladelogic Section - End
  5. Start the RSCD agent using the agentctl start command.
Was this page helpful? Yes No Submitting... Thank you