Monitoring the RHN Server
159
for each of your systems. Although the default values provided for probes may suit you, every
organization has a different environment that may require altering thresholds.
7.5.3. Monitoring the RHN Server
In addition to monitoring all of your client systems, you may also use RHN to monitor your RHN
Server, whether that be an RHN Satellite Server a RHN Proxy Server. To monitor your RHN Server,
find a system monitored by the server, and go to that system's
System Details � Probes
tab.
Click
create new probe
and select the
Satellite
Probe Command Group. Next, complete the
remaining fields as you would for any other probe. Refer to
Section 7.5.1, “Managing Probes”
for
instructions.
Although the RHN Server appears to be monitored by the client system, the probe is actually run from
the server on itself. Thresholds and notifications work normally.
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 following 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
.
Содержание NETWORK SATELLITE 5.1.1 - RELEASE NOTES
Страница 1: ...Red Hat Network Satellite 5 1 1 Reference Guide Red Hat Network Satellite ...
Страница 10: ...x ...
Страница 30: ...Chapter 2 Red Hat Update Agent 18 Figure 2 11 Available Package Updates ...
Страница 46: ...34 ...
Страница 68: ...56 ...
Страница 162: ...150 ...
Страница 174: ...162 ...
Страница 186: ...174 ...
Страница 259: ...247 Appendix D Revision History Revision History Revision 1 0 ...
Страница 260: ...248 ...
Страница 268: ...256 ...