mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Updating Satellite Server Update your connected Satellite Server to the minor version. For information to update a disconnected Satellite setup, see Chapter 3, Updating a disconnected Satellite Server . Prerequisites Back up your Satellite Server. For more information, see Backing Up Satellite Server and Capsule Server in Administering Red Hat Satellite . Warning If you customize configuration files, manually or using a tool such as Hiera, these changes are overwritten when the maintenance script runs during upgrading or updating. You can use the --noop option with the satellite-installer to test for changes. For more information, see the Red Hat Knowledgebase solution How to use the noop option to check for changes in Satellite config files during an upgrade. Procedure Ensure the Satellite Maintenance repository is enabled: Check the available versions to confirm the minor version is listed: Use the health check option to determine if the system is ready for upgrade. On first use of this command, satellite-maintain prompts you to enter the hammer admin user credentials and saves them in the /etc/foreman-maintain/foreman-maintain-hammer.yml file. Review the results and address any highlighted error conditions before performing the upgrade. Because of the lengthy update time, use a utility such as tmux to suspend and reattach a communication session. You can then check the upgrade progress without staying connected to the command shell continuously. If you lose connection to the command shell where the upgrade command is running, you can see the logged messages in the /var/log/foreman-installer/satellite.log file to check if the process completed successfully. Perform the upgrade: Determine if the system needs a reboot: If the command told you to reboot, then reboot the system: Additional resources To restore the backup of the Satellite Server or Capsule Server, see Restoring Satellite Server or Capsule Server from a Backup

Commands:
subscription-manager repos --enable satellite-maintenance-6.15-for-rhel-8-x86_64-rpms
satellite-maintain upgrade list-versions
satellite-maintain upgrade check --target-version 6.15.z
satellite-maintain upgrade run --target-version 6.15.z
dnf needs-restarting --reboothint
reboot
Chapter 2. The value of registering your RHEL system to Red Hat Registration establishes an authorized connection between your system and Red Hat. Red Hat issues the registered system, whether a physical or virtual machine, a certificate that identifies and authenticates the system so that it can receive protected content, software updates, security patches, support, and managed services from Red Hat. With a valid subscription, you can register a Red Hat Enterprise Linux (RHEL) system in the following ways: During the installation process, using an installer graphical user interface (GUI) or text user interface (TUI) After installation, using the command-line interface (CLI) Automatically, during or after installation, using a kickstart script or an activation key. The specific steps to register your system depend on the version of RHEL that you are using and the registration method that you choose. Registering your system to Red Hat enables features and capabilities that you can use to manage your system and report data. For example, a registered system is authorized to access protected content repositories for subscribed products through the Red Hat Content Delivery Network (CDN) or a Red Hat Satellite Server. These content repositories contain Red Hat software packages and updates that are available only to customers with an active subscription. These packages and updates include security patches, bug fixes, and new features for RHEL and other Red Hat products. Important The entitlement-based subscription model is deprecated and will be retired in the future. Simple content access is now the default subscription model. It provides an improved subscription experience that eliminates the need to attach a subscription to a system before you can access Red Hat subscription content on that system. If your Red Hat account uses the entitlement-based subscription model, contact your Red hat account team, for example, a technical account manager (TAM) or solution architect (SA) to prepare for migration to simple content access. For more information, see Transition of subscription services to the hybrid cloud .

Commands:
7.320. haproxy 7.320.1. RHSA-2013:1120 - Moderate: haproxy security update An updated haproxy package that fixes one security issue is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link associated with the description below. HAProxy provides high availability, load balancing, and proxying for TCP and HTTP-based applications. Security Fix CVE-2013-2175 A flaw was found in the way HAProxy handled requests when the proxy's configuration ("/etc/haproxy/haproxy.cfg") had certain rules that use the hdr_ip criterion. A remote attacker could use this flaw to crash HAProxy instances that use the affected configuration. Red Hat would like to thank HAProxy upstream for reporting this issue. Upstream acknowledges David Torgerson as the original reporter. HAProxy is released as a Technology Preview in Red Hat Enterprise Linux 6. More information about Red Hat Technology Previews is available at https://access.redhat.com/support/offerings/techpreview/ . All users of haproxy are advised to upgrade to this updated package, which contains a backported patch to correct this issue. 7.320.2. RHSA-2013:0868 - Moderate: haproxy security update An updated haproxy package that fixes one security issue is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link associated with the description below. HAProxy provides high availability, load balancing, and proxying for TCP and HTTP-based applications. Security Fix CVE-2013-1912 A buffer overflow flaw was found in the way HAProxy handled pipelined HTTP requests. A remote attacker could send pipelined HTTP requests that would cause HAProxy to crash or, potentially, execute arbitrary code with the privileges of the user running HAProxy. This issue only affected systems using all of the following combined configuration options: HTTP keep alive enabled, HTTP keywords in TCP inspection rules, and request appending rules. Red Hat would like to thank Willy Tarreau of HAProxy upstream for reporting this issue. Upstream acknowledges Yves Lafon from the W3C as the original reporter. HAProxy is released as a Technology Preview in Red Hat Enterprise Linux 6. More information about Red Hat Technology Previews is available at https://access.redhat.com/support/offerings/techpreview/ All users of haproxy are advised to upgrade to this updated package, which contains a backported patch to correct this issue.

Commands:
Chapter 2. Deployment Scenarios There are three deployment scenarios for Red Hat Satellite in Amazon Web Services: One region setup Connecting on-premise and AWS region Connecting different regions Figure 2.1. Scenario 1: One region setup The least complex configuration of Satellite Server in Amazon Web Services consists of both Satellite Server and the content hosts residing within the same region and within the Virtual Private Cloud (VPC). You can also use a different availability zone. Scenario 2: Connecting on-premise and AWS region Create a VPN connection between the on-premise location and the AWS region where the Capsule resides. It is also possible to use the external host name of Satellite Server when you register the instance which runs Capsule Server. Option 1: Site-to-Site VPN connection between the AWS region and the On-Premise Datacenter Option 2: Direct connection using the External DNS host name Scenario 3: Connecting different regions Create a site-to-site VPN connection between the different regions so that you can use the Internal DNS host name when you register the instance that runs Capsule Server to Satellite Server. If you do not establish a site-to-site VPN connection, use the external DNS host name when you register the instance that runs Capsule Server to Satellite Server. Note Most Public Cloud Providers do not charge for data being transferred into a region, or between availability zones within a single region; however, they do charge for data leaving the region to the Internet. Option 1: Site-to-Site VPN connection between AWS regions Option 2: Direct connection using the External DNS host name

Commands:
Chapter 1. Overview of Builds Builds is an extensible build framework based on the Shipwright project , which you can use to build container images on an OpenShift Dedicated cluster. You can build container images from source code and Dockerfiles by using image build tools, such as Source-to-Image (S2I) and Buildah. You can create and apply build resources, view logs of build runs, and manage builds in your OpenShift Dedicated namespaces. Builds includes the following capabilities: Standard Kubernetes-native API for building container images from source code and Dockerfiles Support for Source-to-Image (S2I) and Buildah build strategies Extensibility with your own custom build strategies Execution of builds from source code in a local directory Shipwright CLI for creating and viewing logs, and managing builds on the cluster Integrated user experience with the Developer perspective of the OpenShift Dedicated web console Note Because Builds releases on a different cadence from OpenShift Dedicated, the Builds documentation is now available as a separate documentation set at builds for Red Hat OpenShift .

Commands:
8.61. fontconfig 8.61.1. RHBA-2014:0554 - fontconfig bug fix update Updated fontconfig packages that fix one bug are now available for Red Hat Enterprise Linux 6. The fontconfig packages contain the font configuration and customization library, which is designed to locate fonts within the system and select them according to the requirements specified by the applications. Bug Fixes BZ# 1035416 Previously, when the font cache file was stored on a Network File System (NFS), the fontconfig library sometimes did not handle mmap() calls correctly. As a consequence, applications using fontconfig, for example the GNOME terminal, could terminate unexpectedly with a bus error. With this update, the FONTCONFIG_USE_MMAP environment variable has been added to handle the mmap() calls regardless of the file system, and these calls are no longer used if the cache file is stored on an NFS. As a result, the bus errors no longer occur in the described situation. BZ# 1099546 Previously, the 25-no-bitmap-fedora.conf file name contained the word 'fedora', although file names in Red Hat Enterprise Linux are not supposed to include the word 'Fedora'. With this update, 25-no-bitmap-fedora.conf has been renamed to 25-no-bitmap-dist.conf, and the spec file has been updated. Users of fontconfig are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 6. Known issues This section lists the known issues for AMQ Streams 1.6. Issue Number ENTMQST-2030 - kafka-ack reports javax.management.InstanceAlreadyExistsException: kafka.admin.client:type=app-info,id=<client_id>with client.id set Description If the bin/kafka-acls.sh utility is used in combination with the --bootstrap-server parameter to add or remove an ACL, the operation is successful but a warning is generated. The reason for the warning is that a second AdminClient instance is created. This will be fixed in a future release of Kafka.

Commands:
2.3.3. Disabling ACPI Completely in the grub.conf File The preferred method of disabling ACPI Soft-Off is with chkconfig management ( Section 2.3.1, "Disabling ACPI Soft-Off with chkconfig Management" ). If the preferred method is not effective for your cluster, you can disable ACPI Soft-Off with the BIOS power management ( Section 2.3.2, "Disabling ACPI Soft-Off with the BIOS" ). If neither of those methods is effective for your cluster, you can disable ACPI completely by appending acpi=off to the kernel boot command line in the grub.conf file. Important This method completely disables ACPI; some computers do not boot correctly if ACPI is completely disabled. Use this method only if the other methods are not effective for your cluster. You can disable ACPI completely by editing the grub.conf file of each cluster node as follows: Open /boot/grub/grub.conf with a text editor. Append acpi=off to the kernel boot command line in /boot/grub/grub.conf (refer to Example 2.12, "Kernel Boot Command Line with acpi=off Appended to It" ). Reboot the node. When the cluster is configured and running, verify that the node turns off immediately when fenced. Note You can fence the node with the fence_node command or Conga . Example 2.12. Kernel Boot Command Line with acpi=off Appended to It In this example, acpi=off has been appended to the kernel boot command line - the line starting with "kernel /vmlinuz-2.6.18-36.el5".

Commands:
grub.conf generated by anaconda # Note that you do not have to rerun grub after making changes to this file NOTICE: You have a /boot partition. This means that all kernel and initrd paths are relative to /boot/, eg. root (hd0,0) kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 serial --unit=0 --speed=115200 terminal --timeout=5 serial console title Red Hat Enterprise Linux Server (2.6.18-36.el5) root (hd0,0) kernel /vmlinuz-2.6.18-36.el5 ro root=/dev/VolGroup00/LogVol00 console=ttyS0,115200n8 acpi=off initrd /initrd-2.6.18-36.el5.img
8.3.2. Installing from a Hard Drive The Select Partition screen applies only if you are installing from a disk partition (that is, you selected Hard Drive in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd boot option, you already specified a partition. Figure 8.5. Selecting Partition Dialog for Hard Drive Installation Select the partition containing the ISO files from the list of available partitions. Internal IDE, SATA, SCSI, and USB drive device names begin with /dev/sd . Each individual drive has its own letter, for example /dev/sda . Each partition on a drive is numbered, for example /dev/sda1 . Also specify the Directory holding images . Enter the full directory path from the drive that contains the ISO image files. The following table shows some examples of how to enter this information: Table 8.1. Location of ISO images for different partition types Partition type Volume Original path to files Directory to use VFAT D:\ D:\Downloads\RHEL6.9 /Downloads/RHEL6.9 ext2, ext3, ext4 /home /home/user1/RHEL6.9 /user1/RHEL6.9 If the ISO images are in the root (top-level) directory of a partition, enter a / . If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/ , and the images are in /home/new/ , you would enter /new/ . Important An entry without a leading slash may cause the installation to fail. Select OK to continue. Proceed with Chapter 9, Installing Using Anaconda .

Commands:
12.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: allow_postfix_local_write_mail_spool Having this Boolean enables Postfix to write to the local mail spool on the system. Postfix requires this Boolean to be enabled for normal operation when local spools are used. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
Chapter 4. SAP Automation and Performance 4.1. RHEL System Roles for SAP The Red Hat Enterprise Linux System Roles for SAP, provided exclusively with the Red Hat Enterprise Linux for SAP Solutions subscription, removes human error from complex and repetitive SAP configuration tasks, such as configuration of a Red Hat Enterprise Linux system for installation of SAP HANA or SAP NetWeaver software. Customers can use RHEL system roles for SAP to enforce SAP best practices for configuration and setup of both SAP NetWeaver and SAP HANA deployments based on RHEL. Additional resources For more information, see Red Hat Enterprise Linux System Roles for SAP . 4.2. tuned To ensure that RHEL is configured appropriately to best support SAP workloads, the RHEL for SAP Solutions provides tuned profiles "sap" and "sap-hana", which contain many of the SAP best practices and some additional configure settings. Additional resources For more information, see Getting started on your SAP HANA journey with RHEL 8 for SAP Solutions and SAP Note 2777782 . 4.3. Compatibility libraries RHEL for SAP Solutions provides additional GCC runtime compatibility libraries required by newer SAP NetWeaver and SAP HANA releases. These GCC runtime compatibility libraries can be installed independently of the standard GCC runtime libraries provided by RHEL. 4.4. Smart Management The RHEL subscription includes the Smart Management Add-on to provide easy management and updates of Red Hat Enterprise Linux systems by using Red Hat Satellite Server.

Commands:
7.7. ip6tables The introduction of the -generation Internet Protocol, called IPv6, expands beyond the 32-bit address limit of IPv4 (or IP). IPv6 supports 128-bit addresses and, as such, carrier networks that are IPv6 aware are able to address a larger number of routable addresses than IPv4. Red Hat Enterprise Linux supports IPv6 firewall rules using the Netfilter 6 subsystem and the ip6tables command. The first step in using ip6tables is to start the ip6tables service. This can be done with the command: Warning The iptables services must be turned off to use the ip6tables service exclusively: To make ip6tables start by default whenever the system is booted, change the runlevel status on the service using chkconfig . The syntax is identical to iptables in every aspect except that ip6tables supports 128-bit addresses. For example, SSH connections on a IPv6-aware network server can be enabled with the following rule: For more information about IPv6 networking, refer to the IPv6 Information Page at http://www.ipv6.org/ .

Commands:
service ip6tables start
service iptables stop chkconfig iptables off
chkconfig --level 345 ip6tables on
ip6tables -A INPUT -i eth0 -p tcp -s 3ffe:ffff:100::1/128 --dport 22 -j ACCEPT
4.73. gmp 4.73.1. RHBA-2012:0365 - gmp bug fix update An updated gmp package that fixes one bug is now available for Red Hat Enterprise Linux 6. The gmp package contains GNU MP, a library for arbitrary precision arithmetic, signed integers operations, rational numbers and floating point numbers. GNU MP is designed for speed, for both small and very large operands. Bug Fix BZ# 798771 Previously, the interface provided by the gmp library was changed. This resulted in one exported symbol being absent in Red Hat Enterprise Linux 6 (when compared to the Red Hat Enterprise Linux 5 system). In addition, the symbol could have been reported as missing under certain circumstances. To fix this problem, this update adds the missing symbol back to the library. All users of gmp are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 1. Introduction to Federal Information Processing Standards (FIPS) The Federal Information Processing Standards (FIPS) provides guidelines and requirements for improving security and interoperability across computer systems and networks. The FIPS 140-2 and 140-3 series apply to cryptographic modules at both the hardware and software levels. The National Institute of Standards and Technology in the United States implements a cryptographic module validation program with searchable lists of both in-process and approved cryptographic modules. Red Hat Enterprise Linux (RHEL) brings an integrated framework to enable FIPS 140 compliance system-wide. When operating under FIPS mode, software packages using cryptographic libraries are self-configured according to the global policy. Most of the packages provide a way to change the default alignment behavior for compatibility or other needs. Red Hat build of OpenJDK 21 is a FIPS policy-aware package. Additional resources For more information about the cryptographic module validation program, see Cryptographic Module Validation Program CMVP on the National Institute of Standards and Technology website. For more information on how to install RHEL with FIPS mode enabled, see Installing a RHEL 8 system with FIPS mode enabled . For more information on how to enable FIPS mode after installing RHEL, see Switching the system to FIPS mode . For more information on how to run Red Hat build of OpenJDK in FIPS mode on RHEL. See Running OpenJDK in FIPS mode on RHEL . For more information on Red Hat compliance with Government Standards, see Government Standards .

Commands:
Appendix B. RHEL 9 repositories If your system is registered to the Red Hat Content Delivery Network (CDN) using the Red Hat Subscription Manager (RHSM), RHEL 9 repositories are automatically enabled during the in-place upgrade. However, on systems registered to Red Hat Satellite using RHSM, you must manually enable and synchronize both RHEL 8 and RHEL 9 repositories before running the pre-upgrade report. Note Make sure to enable the target OS version of each repository, for example 9.4. If you have enabled only the RHEL 9 version of the repositories, the in-place upgrade is inhibited. If you plan to use Red Hat Satellite during the upgrade, you must enable and synchronize at least the following RHEL 9 repositories before the upgrade using either the Satellite web UI or the hammer repository-set enable and hammer product synchronize commands: Table B.1. RHEL 9 repositories Architecture Repository Repository ID Repository name Release version 64-bit Intel and AMD BaseOS rhel-9-for-x86_64-baseos-rpms Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs) x86_64 <target_os_version> AppStream rhel-9-for-x86_64-appstream-rpms Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs) x86_64 <target_os_version> 64-bit ARM BaseOS rhel-9-for-aarch64-baseos-rpms Red Hat Enterprise Linux 9 for ARM 64 - BaseOS (RPMs) aarch64 <target_os_version> AppStream rhel-9-for-aarch64-appstream-rpms Red Hat Enterprise Linux 9 for ARM 64 - AppStream (RPMs) aarch64 <target_os_version> IBM Power (little endian) BaseOS rhel-9-for-ppc64le-baseos-rpms Red Hat Enterprise Linux 9 for Power, little endian - BaseOS (RPMs) ppc64le <target_os_version> AppStream rhel-9-for-ppc64le-appstream-rpms Red Hat Enterprise Linux 9 for Power, little endian - AppStream (RPMs) ppc64le <target_os_version> IBM Z BaseOS rhel-9-for-s390x-baseos-rpms Red Hat Enterprise Linux 9 for IBM z Systems - BaseOS (RPMs) s390x <target_os_version> AppStream rhel-9-for-s390x-appstream-rpms Red Hat Enterprise Linux 9 for IBM z Systems - AppStream (RPMs) s390x <target_os_version> Replace <target_os_version> with the target OS version, for example 9.4 .

Commands: