What does the following error message in the Control-M/Server NS log mean?   CTM6090 -> NS_AG_AV_cl::handle_start_chk_next: Illegal node type

Version 3
    Share:|

    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



    PROBLEM:

     

    When submitting jobs thru a remote host (agentless), jobs work as expected but the following message keeps appearing in the NS log:

    0924 15:59:18.22 NS: NS_AG_AV_cl::handle_start_chk_next: Handle next node <NODEID>
    0924 15:59:18.22 NS: GM_PARAM_ini_get:table:'dbs_debug_msgtbl', key:'6090'
    0924 15:59:18.22 NS: rc = 1
    0924 15:59:18.22 NS: rc = 1
    0924 15:59:18.22 NS: CTM6090 -> NS_AG_AV_cl::handle_start_chk_next: Illegal node type


     

     


    CAUSE:

    The remote host definition has and incorrect definition / configuration.


    SOLUTION:

     

    1) Connect to the Control-M/Server database using the command:   sql

    2) Run the following query:
    select NODEID, 'X' || NODETYPE || 'X' from CMR_NODES where NODETYPE != 'N' and NODETYPE != 'R' and NODETYPE != 'U';

    3) If the output shows any nodeid's, then that entry is invalid and the nodetype is likely set to null.

    nodeid | ?column?
    ----------------+----------
    examplehostname | XX
    (1 row)


    4) Run the following query to list all node entries.  There may be a situation where a short and long name Agent exist and one of those has the null entry, which will cause the message in the NS log.

    select * from CMR_NODES;

    nodeid | phys_nodeid | agstat | first_set | last_upd | nodetype | is_default | hostname | domain_name | version | os_name | platform
    ------------------------------------+------------------------------------+--------+----------------+----------------+----------+------------+------------------------------------+------------------------+------------+--------------------------------------------------------------------------------------+----------
    examplehostname | examplehostname | U | 20110426120359 | 20110426125200 | | N | | | | |
    examplehostname.domain.com | examplehostname.domain.com | V | 20121106122210 | 20121114171923 | N | N | examplehostname.domain.com | domain.com | 6.4.01.500 | Linux 2.6.18-92.1.18.el5.028stab060.8 | Unix

    In this output, row #1 shows that examplehostname has nodetype set to null, which is not a valid value for that field.


    5) Delete the bad Agent.
    If needed, rediscover the Agent.

     


    Article Number:

    000093796


    Article Type:

    Solutions to a Product Problem



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