Control-M/Server configuration agent (CA process) does not startup by start_ca command.

Version 5
    Share This:

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


    PRODUCT:

    Control-M/Server for UNIX and Microsoft Windows


    COMPONENT:

    Control-M/Server for UNIX and Microsoft Windows


    APPLIES TO:

    Control-M/Server for UNIX and Microsoft Windows ; all versions



    PROBLEM:

     

      Control-M/Server configuration agent (CA process) does not startup.  Messages similar to those below can be found in the CA log in the Control-M/Server's proclog directory. 
      
        
      
      $ cat $CONTROLM_SERVER/proclog/CA.15530.log
    0421 11:36:55.74 CA: Local host: HOSTAAA - Linux 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64
    0421 11:36:55.75 CA: SERVER 6.4.01.300 - folders 1796 - Wed Dec  2 21:00:44 2009
    0421 11:36:55.75 CA: Files descriptors limit: 1024, Maximum : 1024.
    0421 11:36:55.75 CA: Core file limit in bytes: 0, Maximum : unlimited.
    0421 11:36:55.75 CA: CPU usage limit in seconds: unlimited, Maximum : unlimited.
    0421 11:36:55.75 CA: The maximum size of a process' heap in bytes: unlimited, Maximum : unlimited.
    0421 11:36:55.75 CA: The maximum size of a file in bytes: unlimited, Maximum : unlimited.
    0421 11:36:55.75 CA: The maximum size of a process' stack in bytes: 10485760, Maximum : unlimited.
    0421 11:38:06.02 CA: CTM6421 -> server_main_loop : Catastrophic failure while  waiting for requestor to start
    0421 11:38:36.27 CA: OS_MUTEX_destroy failed rc=16
    0421 11:38:36.27 CA: GM_THREAD_SYNC_destroy - Error destroying mutex no 5 rc=2

     


    CAUSE:

    The problem is that the waiting time has elapsed, before all the threads have come up.


    SOLUTION:

     

    The CA (p_ctmca) process, when starting, invokes its working threads and then it waits a certain time, to make sure that indeed the working threads have started running.
    The problem is that the waiting time has elapsed, before all the threads have come up.

      
        
      
      Perform the following steps and verify it solves the problem:  
    1. Stop the CA process, via the command  "shut_ca".  
    2. Open the config.dat file, located under the Control-M/Server Home directory <CTMHOME>/data directory (If it is a HA - high availability environment, do this change at active node).  
    3. Add the following line to the file:  
    THREAD_STATE_RETRY_SLEEP 1000  
    4. Save the file.  
    5. Restart the CA process, using the command "start_ca" 
      
      6. if the CA process starts and stays running, the problem is resolved.  
     
    Parameter THREAD_STATE_RETRY_SLEEP  
    Indicates how much time, in milliseconds, to wait for threads to be in a desire state.  
    default value: 250 
      
        
      
      If the above steps do not resolve the problem, perform the below to collect special debug information and open an Case with BMC Support:  
    1. Stop the CA process, via the command  "shut_ca"  
    2. Make a backup copy of the config.dat file, located in the Control-M/Server's home directory <CTMHOME>/data 
      
      3. Open the config.dat file, located in the Control-M/Server's home directory <CTMHOME>/data  
    4. Add the following lines:  
    CTM_CONFIG_AGENT_DEBUG_LEVEL 4  
    CTM_CONFIG_AGENT_MODULE_LEVEL 0  
    5. Save the file.  
    6. Re-start the CA process, via the command "start_ca" 
      
      7. Disable debug by modifying the config.dat file and removing the two lines added in step 4 above. 
      
        
      
      This will force the CA to run in special debug mode.  When the problem reoccurs, please open a new issue with BMC Support and provide the following information: 
      
      1. From The 'proclog' sub-directory of the Control-M/Server proclog directory, all files that start with CA.  
      
      2. The config.dat file from the Control-M/Server's home directory <CTMHOME>/data 
      
     
    NOTE:  
    On rare occasions starting the CA process in debug does not produce any logs.  
    If this occurs, manually run the p_ctmca binary executable and errors may occur on the screen.  
    For example on an AIX host:   

    % /home/ctmserver/ctm_server/exe_AIX/p_ctmca

       

    Could not load program p_ctmca:

       

    rtld: 0712-001 Symbol __apl__Q2_3std12basic_stringXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__FPCc was referenced

       

          from module p_ctmca(), but a runtime definition

       

                of the symbol was not found.

       

    rtld: 0712-001 Symbol __ct__Q2_3std18basic_stringstreamXTcTQ2_3std11char_traitsXTc_TQ2_3std9allocatorXTc__Fi was referenced

       

          from module p_ctmca(), but a runtime definition

       

                of the symbol was not found.

    For this specific example it was necessary for the AIX System Administrator to update the problematic compilers. 

     


    Article Number:

    000090069


    Article Type:

    Solutions to a Product Problem



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