next up previous contents index
Next: Generating the ORACLE Up: The VM FATMEN Previous: Generating the FATMEN

Monitoring the FATMEN servers

Privileged users may send the FATMEN servers management commands to monitor their progress, check that they are active etc. Examples of use are:

Jamie@Cernvm;
TELL FMDDDIVR QSPOOL
12:44:53  * MSG FROM FMDDDIVR: I HAVE 0 FILES IN MY RDR
Jamie@Cernvm;
TELL FMDDDIVR HELLO
12:44:58  * MSG FROM FMDDDIVR: HELLO AND HOW ARE YOU TODAY?
Jamie@Cernvm;
* See how much disk space CHARM2 service machine has used
TELL FMCHARM2 QDISK A
12:45:19 * MSG FROM FMCHARM2: LABEL  VDEV M STAT CYL TYPE BLKSIZE FILES  BLKS USED-(%) BLKS LEFT BLK TOTAL
12:45:19 * MSG FROM FMCHARM2: CHARM2 191  A R/W   20 3380    4096     6       35-01         2961      3000

 

HELLO Check whether server is active. If the server does not respond immediately, it means that it is either down, or processing an update. As multiple updates can be grouped together, it can happen that the server does not respond for a considerable period of time to a |HELLO| message.
HELP Displays this list of commands.
STOP Stop the server, but does not log it off.
QDISK Issue a |QUERY DISK| command and send the output back to the originator of the message.
QSPOOL Return the number of RDR files that the service machine currently has in its reader.
DROP Cause the server to call the |DROP| exec to drop the specified link.
GIME Cause an |EXEC GIME| to be issued.
CLOSE Close the console log and spool it to the owner of the service machine.
NEWLOG Cause the server to open a new log file.
PURGE Purge (delete) journal files. May be sent automatically whenever a backup of the FATMEN RZ file has been taken.
*FATLOG* This command is issued automatically from the FATMEN user code to log FATMEN activity.
LOGOFF Shutdown the service machines prior to system shutdown or other scheduled interruption, such as ORACLE backup.


Table: List of commands currently supported by the FATMEN service machine

Names file entries for the FATMEN Servers

Each FATMEN server should have at least two entries in their NAMES file. Those on CERNVM may also have a third, FATSERVERS, which points to the list of remote servers who should automatically receive updates from CERNVM.

The two entries that are always required are FATOWNERS and FATOPERATORS. At the present time, usernames in either of these lists are allowed to issue commands in the above table, and receive SMSGs when the servers stop.

Example of NAMES file for the FATMEN server

:nick.FATOPERATORS                :list.fatop1 fatop2
:nick.FATOP1                      :userid.console
                                  :node.cernvm
:nick.FATOP2                      :userid.opsutil
                                  :node.cernvm
:nick.FATOWN1                     :userid.fatone
                                  :node.cernvm
:nick.FATOWN2                     :userid.wojcik
                                  :node.frcpn11
:nick.FATOWNERS                   :list.fatown1 fatown2 jamie



next up previous contents index
Next: Generating the ORACLE Up: The VM FATMEN Previous: Generating the FATMEN


Janne Saarela
Mon May 15 09:59:59 METDST 1995