Setting up ctmping with WatchDog

Derick · Post by **Derick** » 25 Feb 2009 11:30

Hi,

I'm trying to setup ctmping with WatchDog to monitor my agents, but can't seem to get it working/appearing in the Alerts window (6.3). Below are the WD entries in my config.dat and the agent list text file. What should I change or add?

# WatchDog
WD_INTERVAL 6
CTM_PRM_ENABLE_UE Y
WD_USEREXIT_NUMBER 1
WD_CTMEXIT_NUMBER 2
WD_ALIVE_MSG WD is alive

# WatchDog error handlers
WD_CTO_HOSTNAME derickp_lt
WD_CTO_TIMEOUT 10
WD_ERROR_HANDLES_TIMEOUT 10
WD_ERROR_HANDLER_SCRIPT_FILE ./scripts/UE_handler

# CTMPING to agents
WD_USEREXIT_1_CMD_LINE -file C:\agntlist.txt
WD_USEREXIT_1_ERROR_MSG Agent not available
WD_USEREXIT_1_INTERVAL 1
WD_USEREXIT_1_RUN_STATE Y
WD_USEREXIT_1_SCRIPT_ FILE ctmping
WD_USEREXIT_1_SUSPEND_STATE N
WD_USEREXIT_1_TIMEOUT 5

C:\agntlist.txt :
derickp_lt REGULAR
bmc-sun REMOTE

philmalmaison · Post by **philmalmaison** » 25 Feb 2009 3:11

did you stop/start controlm server after modifing config.dat ?
what is the alert on abend em parameter ?

regards
philmalmaison

philmalmaison · Post by **philmalmaison** » 25 Feb 2009 3:16

could you give your UE_handler file ?

Derick · Post by **Derick** » 25 Feb 2009 3:33

Hi, thanks for the assistance.

Where do I find the alert on abend em parameter?

I thought the EU_handler file will be there as default, but it is not. Do you possibly have an example file for me?

philmalmaison · Post by **philmalmaison** » 25 Feb 2009 3:48

UE_handler
sapteus2-controlm [11] more UE_handler
#!/bin/sh

ctmshout -DEST ECS -MESSAGE "$1" -SEVERITY $2 2>&1 1>/dev/null

exit 0

philmalmaison · Post by **philmalmaison** » 25 Feb 2009 3:52

configuration manager/system parameters/gtw/alertonabend (1 ou 0)
regards
philmalmaison

philmalmaison · Post by **philmalmaison** » 25 Feb 2009 3:56

otherwise i use the CTMEXIT instead USEREXIT, and i don't have any problem.
# WatchDog error handlers
WD_CTO_HOSTNAME
WD_CTO_TIMEOUT 10
WD_ERROR_HANDLES_TIMEOUT 10
WD_ERROR_HANDLER_SCRIPT_FILE ./scripts/UE_handler

# WatchDog exit's for users
# Use following format to define user values
WD_USEREXIT_#_INTERVAL # (run every # interval)
WD_USEREXIT_#_TIMEOUT # (in seconds)
WD_USEREXIT_#_RUN_STATE (y / n)
WD_USEREXIT_#_SUSPEND_STATE (y / n)
WD_USEREXIT_#_SCRIPT_FILE Full path to the script / executable file
WD_USEREXIT_#_CMD_LINE A command line to be passed to the script
WD_USEREXIT_#_ERROR_MSG Error to be passed if the check fail

# WatchDog exit's for Control-M
WD_CTMEXIT_1_INTERVAL 50
WD_CTMEXIT_1_TIMEOUT 15
WD_CTMEXIT_1_RUN_STATE y
WD_CTMEXIT_1_SUSPEND_STATE n
WD_CTMEXIT_1_SCRIPT_FILE ctm_diskspace
WD_CTMEXIT_1_CMD_LINE "650M"
WD_CTMEXIT_1_ERROR_MSG ATTENTION:FScontrolm

WD_CTMEXIT_2_INTERVAL 60
WD_CTMEXIT_2_TIMEOUT 20
WD_CTMEXIT_2_RUN_STATE y
WD_CTMEXIT_2_SUSPEND_STATE n
WD_CTMEXIT_2_SCRIPT_FILE ctm_dbspace
WD_CTMEXIT_2_CMD_LINE "30"
WD_CTMEXIT_2_ERROR_MSG ATTENTION:DataLog

WD_CTMEXIT_3_INTERVAL 10
WD_CTMEXIT_3_TIMEOUT 360
WD_CTMEXIT_3_RUN_STATE y
WD_CTMEXIT_3_SUSPEND_STATE n
WD_CTMEXIT_3_SCRIPT_FILE ctm_dmp_te_wd
WD_CTMEXIT_3_CMD_LINE "/produits/arch_ctrlm"
WD_CTMEXIT_3_ERROR_MSG ATTENTION:ctm_dmp_te_wd

WD_CTMEXIT_4_INTERVAL 30
WD_CTMEXIT_4_TIMEOUT 20
WD_CTMEXIT_4_RUN_STATE y
WD_CTMEXIT_4_SUSPEND_STATE n
WD_CTMEXIT_4_SCRIPT_FILE CLEANDIR
WD_CTMEXIT_4_CMD_LINE ""
WD_CTMEXIT_4_ERROR_MSG ATTENTION:CLEANDIR

WD_CTMEXIT_5_INTERVAL 10
WD_CTMEXIT_5_TIMEOUT 120
WD_CTMEXIT_5_RUN_STATE y
WD_CTMEXIT_5_SUSPEND_STATE n
WD_CTMEXIT_5_SCRIPT_FILE ctmjsa
WD_CTMEXIT_5_CMD_LINE "*"
WD_CTMEXIT_5_ERROR_MSG

regards
philmalmaison

Derick · Post by **Derick** » 26 Feb 2009 11:03

Hi, thanks for all the info. I'll implement, test and confirm.