Truesight Capacity Optimization(TSCO) - watchdog scripts are not being scheduled in crontab

Version 1
    Share This:

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


    PRODUCT:

    TrueSight Capacity Optimization


    COMPONENT:

    Capacity Optimization


    APPLIES TO:

    TrueSight Capacity Optimization(TSCO) 10.x



    PROBLEM:

     

    When the TSCO processes are started via the $CPITBASE/cpit command it checks that there are watchdog scripts scheduled in cron to automatically restart the processes if they terminate unexpectedly for any reason.

    So, one expects to see one or more of the following watchdog scripts scheduled in the TSCO Installation Owner (by default the cpit user's) crontab:

    * * * * * /opt/bmc/BCO/tools/watchdog.sh httpd /opt/bmc/BCO/3rd_party/apache2/apache.laststatus
    * * * * * /opt/bmc/BCO/tools/watchdog.sh web /opt/bmc/BCO/web/tomcat/logs/web.pid
    * * * * * /opt/bmc/BCO/tools/watchdog.sh scheduler /opt/bmc/BCO/scheduler/log/scheduler.pid
    * * * * * /opt/bmc/BCO/tools/watchdog.sh datahub /opt/bmc/BCO/datahub/tomcat/logs/datahub.pid

    If the scripts are missing from crontab there are some things to investigate to get them added.

     


    SOLUTION:

     

    First, validate that the TSCO installation owner (the cpit user by default) has access to crontab.

    The following KA describes the most common error that results in the scripts not being scheduled:
    TrueSight Capacity Optimization (TSCO): On startup, one or more services give this message, 'Crontab cannot be used. Make sure "[script]" is scheduled on some other scheduling tool.' (KA000092234)

    Another possibility that the watchdog scripts are missing from crontab -- particularly if only a subset of the scripts are scheduled for the components running on the machine is that the detection code for whether the scripts are already scheduled is failing.

    The cpit script checks crontab -l output to see if the watchdog scripts need to be added to cron. But, the check is too simplistic so it can be tricked into not adding the watchdog scripts.

    So, for example, the check for whether the scheduler watchdog script is scheduled looks like this:
      crontab -l | grep scheduler

    The check for whether the httpd watchdog script looks like this:
      crontab -l | grep httpd 

    The problem is that a simple comment in the crontab output like this causes the cpit script to not add the watchdog script to cron:
    # I love the scheduler watchdog!

    The above comment line would cause the scheduler watchdog script to not be scheduled as it contains the scheduler keyword so the cpit script would think it was already scheduled.

    The recommended workaround is to either:
      (A) Manually insert the necessary watchdog scripts into crontab for the TSCO Installation Owner user
      - or -
      (B) Find the problem entries in crontab that are stopping the insert of the watchdog scripts.

    For example, for the '# I love the scheduler watchdog!' command that line could be changed to "# I love the Scheduler watchdog!' to avoid the match (capital 'S' instead of lowercase since the grep is case sensitive).

    This behavior is being tracked by Defect QM002148433: 'The cpit script to check if the watchdog scripts are scheduled can fail to detect watchdog script needs to be added.'

     


    Article Number:

    000123394


    Article Type:

    Solutions to a Product Problem



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