-
Unpack the distribution tarball:
gunzip -dc remstats.tar.gz | tar xf -
-
create the remstats user and group, if you haven't already,
(by default
remstats
and remstats
respectively.) (See also
the remstats user.)
-
Build and install the software. If you're upgrading, you
might want to take a copy of fixup.config from the old version:
sh configure
If you want to override the defaults, then run
sh configure --help
for a list of what can be overridden.
[Check fixup.config to make sure it is properly setup.]
make all
make install
su -c 'make install-suid'
Note: this step also customizes the programs and documentation
with your choice of directories, owner, ... so this documentation
should refer to your setup after you've done the install.
The make install-suid
simply makes traceroute and multiping suid root.
They won't work most places unles run as root, one way or another. Since I
don't like to run all of remstats as root, this was the best compromise I
could come up with.
-
fix the config-base for site-specific things. Edit the following
files in /home/users/t/te/terskine/projects/remstats/etc/config-base, looking the the string "FIXME", without the "quotes".
alerts general html scripts/http-proxy
I'll try to keep this list up to date, but you can make sure by doing:
grep -l FIXME /home/users/t/te/terskine/projects/remstats/etc/config-base/* /home/users/t/te/terskine/projects/remstats/etc/config-base/*/*
-
Make a config-dir to describe what you
want to monitor. You can do this by hand, or using the configuration
building tools. To use the tools, you'll have to make a few files
listing various kinds of hosts:
cd /home/users/t/te/terskine/projects/remstats/etc
/home/users/t/te/terskine/projects/remstats/bin/new-config config
/home/users/t/te/terskine/projects/remstats/bin/new-ping-hosts groupname1 group1-hosts-file
/home/users/t/te/terskine/projects/remstats/bin/new-ping-hosts groupname2 group2-hosts-file
...
/home/users/t/te/terskine/projects/remstats/bin/new-port-hosts groupname3 port-hosts-file
/home/users/t/te/terskine/projects/remstats/bin/new-snmp-hosts groupname4 SNMP-community-string snmp-hosts-file
After you've installed the unix-status-server on some hosts, you can also
use:
/home/users/t/te/terskine/projects/remstats/bin/new-unix-hosts groupname5 unix-hosts-file
If you're going to use the log-collector, you'll have to build the
rrd entries for each by hand. There doesn't seem to be much standard
in where log-files go, let alone what's in them.
-
Arrange for cron to run
run-remstats
at an appropriate interval.
For a five-minute interval, something like the following will do:
0,5,10,15,20,25,30,35,40,45,50,55 * * * * /home/users/t/te/terskine/projects/remstats/bin/run-remstats
-
[optional] Arrange for cron to run
do-traceroutes
at an appropriate
interval. You could run it in the wee hours of each morning like:
5 3 * * * /home/users/t/te/terskine/projects/remstats/bin/do-traceroutes
This information isn't currently used, but I'm planning to make use of it.
-
[optional] Arrange for cron to run snmpif-description-updater
periodically, if you have any snmpif-* RRDs, which you're likely to change
the descriptions on. Say every day, like:
0 3 * * * /home/users/t/te/terskine/projects/remstats/bin/snmpif-description-updater
-
Arrange for cron to run cleanup every now and then to remove old
un-needed files, like:
0 3 * * * /home/users/t/te/terskine/projects/remstats/bin/cleanup
-
You'll need to set up your web-server to allow
CGI scripts in the remstats html tree and make sure that you're not
allowing everyone in.
-
Make a symlink in the html directory from whichever index
you prefer to index.cgi.
-
You'll want to look at the server installation docs
if you're going to be running any of the remote servers (
log-server, nt-status-server, remoteping-server, and
unix-status-server).
Enjoy your pretty pictures and I hope that you find them usefull.