Red Hat NETWORK 4.0 -, Справочное руководство

Страница: 183 / 290

Chapter 7. Monitoring 167
Note
Any probes that require Red Hat Network Monitoring Daemon connections cannot be
used against a RHN Satellite Server or RHN Proxy Server on which Monitoring software
is running. This includes most probes in the Linux command group as well as the Log
Agent probes and the Remote Program probes. Use the Satellite command group probes
to monitor RHN Satellite Servers and RHN Proxy Servers. In the case of Proxy scouts,
the probes are listed under the system for which they are reporting data.
7.6. Troubleshooting
Though all Monitoring-related activities are conducted through the RHN website, Red Hat
provides access to some command line diagnostic tools that may help you determine the
cause of errors. To use these tools, you must be able to become the nocpulse user on the
RHN Server conducting the monitoring.
First log into the RHN Server as root. Then switch to the
nocpulse user with the follow-
ing command:
su - nocpulse
You may now use the diagnostic tools described within the rest of this section.
7.6.1. Examining Probes with
rhn-catalog
To thoroughly troubleshoot a probe, you must first obtain its probe ID. You may obtain this
information by running
rhn-catalog
on the RHN Server as the nocpulse user. The
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 RHN website) 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
--commandline
(
-c
) and
--dump
(
-d
) options along with a
probe ID to
rhn-catalog
to obtain additional details about the probe, like so:
rhn-catalog --commandline --dump 5