Killing Everything

From tigwiki

Jump to: navigation, search

Contents

[edit] Why you might need to do this

In the August 2005 runs we ran into a rash of situations where the DAQ system hung up and the only way to get things going was to kill everything, then start it all up again.

[edit] First things first

Stop a run if it is in progress.

[edit] Clients -- identifying and killing them

Typically there are five clients running on a "normal" 8pi system.  You have to kill all five of them.

Four of these clients run on grsmid00 and have the following process names:

  • mhttpd
  • mlogger
  • analyzer
  • fe_epics

the fifth, which is the front-end code, runs on lxdaq02:

  • 8pi

You can search for each process name:

  • First ssh to the appropriate machine.  This should only be necessary for 8pi running on lxdaq02. 
   ssh lxdaq02
  • To search for the process, you can use ps 
   ps x | grep name .
  • You will get a listing of process information.  The first column is the process number, and the last column is how the process was invoked (i.e how it was run).  The ps process is the one you just ran, so ignore it.  Real DAQ processes may be invoked as (e.g.) /usr/local/bin/name, or ./name, and may have some extra arguments along with them.  
  • Make a note of all the process numbers that are likely real DAQ processes.
  • For each process number: 
   kill -9 number.

A sample session on grsmid00 for killing mhttpd: 

eightpi@grsmid00> ps x | grep mhttpd
14525 ?        SN     0:00 mhttpd -p 8081 -D
14529 pts/7    S      0:00 grep mhttpd
eightpi@grsmid00> kill -9 14525

[edit] Mservers -- identifying and killing them

The mserver processes are called mserver.  They can be killed the same way as the client processes, with two caveats:

  • The mserver processes are almost always invoked as 
   /usr/local/bin/mserver.
  • Often you will find processes called kmserver.  They are part of the windowing system.  DON'T kill them.

[edit] Cleanup

  • Start up an ODB editor.  From an isdaq08 command line, type 
   odbedit.
  • Type 
   shutdown all.

Make a note of any messages about clients needing to be killed manually.

  • Type 
   quit.
  • If there were any messages about clients needing to be killed manually, see if you can figure out what process names are attaced to those clients, and kill them the same way you killed everything else.  Often the "needs to be killed" message will include a PID which is the process number.
  • type in 
   odbedit 
   cleanup.
   quit.

[edit] Restart

Now you will have to start in order as listed below. Also see the MIDAS Clients Overview#MIDAS Components page. 

Then you can start a run.

You will likely also have to stop and restart the Running the Analyzer and On-Line Spectrum Viewer#GUI Spectrum Viewer Startup, too.

[edit] If this doesn't work

Repeat the process as far as Restart, then call Greg.

Retrieved from "http://www.triumf.info/wiki/tigwiki/index.php/Killing_Everything"
Personal tools
Experiment Pages