Quick Installation Guide

Below is the result of our efforts to be able to walk you through, step by step, the process of installing MiscSARGE on a central server and have it monitor your systems. Walk through it sequentially or hit the quick links to skip to the juicy bits. We've tried very hard to not leave anything out, but no one is perfect. If you're having problems, visit our support pages to see if your problem has already been addressed. If not, please, .

System Requirements

  • MiscSAR
  • MiscSAR is the data collection package that MiscSARGE was developed for. You can find the most recent version on our download page.

  • Hardware
  • Disk space for host performance data for 30 days, plus another .8 MByte of disk space of each disk for 30 days. A monitored host with 3 disks would require 5.0 Mbyte for 30 days of data.

  • Perl 5 (or greater)
  • Also, the following modules, all of which are available from http://www.perl.com

    Required Perl Modules

    Some of the above modules come with Perl while the others are available from the Perl website listed above.

    NOTE: We highly recommend using the following command to install dependancies as CPAN can sometimes cause unforseen problems with installations.

        sudo yum -y install "perl(Date::Calc)"

  • HTTP Server
  • Only if you want the graphs web accessible. The Apache webserver is used for development purposes.

  • Web Browser
  • For viewing files (Google Chrome, Mozilla Firefox, etc).

  • RRDTool
  • Installed with the RRD Perl modules in the system perl libraries. Avaliable at: http://oss.oetiker.ch/rrdtool/

  • MiscSARGE User
  • A generic user and group on all systems that will be used to collect data via the 'rsh' or 'ssh' command from the MiscSARGE server. .rhosts (or .shosts or ssh key exchange) must be configured to allow access without password prompting. (The account can have a disabled password.)

    user - miscsarge:x:3334:MiscSAR Graph Engine:/usr/local/miscsarge:/bin/bash
    group - miscsarge:x:3334:miscsarge

    NOTE: If you intend to use miscsarge to also monitor the 'server' machine, make sure that the key exchanges are also performed to allow passwordless 'remote' access from that machine to itself.


    Newer Versions of MiscSarge (Versions 0.0.10 and up)
  1. Make sure all of the above prerquisites are installed.
  2. Unpack the tarball.
  3. Edit the Makefile User Variables to satisfy your systems requirements.
  4. Type 'make install'.
  5. Change to the ${PREFIX}/miscsarge/bin/ directory.
  6. Rename "crontab" to "miscsarge" and move the file to the system's cron directory.
  7. Update the hosts.master file to include any hosts you would like to monitor.
  8. Run ./webgen to create the MiscSARGE we directory and documentation.
    Older Versions of MiscSarge (Versions before 0.0.10)
  1. Make sure all of the above prerequisites are installed.
  2. Unpack the tarball.
  3. Edit the $web_dir (line 26) and $sw_dir (line 27) variables in the sarge file to suit your environment.
  4. Ex. % cd miscsarge-{VERSION}/bin
         % vim sarge

  5. Edit the $web_dir (line 28) and $sw_dir (line 29) variables in the private file to match those is the sarge file.
  6. Ex. % vim private

  7. Edit the $web_dir (line 63) and $sw_dir (line 64) variables in the webgen file to match those is the sarge file.
  8. Ex. % vim private

  9. Edit the crontab file to match the $sw_dir is the sarge file.
  10. Ex. 5,20,35,50 * * * * /usr/local/miscsarge/bin/sarge > /dev/null 2>&1

  11. Edit the http.conf-miscsarge file to match the $web_dir is the sarge file.
  12. Ex. ScriptAlias /miscsarge/bin/ "/home/www/html/miscsarge/bin/"

  13. Create the $sw_dir and $web_dir directories.
  14. Ex. % mkdir /usr/local/miscsarge /home/www/html/miscsarge

  15. Copy the contents to the miscsarge directory.
  16. Ex. % cp -r ./miscsarge-{VERSION}/* $sw_dir

    Please consult the below configuration checklist if any issues arise. The list is comprimised of the most likely solutions
    to any problems after installation. Feel free to run 'make uninstall' at any point if you believe there has been an error.


  1. Edit the hosts.master file.
  2. Change directory to ${MiscSARGE_PREFIX}/miscsarge/bin and edit the hosts.master file.

    Ex. % cd /usr/local/miscsarge/bin
       % vim hosts.master

    The example hosts.master file provided documents the fields.

  3. Run webgen
  4. Ex. % ./webgen

  5. Create ${MiscSARGE_USER}
  6. Make sure that the ${MiscSARGE_USER} has been created on all hosts to be monitored, and that ${MiscSARGE_USER} can access the system without being prompted for a password. A simple test as ${MiscSARGE_USER} is a good idea ('rsh <remotehost>' is enough).

  7. Enable MiscSAR
  8. Make sure that MiscSAR is installed and activated on all systems to be monitored. MiscSAR is available as one of the packages provided by the NCAR Tools Group. MiscSAR may be installed, but not active. The 'enable_miscsar' script can be used to make entries into the appropriate crontabs to enable MiscSAR data collection.

    The RRDTool databases configured by MiscSARGE expect data samples every 5 minutes. Use the 'enable_miscsar' script on each host to be monitored to properly configure the crontab.

  9. Merge the httpd.conf files.
  10. Merge the 'httpd.conf-miscsarge' file with the web server httpd.conf file, the restart the webserver. (This only needs to be done once per installation, not after every configuration.)

  11. Run loadall.sh - OPTIONAL
  12. This will load historical MiscSAR data. Depending on the number of hosts and size of historical data, this could take a while (30 minutes plus).

    NOTE: This will only work if MiscSAR data has been previously collected in 5 minute sample times.

    Ex. % su ${MiscSARGE_USER}
       % ./loadall.sh

  13. Merge crontabs
  14. Merge the generated crontab with the ${MiscSARGE_USER}'s crontab.

That should be it. Congrats! You now have MiscSARGE installed. For questions and support, see our documentation page where you can get all kinds of useless helpful information, or .