Personal tools
You are here: Home Documentation Monitoring and Information Services
Document Actions

Monitoring and Information Services

by admin last modified 2006-01-05 01:50

A short description on installing the various monitoring and information services.

GridCat

GridCat is not really a program that you run on the CE.  Rather, it is a package that is run centrally which sends out a batch of verification scripts to all registered sites.  The purpose is twofold - first, it is an easy way to check your site is working, and also serves as a catalog of all OSG sites.  The most important GridCat instances are the following:

MIS-CI

The Monitoring and Information Services Core Infrastructure (MIS-CI) provides information on the site environment and computing resources. The OSG-CE package includes MIS-CI. This section describes how to configure MIS-CI if you wish to enable it.  Note that MIS-CI depends on the sqlite database and will emit a cryptic "Database is locked" error if your OSG directory is on NFS.  Be forewarned.

The $VDT_LOCATION/MIS-CI/configure-misci.sh script performs the configuration. It creates or adds a crontab for the MIS-CI information collectors. As root, execute:

cd $VDT_LOCATION 
. setup.sh
$VDT_LOCATION/MIS-CI/configure-misci.sh
$VDT_LOCATION/MIS-CI/configure-misci.sh has the option --choose_user . If a different user is preferred to the default user which is chosen by MIS-CI (ivdgl), please configure MIS-CI using this option instead of above command:
$VDT_LOCATION/MIS-CI/configure-misci.sh --choose_user 

After finishing configuring the MIS-CI, a few checks might be necessary:

1. Check if crontab is created as root, as ivdgl user, or as any other user chosen, e.g.:

#crontab -u ivdgl -l

2. If you want to force an MIS-CI table update (due to fresh install or update), then, as the MIS-CI user, execute:

$VDT_LOCATION/MIS-CI/sbin/run-mis-ci.sh 

3. As a non-root user, check if at least one table is filled (If you chose not to force an update, it might take 10 minutes or so before the tables are filled with current information.)

grid-proxy-init
globus-job-run <hostname>/jobmanager-mis /bin/sh "siteinfo"
#(Here <hostname> is the CE hostname.)
On alliance.unl.edu, the output of this command looks like this:
$ globus-job-run alliance.unl.edu:/jobmanager-mis /bin/sh "siteinfo"
id 1
ymdt Wed Jul 27 14:00:00 UTC 2005
sitename Nebraska
hostname localhost
VOname uscms:50 local:25
appdir /opt/osg/app
datadir /opt/osg/data
tmpdir /opt/osg/tmp
wntmpdir /tmp
grid3dir /opt/osg/osg-021
jobcon condor
utilcon fork
locpname1
locpname2
ncpurunning 5
ncpus 34

MonALISA


The setup of MonALISA is done with the assistance of the configuration script. However there are two files which need to be edited. The $VDT_LOCATION/MonaLisa/Service/CMD/site_env script must be modified manually to set the location of the batch queue. In addition, the $VDT_LOCATION/MonaLisa/Service/VDTFarm/vdtFarm.conf file must be updated for the new TracePath module. Instructions on how to edit these two files are below, following the configuration script.

  • Run the configuration script $VDT_LOCATION/vdt/setup/configure_monalisa.sh to set up MonALISA.
> $VDT_LOCATION/vdt/setup/configure_monalisa.sh


Please specify user account to run MonaLisa daemons as: [daemon]:

This is the name you will be seen by the world, so please choose
a name that represents you. Make sure this name is unique in the
MonaLisa environment.

Please specify the farm name [hostname.domain.tld]: UNIQUE_NAME

Your Monitor Group name is important to group your site correctly
in the global site list. OSG users should enter "OSG".

Please enter your monitor group name [hostname.domain.tld]: OSG
...
...
...

Fill in your site specific information. NOTE: Check your latitude and longitude entries! If you are in the Americas, for example, your longitude will be a negative number. Typical continental U.S. latitudes range from 25 to 55 degrees and longitudes range from -60 to -120 degrees. If you get it wrong, your site will not show up properly in MonALISA.

Please review the information:

MonaLisa user: daemon
Farm name: UNIQUE_NAME
Monitor group: OSG-ITB
...
...
...

Is this information correct (y/n)? [n]: y
  • Edit the site_env file To have MonALISA interact with the local batch queuing system, the file $VDT_LOCATION/MonaLisa/Service/CMD/site_env needs to specify the location of the local installation directories.
  • Edit the vdtFarm.conf file

The Tracepath module lets you trace network activity near your cluster. Edit the file $VDT_LOCATION/MonaLisa/Service/VDTFarm/vdtFarm.conf to add the following line:

*Tracepath{monTracepath, localhost, " "}
If ganglia is installed and working on host "alliance", port 8649, then add the following line to vdtFarm.conf:

*PN_vdt{monIGangliaTCP, alliance, 8649}%30
  • Start Monalisa
/etc/init.d/MLD start
MonaLisa has some simple self-upgrading capabilities.  I have instructions on how to use them on this page.

Powered by Plone, the Open Source Content Management System