Management programs and watchdog scripts

Lists the names and corresponding watchdog scripts for the DataChannel management programs.

The following table lists the names and corresponding watchdog scripts for the DataChannel management programs running on different DataChannel hosts.

Table 10: Programs and Scripts

Component Program Executable* Corresponding Watchdog Script Notes
Channel Name Server CNS cnsw Runs on the host running the Channel Manager.
Log Server LOG logw
Channel Manager CMGR cmgrw
Application Manager AMGR amgrw One per subchannel host and one on the Channel Manager host.
* The actual component's executable file seen in the output of ps -ef is named XXX_visual , where XXX is an entry in this column. For example, the file running for CMGR is seen as CMGR_visual.

The watchdog scripts run every few minutes from cron. Their function is to monitor their corresponding management component, and to restart it if necessary. You can add watchdog scripts for the Channel Manager programs to the crontab for the pvuser on each host on which you installed a DataChannel component.

To add watchdog scripts to the crontab:

  1. Log in as pvuser. Make sure this login occurs on the server running the Channel Manager components.
  2. At a shell prompt, go to the DataChannel conf subdirectory. For example:
    
 $ cd /opt/datachannel/conf
  3. Open the file dc.cron with a text editor. (The dc.cron files differ for different hosts running different DataChannel programs. The following example shows the dc.cron file for the host running the Channel Manager programs.)    
    
	0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 /opt/datachannel/bin/cnsw
  > 	/dev/null  2>&1
  1,6,11,16,21.26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw 
  > 	/dev/null  2>&1
  2,7,12,17,22.27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw
  > /dev/null 2>&1
  3,8,13,18,23.28,33,38,43,48,53,58 1-31 1-12 0-6 /opt/datachannel/bin/amgrw 
  > /dev/null 2>&1
  4. Copy the lines in the dc.cron file to the clipboard.
  5. At another shell prompt, edit the crontab for the current user.
    export EDITOR=vi
crontab -e

    A text editor session opens, showing the current crontab settings.

  6. Paste the lines from the dc.cron tab into the crontab file. For example:    
    
0 * * * * [ -f /opt/datamart/dataMart.env ] && [ -x /opt/datamart/bin/pollinv ]
	&& ....
  0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 /opt/datachannel/bin/cnsw >
	/dev/null  2>&1
  1,6,11,16,21,26,31,36,41,46,51,56 1-31 1-12 0-6 /opt/datachannel/bin/logw >
	/dev/null  2>&1
  2,7,12,17,22,27,32,37,42,47,52,57 1-31 1-12 0-6 /opt/datachannel/bin/cmgrw >
	/dev/null 2>&1
  3,8,13,18,23,28,33,38,43,48,53,58 1-31 1-12 0-6 /opt/datachannel/bin/amgrw >
	/dev/null 2>&1
  7. Save and exit the crontab file.
  8. Repeat steps 1 to 8 on each DataChannel host, with this difference:

    The dc.cron file on collector and loader hosts will have only one line, like this example:   

    
0,5,10,15,20,25,30,35,40,45,50,55 1-31 1-12 0-6 
/opt/datachannel/bin/amgrw > /dev/null 2>&1

    On such hosts, this is the only line you need to add to the pvuser crontab.