Red Hat Satellite 5.
Red Hat Satellite 5.
Legal Notice Copyright © 2013 Red Hat, Inc. T his document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Table of Contents Table of Contents .Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7. . . . . . . . . . 1. Audience 7 2. Document Conventions 7 2.1. T ypographic Conventions 7 2.2. Pull-quote Conventions 8 2.3. Notes and Warnings 9 3. Getting Help and Giving Feedback 9 3.1. Do You Need Help? 9 3.2. We Need Feedback! 10 .Chapter . . . . . . . . 1. . . .Red . . . .
Red Hat Satellite 5.6 Reference Guide 1.2.6.1.1. Probe Status ⇒ Critical 1.2.6.1.2. Probe Status ⇒ Warning 1.2.6.1.3. Probe Status ⇒ Unknown 1.2.6.1.4. Probe Status ⇒ Pending 1.2.6.1.5. Probe Status ⇒ OK 1.2.6.1.6. Probe Status ⇒ All 1.2.6.1.7. Current State 1.2.6.2. Notification 1.2.6.2.1. Notification ⇒ Filters 1.2.6.2.1.1. Notification ⇒ Notification Filters ⇒ Active Filters 1.2.6.2.1.2. Notification ⇒ Notification Filters ⇒ Expired Filters 1.2.6.3. Probe Suites 1.2.6.4. Scout Config Push 1.2.6.5.
Table of Contents 3.1.2. Uploading Packages 57 .Chapter ........4 . ...Custom . . . . . . . . Package . . . . . . . . . .Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 ............ 4.1. Building Packages for Red Hat Network 59 4.1.1. RPM Benefits 59 4.1.2. Red Hat Network RPM Guidelines 60 4.2. Digital Signatures for Red Hat Network Packages 61 4.2.1. Generating a GnuPG Keypair 61 4.2.2. Signing packages 63 4.3.
Red Hat Satellite 5.6 Reference Guide A.5.10. Linux::Process Health A.5.11. Linux::Process Running A.5.12. Linux::Swap Usage A.5.13. Linux::T CP Connections by State A.5.14. Linux::Users A.5.15. Linux::Virtual Memory A.6. LogAgent A.6.1. LogAgent::Log Pattern Match A.6.2. LogAgent::Log Size A.7. MySQL 3.23 - 3.33 A.7.1. MySQL::Database Accessibility A.7.2. MySQL::Opened T ables A.7.3. MySQL::Open T ables A.7.4. MySQL::Query Rate A.7.5. MySQL::T hreads Running A.8. Network Services A.8.1.
Table of Contents A.10.12. Red Hat Satellite::Users 128 . . . . . . . . . .History Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 .............
Red Hat Satellite 5.
Preface Preface 1. Audience T he target audience for this guide includes system administrators who aim to manage updates for systems within an internal network. 2. Document Conventions T his manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. T he Liberation Fonts set is also used in HT ML editions if the set is installed on your system.
Red Hat Satellite 5.6 Reference Guide Choose System → Preferences → Mouse from the main menu bar to launch Mouse Preferences. In the Buttons tab, select the Left-handed m ouse check box and click Close to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand). T o insert a special character into a gedit file, choose Applications → Accessories → Character Map from the main menu bar.
Preface static int kvm_vm_ioctl_deassign_device(struct kvm *kvm, struct kvm_assigned_pci_dev *assigned_dev) { int r = 0; struct kvm_assigned_dev_kernel *match; mutex_lock(&kvm->lock); match = kvm_find_assigned_dev(&kvm->arch.
Red Hat Satellite 5.6 Reference Guide Portal at http://access.redhat.com. T hrough the customer portal, you can: search or browse through a knowledgebase of technical support articles about Red Hat products. submit a support case to Red Hat Global Support Services (GSS). access other product documentation. Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at https://www.redhat.
Chapter 1. Red Hat Satellite Information Chapter 1. Red Hat Satellite Information T his section covers various topics on Red Hat Satellite advanced configuration. 1.1. Command Line Configuration Management Tools In addition to the options provided in the Red Hat Satellite website, there are two command line tools for managing a system's configuration files: the Red Hat Network Configuration Client and the Red Hat Network Configuration Manager.
Red Hat Satellite 5.6 Reference Guide T able 1.1. rhn-actions-control options Option Description --enable-deploy Allow rhncfg-client to deploy files. --enable-diff Allow rhncfg-client to diff files. --enable-upload Allow rhncfg-client to upload files. --enable-mtime-upload Allow rhncfg-client to upload mtime. --enable-all Allow rhncfg-client to do everything. --enable-run Enable script.run --disable-deploy Disable deployment.
Chapter 1. Red Hat Satellite Information Files in config channel 'config-channel-14' /etc/example-config.txt /etc/rhn/rhn.conf You may then wonder where the second version of /etc/exam ple-config.txt went. T he rank of the /etc/exam ple-config.txt file in config-channel-17 was higher than that of the same file in config-channel-14 . As a result, the version of the configuration file in config-channel-14 is not deployed for this system, although the file still resides in the channel.
Red Hat Satellite 5.6 Reference Guide [root@testsatellite root]# rhncfg-client diff --- /etc/test +++ /etc/test 2013-08-28 00:14:49.405152824 +1000 @@ -1 +1,2 @@ This is the first line +This is the second line added In addition, you may include the --topdir option to compare config files in Red Hat Network with those located in an arbitrary (and unused) location on the client system, like so: [root@ root]# rhncfg-client diff --topdir /home/test/blah/ /usr/bin/diff: /home/test/blah/etc/example-config.
Chapter 1. Red Hat Satellite Information configuration values from the Red Hat Update Agent. When run as a user other than root, you may have to make configuration changes within the ~/.rhncfgrc file. T he session file is cached in ~/.rhncfg-m anager-session to prevent logging in for every command. T he default timeout for the Red Hat Network Configuration Manager is 30 minutes. T o alter this, add the server.session_lifetim e option and new value to the /etc/rhn/rhn.
Red Hat Satellite 5.6 Reference Guide T he output resembles the following: Pushing to channel example-channel Local file >/path/to/file -> remote file /new/path/to/file.txt T he following table lists the options available for rhncfg-m anager add: T able 1.4 .
Chapter 1. Red Hat Satellite Information T able 1.5. rhncfg-m anager diff options Option Description -c CHANNEL, --channel=CHANNEL Get file(s) from this config channel -r REVISION, --revision=REVISION Use this revision -d DEST _FILE, --dest-file=DEST _FILE Upload the file as this path -t T OPDIR, --topdir=T OPDIR Make all files relative to this string -h, --help Show help message and exit 1.1.3.4 .
Red Hat Satellite 5.6 Reference Guide T he output resembles the following: Copying /tmp/dest_path/example-config.txt -> \ blah2/tmp/dest_path/exampleconfig.txt T he following table lists the options available for rhncfg-m anager download-channel: T able 1.7. rhncfg-m anager download-channel options Option Description -t T OPDIR, --topdir=T OPDIR Directory all the file paths are relative to. T his option must be set. -h, --help Show help message and exit 1.1.3.6.
Chapter 1. Red Hat Satellite Information Available config channels: example-channel example-channel2 example-channel3 config-channel-14 config-channel-17 Note that this does not list local_override or server_im port channels. 1.1.3.9. Removing a File from a Channel T o remove a file from a channel, issue the command: rhncfg-manager remove --channel=channel-label /tmp/dest_path/example-config.txt If prompted for your Red Hat Network username and password, provide them.
Red Hat Satellite 5.6 Reference Guide rhncfg-manager update \ --channel=channel-label --dest-file=/path/to/file.txt /local/path/to/file T he output resembles the following: Pushing to channel example-channel: Local file examplechannel/tmp/dest_path/example-config.txt -> \ remote file /tmp/dest_path/exampleconfig.txt T he following table lists the options available for rhncfg-m anager update: T able 1.10.
Chapter 1. Red Hat Satellite Information Monitoring provides both real time and historical state change information, as well as specific metric data. It provides notifications of system failures and performance degradation before it becomes critical. It also provides information that assists in capacity planning and event correlation. For example, the results of a probe recording CPU usage across systems would assist in balancing loads on those systems.
Red Hat Satellite 5.6 Reference Guide Note It is recommended that you leave the monitoring configuration values as the default values. Sendmail needs to be configured to use notifications. 1.2.2. Configuring the Red Hat Network Monitoring Daemon (rhnmd) T o make the most out of your monitoring entitlement, Red Hat suggests installing the Red Hat Network monitoring daemon on your client systems.
Chapter 1. Red Hat Satellite Information T he rhnm d package can be found in the Red Hat Network T ools channel for all Red Hat Enterprise Linux distributions. T o install it: 1. Subscribe the systems to be monitored to the Red Hat Network T ools channel associated with the system. T his can be done individually through the System Details → Channels → Software subtab or for multiple systems at once through the Channel Details → T arget Systems tab. 2.
Red Hat Satellite 5.6 Reference Guide the SSH key to. Click the Manage button at the top to finish. 4. From the System Set Manager, click Run rem ote com m ands, then in the Script text box, type the following line: #!/bin/sh cat <> ~nocpulse/.ssh/authorized_keys T hen, press Enter, paste the SSH Key and add EOF. T he result should look similar to the following: #!/bin/sh cat <> ~nocpulse/.
Chapter 1. Red Hat Satellite Information 2. Navigate to Users and select the username. On the User Details page, click on Notification Methods → create new method. 3. Enter an intuitive, descriptive label for the method name, such as DBA day em ail, and provide the correct email address. Remember, the labels for all notification methods are available in a single list during probe creation, so they should be unique to your organization. 4.
Red Hat Satellite 5.6 Reference Guide acknowledgment email. Enable email reply redirects by opening /etc/aliases and adding the following line: rogerthat01: "| /etc/smrsh/ack_queuer.pl" Once the parameter has been set, reply to the notification email and include the desired option. T hese are the possible redirect options, or filter types: ACK MET OO - Sends the notification to the redirect destination(s) in addition to the default destination.
Chapter 1. Red Hat Satellite Information Note Since both the notification method name and address can be edited, consider updating the method rather than deleting it. T his redirects notifications from all probes using the method without having to edit each probe and create a new notification method. 4. If the method is associated with one or more probes, you are presented with a list of the probes using the method and the systems to which the probes are attached instead of a confirmation page.
Red Hat Satellite 5.6 Reference Guide “Establishing T hresholds” for best practices regarding these thresholds. 9. When finished, click Create Probe. Remember, you must commit your monitoring configuration change on the Scout Config Push page for this to take effect. T o delete a probe, navigate to its Current State page (by clicking the name of the probe from the System Details → Probes tab), and click delete probe. Finally, confirm the deletion. 1.2.5.2.
Chapter 1. Red Hat Satellite Information Important T he Monitoring entitlement is required to view this tab. T he Probe Status page is shown by default when you click Monitoring in the top navigation bar. T he Probe Status page displays the summary count of probes in the various states and provides a simple interface to find problematic probes quickly. Note that the probe totals in the tabs at the top of the page may not match the numbers of probes displayed in the tables below.
Red Hat Satellite 5.6 Reference Guide Important T he Monitoring entitlement is required to view this tab. T he probes that have crossed their WARNING thresholds. 1.2.6.1.3. Probe Status ⇒ Unknown Important T he Monitoring entitlement is required for this feature. T he probes that cannot collect the metrics needed to determine probe state. Most but not all probes enter an unknown state when exceeding their timeout period.
Chapter 1. Red Hat Satellite Information Important T he Monitoring entitlement is required to view this tab. Identifies the selected probe's status and when it last ran, while providing the ability to generate a report on the probe. Although this page is integral to monitoring, it is found under the Probes tab within the System Details page since its configuration is specific to the system being monitored.
Red Hat Satellite 5.6 Reference Guide 5. Organization/Scout/Probe: T his option allows you to select the organization, scout(s), or probe(s) to which this filter applies. T o select multiple items from the list, hold the Ctrl key while clicking the names of the items. T o select a range of items, hold the Shift key while clicking on the first and last items in the range. 6. Probes in State: Select which probe state(s) relate to the filter.
Chapter 1. Red Hat Satellite Information Note Sendmail must be configured correctly on your Red Hat Satellite and each client system to which the Probe Suite is applied must have the rhnm d daemon installed and running. See the Red Hat Satellite Installation Guide for additional information. 4. On the "Systems" tab, add the systems to which the Probe Suite applies. Click the add system s to probe suite link in the upper right of the screen to continue. 5.
Red Hat Satellite 5.6 Reference Guide 3. Check the box next to the system(s) you wish to remove from the Probe Suite. 4. Click the Rem ove System (s) from Probe Suite button. Finally, as with single Probes, you may download a CSV file containing information about Probe Suites. Click the Download CSV link at the bottom of the Monitoring ⇒ Probe Suites page to download the file. 1.2.6.4 . Scout Config Push Important T he Monitoring entitlement is required to view this tab.
Chapter 1. Red Hat Satellite Information Note Master and Slave are legacy terms that carry connotations that are not enforced by the ISS protocol. Please keep their restricted meanings, as described above, in mind while studying this section. T he ISS feature can be used in different ways depending on the needs of the organization. T here are ISS configurations where two Satellites may act as both masters and slaves of each other.
Red Hat Satellite 5.6 Reference Guide Note Choosing the Sync All Orgs to Slave? option on the Master Setup page will override any specifically selected organizations in the Local Organization table below. e. Click Create. f. (Optional) Click on any local organization to be exported to the Slave Satellite. g. Click Allow Orgs. Note In Satellite 5.5, the Master Satellite used the iss_slaves parameter in the /etc/rhn/rhn.conf file to identify which slaves could contact the Master Satellite. Satellite 5.
Chapter 1. Red Hat Satellite Information Begin the synchronization by running the satellite-sync command: satellite-sync -c your-channel Note Command line options that are manually provided with the satellite-sync command will override any custom settings in the /etc/rhn/rhn.conf file. Procedure 1.4 .
Red Hat Satellite 5.6 Reference Guide Procedure 1.5. Configuring the Master Satellite Server 1. Enable the inter-satellite synchronization (ISS) feature in the /etc/rhn/rhn.conf file: disable_iss=0 2. Save the configuration file, and restart the httpd service: service httpd restart Procedure 1.6. Configuring Slave Servers Slave Satellite servers are the machines that will have their content synchronized to the master server. 1.
Chapter 1.
Red Hat Satellite 5.6 Reference Guide Example 1.1. Import Content from Master to Slave Satellite T his example imports content from master to slave satellite: satellite-sync --parent-sat=master.satellite.example.com -c channel-name -orgid=2 Example 1.2. Import Content from an Exported Dump of an Organization T his example imports content from an exported dump of a specific organization: $ satellite-sync -m /dump -c channel-name --orgid=2 Example 1.3.
Chapter 1. Red Hat Satellite Information Example 1.5. Synchronized Slaves In this example, the master satellite provides data directly to the slaves and changes are regularly synchronized. Example 1.6. Slave Custom Content T his example uses the master satellite as a development channel, from which content is distributed to all production slave satellites. Some of the slave satellites have extra content that is not present in the master satellite channels.
Red Hat Satellite 5.6 Reference Guide Chapter 2. Red Hat Satellite and Solaris-specific Information T his is a section on using Red Hat Satellite with Solaris systems. 2.1. UNIX Support Guide 2.1.1. Introduction T his chapter documents the installation procedure for, and identifies differences in, Red Hat Network functionality when used to manage UNIX-based client systems. Red Hat Network offers UNIX support to help customers migrate from UNIX to Linux.
Chapter 2.
Red Hat Satellite 5.6 Reference Guide installation process, as pictured: Figure 2.1. Enabling UNIX Support During Satellite Installation 2. After the Satellite has been installed: Enable UNIX support by configuring the Satellite after it has been installed. T o do so, select Admin in the top menu bar, then select Satellite Configuration in the left navigation bar.
Chapter 2. Red Hat Satellite and Solaris-specific Information Figure 2.2. Enabling UNIX Support After Satellite Installation Click the Update Configuration button to confirm the change. 3. Finally, create a base channel to which your client systems may subscribe. Red Hat Network does not provide UNIX content, satellite-sync cannot be used to create the channel. T o create a Solaris channel, login to the web interface of the Satellite as either a Satellite Administrator or a certificate authority.
Red Hat Satellite 5.6 Reference Guide sections explain these steps in detail. 2.1.3.1. Downloading and Installing Additional Packages T his section steps you through the process of downloading and installing third-party applications and the Red Hat Network applications from the Satellite onto the UNIX client. Of primary importance is the Red Hat Update Agent for UNIX (up2date), which provides the link between your client systems and Red Hat Network.
Chapter 2. Red Hat Satellite and Solaris-specific Information Note Solaris package archive names differ from the name of the installed package. For example, the package archive libgcc-sol-sparc-local.gz becomes SMClibgcc after installation 2.1.3.1.2. Configuring the Library Search Path T o allow the Solaris client to use the libraries installed in the previous step, you must add their location to the library search path.
Red Hat Satellite 5.6 Reference Guide SMClibgcc and SMCosslg may also be included in the tarball. 2.1.3.1.4 . Installing the Red Hat Network Packages Change to the uncompressed directory and use the UNIX variant's native installation tool to install each package. For example, on Solaris, use the pkgadd command. Answer "yes" to any prompts during package install. Here is how a typical installation might proceed: # pkgadd -d RHATpossl-0.6-1.p24.6.pkg all # pkgadd -d RHATpythn-2.4.1-2.rhn.4.sol9.
Chapter 2. Red Hat Satellite and Solaris-specific Information T o install the certificate, follow these steps for each client: 1. Download the SSL certificate from the /var/www/htm l/pub/ directory of the Red Hat Satellite onto the client system. T he certificate will be named something similar to RHN-ORG-T RUST EDSSL-CERT . It is accessible via the web at the following URL: https://yoursatellite.exam ple.com /pub/RHN-ORG-T RUST ED-SSL-CERT . 2.
Red Hat Satellite 5.6 Reference Guide Now that you have installed Red Hat Network-specific packages, implemented SSL, and reconfigured your client systems to connect to the Red Hat Satellite, you are ready to begin registering systems and obtaining updates. 2.1.4 .1. Registering Unix Systems T his section describes the Red Hat Network registration process for UNIX systems. You must use the rhnreg_ks command to accomplish this; the use of activation keys for registering your systems is optional.
Chapter 2. Red Hat Satellite and Solaris-specific Information Red Hat Network treats patches similarly to packages; they are listed and installed in the same way and with the same interface as normal packages. Patches are 'numbered' by Solaris, and will have names like "patch-solaris-108434". T he version of a Solaris patch is extracted from the original Solaris metadata, and the release is always 1. Patch Clusters are bundles of patches that are installed as a unit.
Red Hat Satellite 5.6 Reference Guide T able 2.2. solaris2mpm options Option Description --version Displays the program's version number and exits -h, --help Displays this information and exits -?, --usage Prints program usage information and exits --tem pdir= T emporary directory to work from --select-arch= Selects the architecture (i386 or SPARC) for multi-arch packages. 2.1.4 .2.1.2. rhnpush with .
Chapter 2. Red Hat Satellite and Solaris-specific Information available options for rhnsd on Solaris: T able 2.3. rhnsd Options Option Description -f, --foreground Run in foreground -i, --interval=MINS Connect to Red Hat Network every MINS minutes -v, --verbose Log all actions to syslog -h, --help Give this help list -u, --usage Give this help list -V, --version Print program version 2.1.4 .2.4 .
Red Hat Satellite 5.6 Reference Guide through the Satellite's website. T his feature allows you to run virtually any (compatible) application or script on any system in your domain without ever having to open a terminal. 2.1.5.1. Enabling Commands With the flexibility this tool offers comes great risk and the responsibility to mitigate that risk. For all practical purposes, this feature grants a root BASH prompt to anyone with administrative access to the system on the website.
Chapter 3. Red Hat Satellite Proxy Information Chapter 3. Red Hat Satellite Proxy Information T his is a section on using Red Hat Satellite Proxy with the Red Hat Network Package Manager. 3.1. Using the Red Hat Network Package Manager and Serving Local Packages through the Red Hat Network Proxy T he Red Hat Network Package Manager is a command line tool that allows an organization to serve local packages associated with a private Red Hat Network channel through the Red Hat Network Proxy Server.
Red Hat Satellite 5.6 Reference Guide T able 3.1. rhn_package_m anager options Option Description -v, --verbose Increase verbosity. -dDIR, --dir=DIR Process packages from directory DIR. -cCHANNEL, --channel=CHANNEL Manage this channel - may be present multiple times. -nNUMBER, --count=NUMBER Process this number of headers per call - the default is 32. -l, --list List each package name, version number, release number, and architecture in the specified channel(s).
Chapter 3. Red Hat Satellite Proxy Information T he steps will be further discussed in the next sections. 3.1.1. Creating a Private Channel Before local packages can be provided through the Red Hat Network Proxy Server, a private channel is needed to store them. Perform the following steps to create a private channel: 1. Log in to the Red Hat Network Web interface at https://rhn.redhat.com or to the local Red Hat Satellite server in the network. 2. Click Channels on the top navigation bar.
Red Hat Satellite 5.6 Reference Guide Note If a channel name is not specified, the packages are not added to any channel. T he packages can then be added to a channel using the Red Hat Network web interface. T he interface can also be used to modify existing private channels. After uploading the packages, you can immediately check the Red Hat Network Web interface to verify their presence.
Chapter 4. Custom Package Management Chapter 4. Custom Package Management T his chapter provides an overview of how to build packages for successful delivery via Red Hat Network. T opics covered include why RPM should be used, how to build packages for Red Hat Network, and how to properly sign packages. 4.1. Building Packages for Red Hat Network Red Hat Network uses the RPM Package Manager (RPM) technology to determine what software additions and updates are applicable to each client system.
Red Hat Satellite 5.6 Reference Guide Keeping sources pristine may seem important only to developers, but it results in higher quality software for end users as well. 4.1.2. Red Hat Network RPM Guidelines T he strength of RPM lies in its ability to define dependencies and identify conflicts accurately. Red Hat Network relies on this aspect of RPM. Red Hat Network offers an automated environment, which means that no manual intervention can take place during the installation of a package.
Chapter 4. Custom Package Management Important Do not create an RPM by archiving files and then unarchiving them in the post-install script. T his defeats the purpose of RPM. If the files in the archive are not included in the file list, they cannot be verified or examined for conflicts. In the vast majority of cases, RPM itself can pack and unpack archives most effectively anyway. For instance, don't create files in a %post that cannot or will not be cleaned up in a %postun section. 4.2.
Red Hat Satellite 5.6 Reference Guide 6. Press y to confirm your decision. 7. Provide a User-ID containing your name, your email address, and an optional comment. Each of these is requested individually. When finished, you are presented with a summary of the information you entered. 8. Accept your choices and enter a passphrase. Note Like your account passwords, a good passphrase is essential for optimal security in GnuPG.
Chapter 4. Custom Package Management 4.2.2. Signing packages Before signing packages, configure the ~/.rpm m acros file to include the following: %_signature gpg %_gpg_name B7085C8A Replace the _gpg_nam e key ID value of B7085C8A with the key ID from your GPG keyring that you use to sign packages. T his value tells RPM which signature to use. T o sign the package package-name-1.0-1.noarch.rpm, use the following command: rpm --resign package-name-1.0-1.noarch.rpm Enter your passphrase.
Red Hat Satellite 5.6 Reference Guide For Red Hat Enterprise Linux 3 or later, use the following command: rpm --import /path/to/YOUR-RPM-GPG-KEY Once the GPG key has been successfully added to the client, the system should be able to validate custom RPMs signed with the corresponding key. Note When using custom RPMs and channels, always create a custom GPG key for these packages. T he location of the GPG key also needs to be added to the Kickstart profile.
Chapter 5. Troubleshooting Chapter 5. Troubleshooting T his chapter provides tips for determining the cause of and resolving the most common errors associated with Red Hat Satellite. If you need additional help, contact Red Hat Network support at https://access.redhat.com/support/. Log in using your Satellite-entitled account to see the full list of options. T o begin troubleshooting general problems, examine the log file or files related to the component exhibiting failures.
Red Hat Satellite 5.6 Reference Guide Q: My Satellite is failing. Any idea why? A: Do not subscribe the Red Hat Satellite to any of the following child channels available from Red Hat Network's central servers: Red Hat Developer Suite Red Hat Application Server Red Hat Extras JBoss product channels Subscribing to these channels and updating the Satellite might install newer, incompatible versions of critical software components, causing the Satellite to fail. 5.3.
Chapter 5. Troubleshooting Make sure that Red Hat Satellite is using Network T ime Protocol (NT P) and set to the appropriate time zone. T his also applies to all client systems and the separate database machine in Red Hat Satellite with Stand-Alone Database. Confirm the correct package: rhn-org-httpd-ssl-key-pair-MACHINE_NAME-VER-REL.noarch.rpm is installed on the Red Hat Satellite and the corresponding rhn-org-trusted-ssl-cert* .noarch.
Red Hat Satellite 5.6 Reference Guide # openssl x509 -dates -noout -in /etc/httpd/conf/ssl.crt/server.crt By default, the server certificate has a one-year life while client certificates are good for 10 years. If you find the certificates are incorrect, you can either wait for the valid start time, if possible, or create new certificates, preferably with all system times set to GMT . 5.5.
Chapter 5. Troubleshooting users and organizations. Rather than gathering such information manually from the Satellite interface, Red Hat Satellite includes the spacewalk-report command to gather and display vital Satellite information at once. Note T o use spacewalk-report you must have the spacewalk-reports package installed. spacewalk-report allows administrators to organize and display reports about content, errata, systems, system event history, and user resources across the Satellite.
Red Hat Satellite 5.6 Reference Guide T able 5.2.
Chapter 5. Troubleshooting invocations and their options.
Red Hat Satellite 5.6 Reference Guide ERROR: unhandled exception occurred: Traceback (most recent call last): File "/usr/bin/rhn-satellite-activate", line 45, in ? sys.exit(abs(mod.main() or 0)) File "/usr/share/rhn/satellite_tools/rhn_satellite_activate.py", line 585, in main activateSatellite_remote(options) File "/usr/share/rhn/satellite_tools/rhn_satellite_activate.py", line 291, in activateSatellite_remote ret = s.satellite.deactivate_satellite(systemid, rhn_cert) File "/usr/lib/python2.
Chapter 5. Troubleshooting file=answer file option. Ensure the answer file has the HT T P proxy information specified as follows: rhn-http-proxy = : rhn-http-proxy-username = rhn-http-proxy-password = Q: I'm getting an "ERROR: server.mount_point not set in the configuration file" error when I try to activate or synchronize the Red Hat Satellite. How do I fix it? A: An "ERROR: server.
Red Hat Satellite 5.6 Reference Guide Q: I'm getting an "Internal Server Error" complaining about ASCII when I try to edit the kickstart profile. What's going on? A: If you have recently added some kernel parameters to your kickstart profile, you might find that when you attempt to View a List of Kickstart Profiles that you get the following Internal Server Error: 'ascii' codec can't encode character u'\u2013' T his error occurs because some text in the profile is not being recognized correctly.
Chapter 5. Troubleshooting # rhn-satellite restart Shutting down rhn-satellite... Stopping RHN Taskomatic... Stopped RHN Taskomatic. Stopping cobbler daemon: Stopping rhn-search... Stopped rhn-search. Stopping MonitoringScout ... Stopping Monitoring ... Stopping httpd: Stopping tomcat5: Shutting down osa-dispatcher: Shutting down Oracle Net Listener ... Shutting down Oracle DB instance "rhnsat" ... Shutting down Jabber router: Done. Starting rhn-satellite...
Red Hat Satellite 5.6 Reference Guide 127.0.0.1 localhost.localdomain.com localhost T hen, save the file and attempt to re-run the Red Hat Network client applications or the Apache Web server. If they still fail, explicitly identify the IP address of the Satellite in the file, such as: 127.0.0.1 localhost.localdomain.com localhost 123.45.67.8 this_machine.example.com this_machine Replace the value here with the actual IP address of the Satellite. T his should resolve the problem.
Chapter 5.
Red Hat Satellite 5.6 Reference Guide # grep chkconfig /var/log/httpd/access_log 10.10.77.131 - - [19/Aug/2011:15:12:36 -0400] "GET /rhn/common/DownloadFile.do?url=/ks/dist/ks-rhel-i386-server5-u3/Server /chkconfig-1.3.30.1-2.i386.rpm HTTP/1.1" 206 24744 "-" "urlgrabber/3.1.0 yum/3.2.19" 10.10.76.143 - - [19/Aug/2011:15:12:36 -0400] "GET /ks/dist/ks-rhel-i386server-5-u3/Server/chkconfig1.3.30.1-2.i386.rpm HTTP/1.1" 206 24744 "-" "urlgrabber/3.1.0 yum/3.2.19" 10.10.76.
Chapter 5. Troubleshooting Subject: WEB TRACEBACK from satellite.example.com Date: Wed, 19 Aug 2011 20:28:01 -0400 From:Red Hat Satellite To: admin@example.com java.lang.RuntimeException: XmlRpcException calling cobbler. at com.redhat.rhn.manager.kickstart.cobbler.CobblerXMLRPCHelper.invokeMethod(Cobb lerXMLRPCHelper.java:72) at com.redhat.rhn.taskomatic.task.CobblerSyncTask.execute(CobblerSyncTask.java:76) at com.redhat.rhn.taskomatic.task.SingleThreadedTestableTask.
Red Hat Satellite 5.6 Reference Guide # begin Red Hat management server registration mkdir -p /usr/share/rhn/ wget http://satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT -O /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT perl -npe 's/RHNS-CA-CERT/RHN-ORG-TRUSTED-SSL-CERT/g' -i /etc/sysconfig/rhn/* rhnreg_ks --serverUrl=https://satellite.example.
Chapter 5. Troubleshooting 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 Q: Are there any diagnostic tools that help determine the cause of monitoring errors? A: T hough 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.
Red Hat Satellite 5.6 Reference Guide runprobe to examine the complete output of the probe. Note that by default, rhn-runprobe works in test mode, meaning no results are entered in the database. Here are its options: T able 5.3. rhn-runprobe Options Option Description --help List the available options and exit. --probe=PROBE_ID Run the probe with this ID. --prob_arg=PARAMETER Override any probe parameters from the database. --m odule=PERL_MODULE Package name of alternate code to run.
Chapter 5. Troubleshooting 4. A number of systems in the organization should now be in an unentitled state. T he number of systems unentitled in the organization will be equal to the difference between the total number of entitlements you removed from the organization and the number of entitlements the organization did not have applied to the systems.
Red Hat Satellite 5.6 Reference Guide A: Make sure /etc/sysconfig/rhn/system id is owned by root.apache with the permissions 0640. Read the log files. A list is available on the Log Files section of the Red Hat Satellite Proxy Installation Guide. Q: How do I troubleshoot general problems in the Red Hat Satellite Proxy? A: T o begin troubleshooting general problems, examine the log file or files related to the component exhibiting failures. A common issue is full disk space.
Chapter 5. Troubleshooting In a text editor, remove the machine host information from the file, it should look like so: 127.0.0.1 localhost.localdomain.com localhost Save the file and attempt to re-run the Red Hat Network client applications or the Apache Web server. If they still fail, explicitly identify the IP address of the Proxy in the file, such as: 127.0.0.1 localhost.localdomain.com localhost 123.45.67.8 this_machine.example.
Red Hat Satellite 5.6 Reference Guide 3. Delete the contents of that directory: rm -fv /var/cache/rhn/* 4. Restart both services: service squid start service httpd start T he same task can be accomplished quicker by just clearing the directory and restarting squid, but this method will most likely result in a number of Red Hat Network traceback messages. T he internal caching mechanism used for authentication by the Proxy may also need its cache cleared.
Chapter 5. Troubleshooting Note If you have exhausted these troubleshooting steps or want to defer them to Red Hat Network professionals, Red Hat recommends you take advantage of the strong support that comes with Red Hat Satellite. T he most efficient way to do this is to aggregate your Satellite's configuration parameters, log files, and database information and send this package directly to Red Hat.
Red Hat Satellite 5.
Probes Probes Monitoring-entitled systems can have probes applied to them that constantly confirm their health and full operability. T his section lists the available probes broken down by command group, such as Apache. Many probes that monitor internal system aspects (such as the Linux::Disk Usage probe) rather than external aspects (such as the Network Services::SSH probe) require the installation of the Red Hat Network monitoring daemon (rhnm d).
Red Hat Satellite 5.6 Reference Guide otherwise indicated. Exceptions to these rules are noted within the individual probe references. Important Some probes have thresholds based on time. In order for such CRIT ICAL and WARNING thresholds to work as intended, their values cannot exceed the amount of time allotted to the timeout period. Otherwise, an UNKNOWN status is returned in all instances of extended latency, thereby nullifying the thresholds.
Probes A.2.2. Apache::Traffic T he Apache::T raffic probe monitors the requests on an Apache web server and collects the following metrics: Current Requests - T he number of requests being processed by the server at probe runtime. Request Rate - T he accesses to the server per second since the probe last ran. T raffic - T he kilobytes per second of traffic the server has processed since the probe last ran. T he ExtendedStatus directive in the httpd.
Red Hat Satellite 5.6 Reference Guide T he probes in this section (with the exception of JDBC Connection Pool) can be configured to monitor the properties of any BEA WebLogic 6.x and higher server (Administration or Managed) running on a given host, even in a clustered environment. Monitoring of a cluster is achieved by sending all SNMP queries to the Administration Server of the domain and then querying its Managed Servers for individual data.
Probes A.3.2. BEA WebLogic::Heap Free T he BEA WebLogic::Heap Free probe collects the following metric: Heap Free - T he percentage of free heap space. T his probe's transport protocol is User Datagram Protocol (UDP). T able A.5. BEA WebLogic::Heap Free settings Field Value SNMP Community String* public SNMP Port* 161 SNMP Version* 1 BEA Domain Admin Server BEA Server Name* myserver Critical Maximum Heap Free Warning Maximum Heap Free Warning Minimum Heap Free Critical Minimum Heap Free A.3.3.
Red Hat Satellite 5.6 Reference Guide T able A.6. BEA WebLogic::JDBC Connection Pool settings Field Value SNMP Community String* public SNMP Port* 161 SNMP Version* 1 BEA Domain Admin Server BEA Server Name* myserver JDBC Pool Name* MyJDBC Connection Pool Critical Maximum Connections Warning Maximum Connections Critical Maximum Connection Rate Warning Maximum Connection Rate Critical Maximum Waiters Warning Maximum Waiters A.3.4.
Probes T able A.8. BEA WebLogic::Servlet settings Field Value SNMP Community String* public SNMP Port* 161 SNMP Version* 1 BEA Domain Admin Server BEA Server Name* myserver Servlet Name* Critical Maximum High Execution T ime Warning Maximum High Execution T ime Critical Maximum Execution T ime Moving Average Warning Maximum Execution T ime Moving Average A.4. General T he probes in this section are designed to monitor basic aspects of your systems.
Red Hat Satellite 5.6 Reference Guide T he remote program will need to output some iteration of the following code to ST DOUT : - 10
- status message here
T he required value for data is the data point to be inserted in the database for time-series trending. T he status_m essage is optional and can be whatever text string is desired with a maximum length of 1024 bytes.
Probes T able A.11. General::SNMP Check settings Field Value SNMP OID* SNMP Community String* public SNMP Port* 161 SNMP Version* 2 T imeout* 15 Critical Maximum Value Warning Maximum Value Warning Minimum Value Critical Minimum Value A.4.4. General::TCP Check T he General::T CP Check probe tests your T CP server by verifying that it can connect to a system via the specified port number.
Red Hat Satellite 5.6 Reference Guide T able A.13. General::UDP Check settings Field Value Port* 1 Send Expect T imeout* 10 Critical Maximum Latency Warning Maximum Latency A.4.6. General::Uptime (SNMP) T he General::Uptime (SNMP) probe records the time since the device was last started. It uses the SNMP object identifier (OID) to obtain this value. T he only error status it will return is UNKNOWN.
Probes T able A.15. Linux::CPU Usage settings Field Value T imeout* 15 Critical Maximum CPU Percent Used Warning Maximum CPU Percent Used A.5.2. Linux::Disk IO Throughput T he Linux::Disk IO T hroughput probe monitors a given disk and collects the following metric: Read Rate - T he amount of data that is read in kilobytes per second. Write Rate - T he amount of data that is written in kilobytes per second.
Red Hat Satellite 5.6 Reference Guide T able A.17. Linux::Disk Usage settings Field Value File system* /dev/hda1 T imeout* 15 Critical Maximum File System Percent Used Warning Maximum File System Percent Used Critical Maximum Space Used Warning Maximum Space Used Warning Minimum Space Available Critical Minimum Space Available A.5.4. Linux::Inodes T he Linux::Inodes probe monitors the specified file system and collects the following metric: Inodes - T he percentage of inodes currently in use.
Probes T able A.19. Linux::Interface T raffic settings Field Value Interface* T imeout* 30 Critical Maximum Input Rate Warning Maximum Input Rate Warning Minimum Input Rate Critical Minimum Input Rate Critical Maximum Output Rate Warning Maximum Output Rate Warning Minimum Output Rate Critical Minimum Output Rate A.5.6. Linux::Load T he Linux::Load probe monitors the CPU of a system and collects the following metric: Load - T he average load on the system CPU over various periods.
Red Hat Satellite 5.6 Reference Guide T able A.21. Linux::Memory Usage settings Field Value Include reclaimable memory no T imeout* 15 Warning Maximum RAM Free Critical Maximum RAM Free A.5.8. Linux::Process Counts by State T he Linux::Process Counts by State probe identifies the number of processes in the following states: Blocked - A process that has been switched to the waiting queue and whose state has been switched to waiting.
Probes T able A.23. Linux::Process Count T otal settings Field Value T imeout* 15 Critical Maximum Process Count Warning Maximum Process Count A.5.10. Linux::Process Health T he Linux::Process Health probe monitors user-specified processes and collects the following metrics: CPU Usage - T he CPU usage rate for a given process in milliseconds per second. T his metric reports the time column of ps output, which is the cumulative CPU time used by the process.
Red Hat Satellite 5.6 Reference Guide A.5.11. Linux::Process Running T he Linux::Process Running probe verifies that the specified process is functioning properly. It counts either processes or process groups, depending on whether the Count process groups checkbox is selected. By default, the checkbox is selected, thereby indicating that the probe should count the number of process group leaders independent of the number of children.
Probes T IME_WAIT - T he socket is waiting after close for remote shutdown transmission so it may handle packets still in the network. CLOSE_WAIT - T he remote side has been shut down and is now waiting for the socket to close. FIN_WAIT - T he socket is closed, and the connection is now shutting down. EST ABLISHED - T he socket has a connection established. SYN_RCVD - T he connection request has been received from the network.
Red Hat Satellite 5.6 Reference Guide T able A.28. Linux::Users settings Field Value T imeout* 15 Critical Maximum Users Warning Maximum Users A.5.15. Linux::Virtual Memory T he Linux::Virtual Memory probe monitors the total system memory and collects the following metric: Virtual Memory - T he percent of total system memory - random access memory (RAM) plus swap that is free. Requirements - T he Red Hat Network monitoring daemon (rhnm d) must be running on the monitored system to execute this probe.
Probes ^ beginning of line $ end of line . match one char * match zero or more chars [] match one character set, e.g. '[Ff]oo' [^] match not in set '[^A-F]oo' + match one or more of preceding chars ? match zero or one of preceding chars | or, e.g. a|b () groups chars, e.g., (foo|bar) or (foo)+ Warning Do not include single quotation marks (') within the expression. Doing so causes egrep to fail silently and the probe to time out. T able A.30.
Red Hat Satellite 5.6 Reference Guide T able A.31.
Probes T he MySQL::Opened T ables probe monitors the MySQL server and collects the following metric: Opened T ables - T he tables that have been opened since the server was started. T able A.33. MySQL::Opened T ables settings Field Value Username Password MySQL Port* 3306 T imeout 15 Critical Maximum Opened Objects Warning Maximum Opened Objects Warning Minimum Opened Objects Critical Minimum Opened Objects A.7.3.
Red Hat Satellite 5.6 Reference Guide T able A.35. MySQL::Query Rate settings Field Value Username Password MySQL Port* 3306 T imeout 15 Critical Maximum Query Rate Warning Maximum Query Rate Warning Minimum Query Rate Critical Minimum Query Rate A.7.5. MySQL::Threads Running T he MySQL::T hreads Running probe monitors the MySQL server and collects the following metric: T hreads Running - T he total number of running threads within the database. T able A.36.
Probes T able A.37. Network Services::DNS Lookup settings Field Value Host or Address to look up T imeout* 10 Critical Maximum Query T ime Warning Maximum Query T ime A.8.2. Network Services::FTP T he Network Services::FT P probe uses network sockets to test FT P port availability. It collects the following metric: Remote Service Latency - T he time it takes in seconds for the FT P server to answer a connection request. T his probe supports authentication.
Red Hat Satellite 5.6 Reference Guide T able A.39. Network Services::IMAP Mail settings Field Value IMAP Port* 143 Expect* OK T imeout* 5 Critical Maximum Remote Service Latency Warning Maximum Remote Service Latency A.8.4. Network Services::Mail Transfer (SMTP) T he Network Services::Mail T ransfer (SMT P) probe determines if it can connect to the SMT P port on the system. Specifying an optional port number overrides the default port 25.
Probes T able A.4 1. Network Services::Ping settings Field Value IP Address (defaults to system IP) Packets to send* 20 T imeout* 10 Critical Maximum Round-T rip Average Warning Maximum Round-T rip Average Critical Maximum Packet Loss Warning Maximum Packet Loss A.8.6. Network Services::POP Mail T he Network Services::POP Mail probe determines if it can connect to the POP3 port on the system. A port number must be specified; specifying another port number overrides the default port 110.
Red Hat Satellite 5.6 Reference Guide Requirements - T he Red Hat Network monitoring daemon (rhnm d) must be running on the monitored system to execute this probe. T able A.4 3. Network Services::Remote Ping settings Field Value IP Address* Packets to send* 20 T imeout* 10 Critical Maximum Round-T rip Average Warning Maximum Round-T rip Average Critical Maximum Packet Loss Warning Maximum Packet Loss A.8.8.
Probes T his probe confirms that it can connect to the HT T PS port on the specified host and retrieve the specified URL. If no URL is specified, the probe fetches the root document. T he probe looks for a HT T P/1. message from the system unless you alter that value. Specifying another port number overrides the default port of 443. T his probe supports authentication. Provide a username and password in the appropriate fields to use this feature.
Red Hat Satellite 5.6 Reference Guide T his probe confirms it can connect to the HT T P port on the specified host and retrieve the specified URL. If no URL is specified, the probe will fetch the root document. T he probe looks for a HT T P/1. message from the system, unless you alter that value. Specifying another port number will override the default port of 80. Unlike most other probes, this probe will return a CRIT ICAL status if it cannot contact the system within the timeout period.
Probes Finally, customers using these Oracle probes against a database using Oracle's Multi-T hreaded Server (MT S) must contact Red Hat support to have entries added to the Red Hat Network Server's /etc/hosts file to ensure that the DNS name is resolved correctly. A.9.1. Oracle::Active Sessions T he Oracle::Active Sessions probe monitors an Oracle instance and collects the following metrics: Active Sessions - T he number of active sessions based on the value of V$PARAMET ER.PROCESSES.
Red Hat Satellite 5.6 Reference Guide T able A.50. Oracle::Blocking Sessions settings Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 T ime Blocking (seconds)* 20 T imeout* 30 Critical Maximum Blocking Sessions Warning Maximum Blocking Sessions A.9.4. Oracle::Buffer Cache T he Oracle::Buffer Cache probe computes the Buffer Cache Hit Ratio so as to optimize the system global area (SGA) Database Buffer Cache size.
Probes T able A.52. Oracle::Client Connectivity settings Field Value Oracle Hostname or IP address* Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 ORACLE_HOME* /opt/oracle Expected DB Name* T imeout* 30 A.9.6. Oracle::Data Dictionary Cache T he Oracle::Data Dictionary Cache probe computes the Data Dictionary Cache Hit Ratio so as to optimize the SHARED_POOL_SIZ E in init.ora.
Red Hat Satellite 5.6 Reference Guide T able A.54 . Oracle::Disk Sort Ratio settings Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 T imeout* 30 Critical Maximum Disk Sort Ratio Warning Maximum Disk Sort Ratio A.9.8. Oracle::Idle Sessions T he Oracle::Idle Sessions probe monitors an Oracle instance and collects the following metric: Idle Sessions - T he number of Oracle sessions that are idle, as determined by the required Time Idle value you provide.
Probes T able A.56. Oracle::Index Extents settings Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 Index Owner* % Index Name* % T imeout* 30 Critical Maximum of Allocated Extents Warning Maximum of Allocated Extents Critical Maximum of Available Extents Warning Maximum of Available Extents A.9.10. Oracle::Library Cache T he Oracle::Library Cache probe computes the Library Cache Miss Ratio so as to optimize the SHARED_POOL_SIZ E in init.ora.
Red Hat Satellite 5.6 Reference Guide T able A.58. Oracle::Locks settings Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 T imeout* 30 Critical Maximum Active Locks Warning Maximum Active Locks A.9.12. Oracle::Redo Log T he Oracle::Redo Log probe monitors an Oracle database instance and collects the following metrics: Redo Log Space Request Rate - T he average number of redo log space requests per minute since the server has been started.
Probes For example, a table that starts with 10 MB of space and that is configured with an extent size of 1 MB and max extents of 10 can grow to a maximum of 20 MB (by being extended by 1 MB ten times). T his probe can be configured to alert by (1) the number of allocated extents (e.g. "go critical when the table has been extended 5 or more times"), or (2) the table is extended past a certain percentage of its max extents (e.g. "go critical when the table has exhausted 80% or more of its max extents").
Red Hat Satellite 5.6 Reference Guide T able A.61. Oracle::T ablespace Usage settings Field Value Oracle SID* Oracle Username* Oracle Password* Oracle Port* 1521 T ablespace Name* % T imeout* 30 Critical Maximum Available Space Used Warning Maximum Available Space Used A.9.15.
Probes T able A.63. Red Hat Satellite::Disk Space settings Field Value Device Pathname* /dev/hda1 Critical Maximum File System Used Warning Maximum File System Used Critical Maximum Space Used Warning Maximum Space Used Critical Maximum Space Available Warning Maximum Space Available A.10.2.
Red Hat Satellite 5.6 Reference Guide T able A.66. Red Hat Satellite::Latency settings Field Value Critical Maximum Probe Latency Average Warning Maximum Probe Latency Average A.10.5. Red Hat Satellite::Load T he Red Hat Satellite::Load probe monitors the CPU load on a Satellite and collects the following metric: Load - T he load average on the CPU for a 1-, 5-, and 15-minute period. T able A.67.
Probes T able A.69. Red Hat Satellite::Process Counts settings Field Value Critical Maximum Blocked Processes Warning Maximum Blocked Processes Critical Maximum Child Processes Warning Maximum Child Processes Critical Maximum Defunct Processes Warning Maximum Defunct Processes Critical Maximum Stopped Processes Warning Maximum Stopped Processes Critical Maximum Sleeping Processes Warning Maximum Sleeping Processes A.10.8.
Red Hat Satellite 5.6 Reference Guide T able A.71. Red Hat Satellite::Process Health settings Field Value Command Name Process ID (PID) file T imeout* 15 Critical Maximum CPU Usage Warning Maximum CPU Usage Critical Maximum Child Process Groups Warning Maximum Child Process Groups Critical Maximum T hreads Warning Maximum T hreads Critical Maximum Physical Memory Used Warning Maximum Physical Memory Used Critical Maximum Virtual Memory Used Warning Maximum Virtual Memory Used A.10.10.
Probes value exceeds the Warning threshold. T able A.74 .
Red Hat Satellite 5.6 Reference Guide Revision History Revision 4 -33.4 00 Rebuild with publican 4.0.
Revision History Revision 4 -18 Final beta updates T hu Jul 12 2013 Dan Macpherson Revision 4 -17 Beta update T hu Jul 12 2013 Dan Macpherson Revision 4 -16 Edited Splice section. Additional ISS content added. T hu Jul 11 2013 Athene Chan Revision 4 -15 Fri Jul 5 2013 BZ #906577 ISS editing from developer reviews. Athene Chan Revision 4 -14 Fri Jul 5 2013 Athene Chan BZ #906577 Additional information about ISS new features have been included.
Red Hat Satellite 5.6 Reference Guide Revision 4 -4 Wed Aug 15 2012 BZ #773647 updated "create new account" screenshot Athene Chan Revision 4 -3 Staging documents for review Athene Chan T hu Aug 9 2012 Revision 3-2 Fri Aug 3 2012 BZ #844849 Restructured paragraph. Athene Chan Revision 3-1 T ue Jun 17 2012 Deprecated content removed. Prepared for 5.
Revision History BZ #683466 - Monitoring Revision 1-28 T hu March 24 2011 BZ #679621 - Fix entities for translation BZ #681788 - Notifications Lana Brindley Revision 1-27 BZ #658127 - API Access Lana Brindley Mon Feb 14 2011 Revision 1-26 Wed Feb 9 2011 BZ #658120 - Remove RHEL 2.
