MARS

the Monitoring Application for Resources and Servers

User's Guide, Version 1.4.1

February 27, 2001

(minor revisions to User's Guide, Version 1.4, June 7, 1999)


Table of Contents


What's New in 1.4.1

MARS is substantially unchanged from version 1.4 of June, 1999. However, the build and distribution systems have completely changed. MARS 1.4.1 is distributed without source code by default; a separate source tree with a Makefile is distributed as a separate package. This makes working with the MARS source somewhat easier, and requires minor changes to documentation.

What's New in 1.4

Several things have changed in MARS 1.4.

Installing MARS

Before installing MARS, you should ensure that you have the following installed on your system:

for UNIX systems

To install MARS on a UNIX system, follow these steps:
  1. Download the MARS distribution in .tar.gz form.
    The most current version of MARS is always available via anonymous FTP at ftp.altara.org.
  2. Unpack the MARS distribution where you want to install it.
    MARS will run in any directory, and installing it as root is unnecessary (and not recommended, as you should not need to run MARS with root permissions). We recommend unpacking MARS in your home directory. To do this using GNU tar (the version of tar available on most Linux systems), type the following commands:

    mv mars-current.tar.gz ~
    cd ~
    tar xvzf mars-current.tar.gz

    To do this using a version of tar that cannot automatically uncompress archives, use the following commands:

    mv mars-current.tar.gz ~
    cd ~
    gunzip mars-current.tar.gz
    tar xvzf mars-current.tar

  3. Set the symbolic link for runmars
    The Java 1.2 interpreter needs to be invoked differently from the Java 1.1.7 interpreter. If you're running Java 1.1, set the runmars symbolic link to point to the runmars-1.1 script. If you're running Java 1.2 or 1.3, set the runmars symbolic link to point to the runmars-1.2 script. The following command should work on most Unices:

    ln -sf runmars-version runmars

MARS is now ready to run!

for Microsoft systems

To install MARS on a Microsoft system (Windows 9x, Windows NT), follow these steps:
  1. Download the MARS distribution in .zip form.
    The most current version of MARS is always available via anonymous FTP at ftp.altara.org.
  2. Unpack the MARS distribution where you want to install it.
    You'll need PKZIP, WinZip, or some other utility capable of opening .zip files.
MARS is now ready to run.

Installing SPOTS

SPOTS (for "Something Placed on That System", in.spotsd in the MARS distribution directory) needs to be installed on each machine for which you want extended information (free disk space, memory, and load average). SPOTS currently has built-in support for Linux, Solaris, IRIX, HP/UX, Digital UNIX, and AIX variants of UNIX. Before installing SPOTS on a system to be monitored, ensure that the following are installed on the machine: To install SPOTS on a machine meeting these requirements, follow these steps:
  1. Copy in.spotsd to a directory on the server system.
    We recommend the system path /usr/local/sbin. The rest of this installation example will assume this is the SPOTS installation location.
  2. Make sure in.spotsd has the proper permissions
    in.spotsd should be world readable and executable. To ensure this, type:

    chmod 555 /usr/local/sbin/in.spotsd

  3. Add the following line to the server system's /etc/inetd.conf file:

    24210 stream tcp nowait nobody /usr/local/sbin/in.spotsd in.spotsd

  4. Restart inetd
    Consult your UNIX documentation for directions on restarting inetd. On RedHat Linux systems, the following command will work:

    killall -HUP inetd

SPOTS is now configured to give disk space, memory, and load average information to your MARS client.

Introduction to MARS

This section will walk you through your first time running MARS. It covers the initial configuration of a new MARS installation, including adding hosts to the system and selecting services on those hosts. There is not much to actually using MARS, as it runs without intervention, automatically probing the hosts it knows about. After this introduction, you should have a pretty good feel for how MARS works.

Starting MARS

On UNIX systems, change to the MARS installation directory and type ./runmars to start MARS.

On Microsoft systems, double-click the MARS.jar icon in the MARS installation directory to start MARS.

Simple, isn't it?

Initial Configuration

The first time you start MARS, the host display will contain no hosts. In order to add hosts to the system, select Configure from the File menu. This will bring up an empty configuration window.

To add a host to the configuration, select Add Host from the Host menu. This will bring up a dialog box asking you for the fully-qualified domain name of the host to add. Enter a host name; in this example, we'll use discworld.altara.org. Click the OK button or press return after you have entered the host name. This will bring up another dialog box asking you for the host's name as it should appear in the host table. This is how the host will be displayed in the host display and in the configuration window. Notice that the default name is the first part of the host's fully qualified domain name; this is usually what you want, so you can generally click OK again.

The dialog box will disappear, and the host name will now appear in the configuration window with a row of seven checkboxes, one for each service MARS can probe, and one for SPOTS. Check or uncheck these boxes depending on whether the corresponding service is enabled on the system. For the discworld example, you can check all the boxes.

NOTE: You may have to click a checkbox twice to get it to check or uncheck. We haven't figured out what causes this; we believe it's a bug in Swing 1.1.
You can go ahead and repeat the add host procedure for any other hosts you want to monitor.

When you're done, close the configuration window and save your changes by selecting Save from the configuration window's File menu. Click OK in the confirmation dialog box that comes up. The configuration window will disappear, and the new host(s) will be displayed in the host display. The status bar in the main window will change momentarily to show you what MARS is doing, and when MARS has finished probing the host(s) you specified, it will display the status of services and SPOTS information for those hosts.

To quit MARS, you can either click the host display's close box or select Quit from the File menu.


MARS Reference

MARS consists of two windows, a host display and a configuration window. All of MARS' features can be accessed via these windows.

Host Display

The Host Display


The host display is the "core" of the MARS user interface. It consists of a menu bar, a table displaying the status of all the hosts MARS is probing, and a status bar along the bottom of the window.

Along the top of the table are the services MARS can probe, and down the left is a list of hosts MARS has been configured to monitor. The status cells can have one of four possible values:

The SPOTS cells will either display the load average and percentage of disk space free, display "down" (if SPOTS could not be contacted), or be grayed out (if SPOTS is not enabled on the host).

You can click on any service status cell to get a detailed view of the last response received from that service. This can help you to determine which if a "t/o" status is really a timeout, or a service configuration error. You can also click on a host's disk space cell to get a detailed view of free space per filesystem on the host.

Detailed Service and Filesystem Information


The status bar along the bottom of the host display tells you what MARS is doing. Since MARS is multi-threaded, and can probe multiple services at once, the status bar will only show the most recent action MARS started. The following messages can be displayed in the status bar:

There are two menus in the host display, File and Control.

Configuration Window

The Configuration Window


The configuration window allows access to every configurable aspect of MARS. It consists of a menu bar and a host/service table.

Along the top of the table are the services MARS can probe for each host, and down the left is a list of hosts MARS has been configured to monitor. You can enable and disable probing of services on specific hosts by checking and unchecking the boxes in the center of the table. Enable and disable display of all SPOTS information by checking and unchecking the SPOTS box for each host.

The menus allow you to modify the host table itself, and to configure other aspects of MARS' behavior. There are three menus in the configuration window, File, Host, Adjust, and Notification.

Warnings

MARS' three warnings


MARS can display three types of warnings to let you know there is a problem.

If you have configured mail notification, MARS will send an e-mail message to the address you specified each time an alert is displayed. MARS encodes relevant information about the error in the alert message's subject; this makes the feature useful for e-mail based paging systems. If MARS is configured to send mail notification but cannot for some reason, it displays the following alert:

Mail notification failure warning

what's an fqdn?

FQDN (Fully-Qualified Domain Name) refers to the entire domain name of a machine. If a machine's host name is foo, and its domain is bar.com, the FQDN is foo.bar.com. MARS needs FQDNs to find machines; a node name or Windows (NetBIOS) name will not do.

Hacking MARS

The MARS source is distributed as a separate package, and is available at http://www.altara.org/mars/dist/mars-src-current.tar.gz. The MARS source is documented using Javadoc, so you can use the Javadoc tool to automatically generate detailed source documentation. MARS' Makefile contains several useful targets:
This User's Guide is ©1999, 2001 Brian H. Trammell. Unlimited redistribution is permitted and encouraged. If you hack MARS and wish for us to distribute your changes, it would be most helpful to us if you hacked the relevant bits of this manual, too.