Version 13 (modified by 12 years ago) (diff) | ,
---|
How to configure Plastic Slices monitoring on a MyPLC server
Introduction
This page explains how to configure a MyPLC server for the Plastic Slices central monitoring configuration. This page was written for
tango-monitor-myplc-0.5-1
which is the latest version of the monitoring utilities for a MyPLC server running Fedora 8 or Fedora 12. It may not work well with older versions.
Upgrading from version 0.3
If you are currently running plastic-slices-monitor-myplc-0.3
or later, you need to do the following steps of this upgrade:
- II. Install the monitoring software itself
- IV. Test the new script and make sure it still works
- V. Install the scripts to run from cron: the script paths have changed, so you will need to update your crontab.
If you are installing tango-monitor-myplc
for the first time or upgrading from an earlier version, read all sections to see which steps you need to take.
Variables
<cronuser>
: The user as which to run the monitoring on MyPLC. The scripts can run as root, or as a non-root user of your choice. (At GPO, we use theganglia
user.)<site>
: a one-word phrase describing your site, probably the name of your university or lab (e.g.stanford
,gpolab
). Use the same value for all hosts your site is monitoring.<fqdn>
: The fully-qualified domain name as which your MyPLC should report data. IF this is not the same as the output ofuname -n
on your node, pay attention to section IV below.
Steps to configure MyPLC monitoring
I. Prepare to submit authenticated monitoring data to GMOC
You need to do these steps if you are installing monitoring for the first time, or if you are upgrading from version 0.1.
- Register site credentials: IF you have not yet registered your site to submit data to GMOC, follow the instructions at GENIMetaOps/SiteCredentials. All site resources use the same credential; you only need to do this step once for your entire site. Note: the password you use for your site registration is a new password generated for the purpose of submitting monitoring data. Do not reuse any existing passwords from your site.
- Store your site password in a file which MyPLC monitoring can use:
sudo touch /usr/local/etc/monitoring_passwd sudo chown <cronuser> /usr/local/etc/monitoring_passwd sudo chmod 600 /usr/local/etc/monitoring_passwd sudo vi /usr/local/etc/monitoring_passwd
Add exactly one line to this file, containing the site monitoring password you registered with GMOC.
II. Install the monitoring software
Do all of these steps every time you install or upgrade the monitoring software.
- Download the
tango-monitor-myplc-0.5-1.noarch.rpm
file from http://software.geni.net/local-sw/, and copy it onto your MyPLC host, e.g. into~/tango-monitor-myplc-0.5-1.noarch.rpm
.
- Use yum localinstall to install the RPM and any necessary dependencies:
sudo yum localinstall ~/tango-monitor-myplc-0.5-1.noarch.rpm
III. Create required directories and files
These steps only need to be done the first time you install the monitoring software.
- Create required directories:
sudo mkdir -p /var/spool/rrds/$(uname -n) sudo mkdir -p /var/spool/rrds/REPORT sudo chown -R <cronuser> /var/spool/rrds
- IF
uname -n
does not report your node's FQDN for whatever reason, create a symlink so that reporting and reading scripts can find your RRD files:cd /var/spool/rrds sudo ln -s $(uname -n) <fqdn>
IV. Test the script
Run the monitoring and submission scripts by hand to make sure they work.
- Check the time on your MyPLC server, and make sure it is accurate. The timeseries data reporting format relies on clock accuracy, so your nodes must be running ntpd (or ntpdate regularly out of cron) in order for monitoring to work.
- Run the metric-gathering script by hand to make sure it works:
sudo -u <cronuser> /usr/bin/metric_plc
- This should produce no output
- After this runs, a number of RRD files should be created in
/var/spool/rrds/$(uname -n)
- Run the data reporting script by hand to make sure it works:
sudo -u <cronuser> /usr/bin/report_data_to_gmoc <site> <fqdn>
- This should produce no output
- You should be able to browse to http://gmoc-dev.grnoc.iu.edu/api-demo/data/, view data by Location, select your site, and find an entry for
<fqdn>
.
V. Install the scripts to run from cron
This only needs to be done the first time you install the monitoring software.
Add the two scripts to cron: modify the <cronuser>
crontab:
sudo -u <cronuser> crontab -e
and add the new lines:
*/1 * * * * /usr/bin/metric_plc */5 * * * * /usr/bin/report_data_to_gmoc <site> <fqdn>