The Control-M/Server Configuration Agent stops running and the logs show the following: Catastrophy occured CTM6415 - Failed while trying to send kpa message to all threads code: 2

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

    All versions of Control-M/Server for UNIX and Microsoft Windows



    PROBLEM:

     

    - Control-M/Server Configuration Agent - Catastrophy occured
    - The Control-M/Server Configuration Agent (CA) ended with the following messages in CA log

      
    0928 10:38:03.769 CA: CTM6415 -> GM_THREAD_MGR_check_kpa : thread with index 2 has kpa problem 0928 10:38:03.773 CA: Catastrophy occured 0928 10:38:03.773 CA: server_main_loop: Failed while trying to send kpa message to all threads code: 2. 0928 10:38:03.773 CA: CTM6421 -> server_main_loop : Catastrophic failure while in main loop 0928 10:38:33.948 CA: CTM6404 -> gm_thread_enty_destroy : asked to terminate a running thread id=515 0928 10:38:33.948 CA: CTM6404 -> gm_thread_enty_destroy : asked to terminate a running thread id=772

     


    CAUSE:

    The stack used by Control-M/Server Configuration Agent to write function call has reached its limit


    SOLUTION:

     

    Perform the below to fine tune the usage of of the stack used by Control-M/Server Configuration Agent:

    Increase the Control-M/Server Configuration Agent timeout for the all thread to start:
    1. Stop the CA process via the command "shut_ca".
    2. Edit the config.dat file located under the Control-M/Server Home directory <CTMHOME>/data directory.
    3. Add the following line to the file (check if it exists first, and modify if found):
    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.

      

    If not resolved, perform the following steps to decrease the time interval for WD to perform the health check:
    1. Shut down the Control-M/Server via ctm_menu or the shut_ctm command.
    2. Make a backup of the Control-M/Server ctm_server/data/config.dat file, then open it for editing
    3. Look for the parameter WD_HEARTBEAT_INTERVAL and change its value to 10.
    4. Restart the Control-M/Server via ctm_menu or with the start_ctm command.

    Note:
    WD_HEARTBEAT_INTERVAL - Amount of time (in seconds) to wait after receiving a response to a heartbeat check before issuing the next heartbeat check.

     

       If still is not resolved then performing he following steps to increase the size of stack used by Control-M/Server Configuration Agent:

    1. Shut down CA process via the command shut_ca 
    2. Add the following line into config.dat file:  

                   THREAD_STACK_CA_SIZE 2048

    3. Start CA via the command start_ca  

    The CA process uses a stack, which writes the function calls, the parameter THREAD_STACK_CA_SIZE decides the size of this stack.

      

    In some cases this stack is used until the limit, and then the CA process crashes.

      

    The default value is 1024, therefore it's suggested to raise it to 2048

      

    Legacy ID:KA380206

     


    Article Number:

    000074815


    Article Type:

    Solutions to a Product Problem



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