Theodolites are the basic monitoring fuctionality. Theodolites should run on hosts located as near as possible to the router at the border of your domain: in the simplest case, you will have one monitoring host running a single theodolite. The border of the domain should be defined so that the connectivity within the domain is, as a general rule, better than between domains.
In case you have more than one router to different WANs you might specify several theodolites, but you should also tell us other routing infos. For the now, one theodolite should be sufficient, and its location should be found by compromise.
Hosts running theodolites need not to be specially equipped: instead, they
may have quite modest capabilities. The following might be considered as typical:
# cat /proc/cpuinfo
processor: 1
vendor_id: GenuineIntel
cpu family: 6
model: 8
model name: Pentium III (Coppermine)
stepping: 3
cpu MHz: 797.380
cache size: 256 KB
Network interfaces should be adequate to the infrastructure inside the domain. Hard disk capacity is not an issue: 10 GB is Ok.
The computational load of a theodolite is minimal, but its activity relies on a fast response. Therefore it is inappropriate to install the theodolite on a host with a high computational load.
You will receive a "welcome aboard" reply to your mail containing the IP addresses of the hosts that run your theodolites. The reply contains a tar attachment gridice-theodolite-custom-<date>.tar where <date> is used for versioning. Save that file and proceed selecting between:
You can later inspect your installation using the log of the daemon that controls the theodolite(s) (/opt/GlueDomains/var/log/*.thd) or those that log the activity of the monitoring sessions (same directory).
The following step by step howto applies to Scientific Linux SLC303 installed from scratch with boot CD + NFS/HTTP. You can probably skip the first two steps if your host already runs Scientific Linux, or you can adapt the OS install part with your preferred OS install system.
The following steps are needed to install the required software (or use this untested quattor template):
iperf-1.7.0-cern1 compat-gcc-c++-7.3-2.96.123 compat-gcc-7.3-2.96.123 compat-libstdc++-7.3-2.96.123 compat-libstdc++-devel-7.3-2.96.123 perl-DBI-1.32-5 perl-DBD-MySQL-2.1021-3 mysql-3.23.58-2.3
# cd /usr/include; h2ph -r -l . # cd /tmp # wget ftp://ftp.di.unipi.it/pub/Papers/ciuffoletti/gluedomains/install.sh # chmod u+x install.sh # ./install.sh mdstheodolite
Unpack the configuration tarball you received with the welcome mail:
# tar -xv -C / -f gridice-theodolite-custom-<DATE>.tar
When installation is complete, start GlueDomains with:
# service gluedomains startand activate it at system startup with:
# chkconfig gluedomains on
Installation is at present fully supported for Linux RedHat7.3. RedHat and external rpms that are needed to satisfy GlueDomains dependencies are available here. To get support for Linux Debian contact Augusto Ciuffoletti.
The following steps, tested for a Linux RedHat 7.3 should bring your theodolites up and running on the target host:
Follow the instruction sections INSTALLATION for theodolite in the document README.html. In a nutshell:
# cd /usr/include; h2ph -r -l . # cd /tmp # wget ftp://ftp.di.unipi.it/pub/Papers/ciuffoletti/gluedomains/install.sh # chmod u+x install.sh # ./install.sh mdstheodolite
Unpack the configuration tarball you received with the welcome mail:
# tar -xvf gridice-theodolite-custom-<DATE>.tar -C /
When installation is complete, start GlueDomains with:
# service gluedomains startand activate it at system startup with:
# chkconfig gluedomains on
This part is still incomplete: you should start with a RedHat 7.3
installed with a PlainGRIS-cfg.h profile, and next follow the
instructions for installation
without LCFG.
If you are running Red Hat 7.3, you should consider this upgrade as an opportunity to switch to Scientific Linux, and to reinstall GlueDomains from scratch.
Prior to upgrading your software, stop GlueDomains with:
# service gluedomains stop # killall -9 mdsproxy.pl
next:
# cd /tmp # wget ftp://ftp.di.unipi.it/pub/Papers/ciuffoletti/gluedomains/install.sh # chmod u+x install.sh # ./install.sh mdstheodoliteYou may also want to check whether an upgrade is required for the configuration tarball: you should be notified about this, and the mail should contain the new tarball. In case, save the attachment and run:
# tar -xv -C / -f gridice-theodolite-custom-DATE.tarusing the appropriate DATE. Finally restart:
# service gluedomains start
[root@myhost /]# service gluedomains start Launching MDS proxy mdsproxy.pl On interface 123.123.123.123: theodolite a (started) theodolite a (running) theodolite a (running) ... On interface 127.0.0.1: [root@lcgui /]# Can't locate sys/syscall.ph in @INC (did you run h2ph?) (@INC contains: /opt/GlueDomains/lib/GISplugin /opt/GlueDomains/lib ...You probably forgot to run
# cd /usr/include; h2ph -r -l .Just do it.
[root@myhost /]# service gluedomains start Launching MDS proxy mdsproxy.pl On interface 123.123.123.123: ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) On interface 127.0.0.1: ERROR 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)You probably forgot to install the configuration tarball: do it now.
[root@myhost root]# /opt/GlueDomains/gluedomains start Launching MDS proxy mdsproxy.pl On interface 123.123.123.123: ERROR 1129: Host 'myhost' is blocked because of many connection errors. Unblock with 'mysqladmin flush-hosts'A known problem on GlueDomains server: send an email to Augusto or to Alessandro