Installation guide

Important

Red Hat Satellite RPMs expect the Cobbler kickstart and snippet directories to be in their

default locations, do not change them.

5.12. Monitoring

Are there any diagnostic tools that help determine the cause of monit oring errors?

Though all monitoring-related activities are conducted through the Satellite interface, Red Hat

provides access to some command line diagnostic tools that may help you determine the cause of

errors. T o use these tools, you must be able to become the nocpulse user on the Satellite

conducting the monitoring.

First log into the Satellite as root. T hen switch to the nocpulse user with the following command:

su - nocpulse

To thoroughly troubleshoot a probe, you must first obtain its probe ID. You may obtain this

information by running rhn-catalog on the Red Hat Satellite Server as the nocpulse user. T he

output will resemble:

2 ServiceProbe on example1.redhat.com (199.168.36.245): test 2

3 ServiceProbe on example2.redhat.com (199.168.36.173): rhel2.1 test

4 ServiceProbe on example3.redhat.com (199.168.36.174): SSH

5 ServiceProbe on example4.redhat.com (199.168.36.175): HTTP

The probe ID is the first number, while the probe name (as entered in the Satellite interface) is the

final entry on the line. In the above example, the 5 probe ID corresponds to the probe named

HTTP.

Further, you may pass the --com mandline (-c) and --dum p (-d) options along with a probe ID

to rhn-catalog to obtain additional details about the probe, like so:

rhn-catalo g --commandline --dump 5

The --com m andline option yields the command parameters set for the probe, while --dum p

retrieves everything else, including alert thresholds and notification intervals and methods.

The command above will result in output similar to:

5 ServiceProbe on example4.redhat.com (199.168.36.175 ):

linux:cpu usage

Run as: Unix::CPU.pm --critical=90 --sshhost=199.168.36.175

--warn=70 --tim eout=15 --sshuser=nocpulse

--shell=SSHRemoteCom mandShell --sshport=4545

Now that you have the ID, use it with rhn-runprobe to examine the probe's output.

How do I interpret the output of rhn-runprobe?

Now that you have obtained the probe ID with rhn-catalog, use it in conjunction with rhn-

Chapter 5. Troubleshooting