These notes describe how to restart the CMLOG system processes and the ERR processes.
The CMLOG processes on lcls-daemon2 are the following:
Although not a part of the CMLOG system, the ALH and Channel Watcher processes running on lcls-daemon2 must be restarted after the cmlogClientD process is restarted in order for the ALH and Channel Watcher processes to be able to log messages.
This script performs the following actions:
Note that this script does not need to be modified when new Channel Watcher instances are added or removed. The script determines which Channel Watcher processes are currently running (from information obtained through a UNIX "ps" command) and restarts them using the associated system startup commands in the lcls-daemon2 /etc/init.d directory.
It is advisable to request permission from the current EOIC before restarting the CMLOG system and related processes. However, experience has shown (confirmed by feedback from EOICs) that restarting the CMLOG system and related processes using the Controls UNIX Watchdog GUI does not adversely affect Operations.
The following steps can be followed to invoke the Controls UNIX Watchdog GUI and to find the button to restart the CMLOG system and related processes:
uwd -> Controls_UNIX_Watchdog -> Controls_Servers right arrow -> lcls-daemon2 right arrow -> PROC ->CMLOG SYSTEM RESTART "P" button
The actions resulting from restarting the CMLOG system and related processes take approximately three minutes to complete. This is due to the large number of processes that are stopped and then restarted (with waits of 5 seconds after a process is restarted). Most of these processes are Channel Watcher processes.
As noted above, the CMLOG system processes (with the ALH and Channel Watcher processes) are usually restarted by a single button push on the Unix Watchdog GUI. This procedure describes a manual procedure for restarting these processes.
As noted above, if the cmlogClientD process is restarted, the ALH process and the Channel Watcher processes must be restarted in order for them to log messages.
To stop and restart the ALH process:
There is a separate Channel Watcher system startup file for each Channel Watcher process. Channel Watcher system startup files have names of the form:
The Err logging processes, errClient and oocCosEventService, run on mccas0 and are required to log Aida messages. They may need to be restarted if Aida messages are not being logged. There are two methods of restarting these processes: (1) using system startup files on mccas0, and (2) using the errmanager script.
Occasionally a problem occurs with the cmlogClientD process on mccas0, which is started by errClient process. If Aida messages are not being logged after restarting the Err logging process, kill the cmlogClientD process(es) on mccas0 and then restart the Err logging processes again.
Perform the following (e.g., on a machine such as flora or tersk):
Author: Bob Hall 04-Jun-2008 Modified: Jingchen Zhou 01-June-2012
Revision: Bob Hall 03-Jan-2008 Added errmanager information.
Revision: Bob Hall 27-Mar-2012 Updated information including starting CMLOG with button press.
Modified: Jingchen Zhou 01-June-2012