mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Performing the pre-customization tasks 2.1. Working with ISO images In this section, you will learn how to: Extract a Red Hat ISO. Create a new boot image containing your customizations. 2.2. Downloading RH boot images Before you begin to customize the installer, download the Red Hat-provided boot images. You can obtain Red Hat Enterprise Linux 9 boot media from the Red Hat Customer Portal after login to your account. Note Your account must have sufficient entitlements to download Red Hat Enterprise Linux 9 images. You must download either the Binary DVD or Boot ISO image and can use any of the image variants (Server or ComputeNode). You cannot customize the installer using the other available downloads, such as the KVM Guest Image or Supplementary DVD; other available downloads, such as the KVM Guest Image or Supplementary DVD . For more information about the Binary DVD and Boot ISO downloads, see Product Downloads . 2.3. Extracting Red Hat Enterprise Linux boot images Perform the following procedure to extract the contents of a boot image. Procedure Ensure that the directory /mnt/iso exists and nothing is currently mounted there. Mount the downloaded image. Where path/to/image.iso is the path to the downloaded boot image. Create a working directory where you want to place the contents of the ISO image. Copy all contents of the mounted image to your new working directory. Make sure to use the -p option to preserve file and directory permissions and ownership. Unmount the image. Additional resources For more information about the Binary DVD and Boot ISO downloads, see Product Downloads .

Commands:
mount -t iso9660 -o loop path/to/image.iso /mnt/iso
mkdir /tmp/ISO
cp -pRf /mnt/iso /tmp/ISO
umount /mnt/iso
5.4. Configure CXF for a Web Service Data Source: Logging CXF configuration can control the logging of requests and responses for specific or all ports. Logging, when enabled, is performed at an INFO level to the org.apache.cxf.interceptor context. Prerequisites The web service data source must be configured and the ConfigFile and EndPointName properties must be configured for CXF. Procedure 5.3. Configure CXF for a Web Service Data Source: Logging Modify the CXF Configuration File Open the CXF configuration file for the web service data source and add your desired logging properties. The following is an example of a CXF configuration file for a web service data source that enables logging: References For more information about CXF logging configuration options see http://cxf.apache.org/docs/debugging-and-logging.html .

Commands:
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jaxws="http://cxf.apache.org/jaxws" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd"> <jaxws:client name="{http://teiid.org}teiid" createdFromAPI="true"> <jaxws:features> <bean class="org.apache.cxf.feature.LoggingFeature"/> </jaxws:features> </jaxws:client> </beans>
Chapter 88. Configuring a logging utility in the decision engine The decision engine uses the Java logging API SLF4J for system logging. You can use one of the following logging utilities with the decision engine to investigate decision engine activity, such as for troubleshooting or data gathering: Logback Apache Commons Logging Apache Log4j java.util.logging package Procedure For the logging utility that you want to use, add the relevant dependency to your Maven project or save the relevant XML configuration file in the org.drools package of your Red Hat Process Automation Manager distribution: Example Maven dependency for Logback <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>USD{logback.version}</version> </dependency> Example logback.xml configuration file in org.drools package <configuration> <logger name="org.drools" level="debug"/> ... <configuration> Example log4j.xml configuration file in org.drools package <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"> <category name="org.drools"> <priority value="debug" /> </category> ... </log4j:configuration> Note If you are developing for an ultra light environment, use the slf4j-nop or slf4j-simple logger.

Commands:
<dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>USD{logback.version}</version> </dependency>
<configuration> <logger name="org.drools" level="debug"/> <configuration>
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/"> <category name="org.drools"> <priority value="debug" /> </category> </log4j:configuration>
7.55. febootstrap 7.55.1. RHBA-2013:0432 - febootstrap bug fix update Updated febootstrap packages that fix one bug are now available for Red Hat Enterprise Linux 6. The febootstrap packages provide a tool to create a basic Red Hat Enterprise Linux or Fedora file system, and build initramfs (initrd.img) or file system images. Bug Fix BZ#803962 The "febootstrap-supermin-helper" program is used when opening a disk image using the libguestfs API, or as part of virt-v2v conversion. Previously, this tool did not always handle the "-u" and "-g" options correctly when the host used an LDAP server to resolve user names and group names. This caused the virt-v2v command to fail when LDAP was in use. With this update, the "febootstrap-supermin-helper" program has been modified to parse the "-u" and "-g" options correctly, so that virt-v2v works as expected in the described scenario. Users of febootstrap are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 16. Updating Red Hat Certificate System To update Certificate System and the operating system it is running on, use the dnf update command. This downloads, verifies, and installs updates for Certificate System as well as operating system packages. For example: This downloads, verifies, and installs updates for Certificate System as well as operating system packages. You can verify the version number before and after updating packages, to confirm they were successfully installed. Important Updating Certificate System requires the PKI infrastructure to be restarted. We suggest scheduling a maintenance window to take the PKI infrastructure offline and install the update. To optionally download updates without installing, use the --downloadonly option in the above procedure: The downloaded packages are stored in the /var/cache/yum/ directory. The dnf update will later use the packages if they are the latest versions.

Commands:
dnf update
dnf update --downloadonly
Appendix A. Revision History Revision History Revision 6.6.0-4 Thur May 25 2017 John Brier JDG-984: Removed references to unsupported mixed Client-Server and embedded cluster Revision 6.6.0-3 Wed 7 Sep 2016 Christian Huffman Updating for 6.6.1. Revision 6.6.0-2 Wed 24 Feb 2016 Christian Huffman BZ-1310604: Included note on updates to source cluster during rolling upgrades. Revision 6.6.0-1 Tue 16 Feb 2016 Christian Huffman Included chapter on Integration with the Spring Framework. Revision 6.6.0-0 Thu 7 Jan 2016 Christian Huffman Initial draft for 6.6.0. BZ-1296210: Added note on deprecation of MapReduce. BZ-1269542: Included information on @CacheEntryExpired. Updated versions.

Commands:
Appendix A. Using Your Subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Streams entries in the JBOSS INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Revised on 2020-12-02 15:51:49 UTC

Commands:
Chapter 7. Subscription Management 7.1. Subscription Manager String Updates In Red Hat Enterprise Linux 6.4, several strings have been renamed in Subscription Manager: subscribe was renamed to attach auto-subscribe was renamed to auto-attach unsubscribe was renamed to remove consumer was renamed to system or unit Testing Proxy Connection The Proxy Configuration dialog now allows users to test a connection to a proxy after entering a value. Subscribe or Unsubscribe Multiple Entitlements Subscription Manager is now able to subscribe (attach) or unsubscribe (remove) multiple entitlements using their serial numbers at once. Activation Keys Support in the GUI The Subscription Manager graphical user interface now allows you to register a system using an activation key . Activation keys allow users to preconfigure subscriptions for a system before it is registered. Registering Against External Servers Support for the selection of a remote server during the registration of a system is now supported in Subscription Manager. The Subscription Manager user interface provides an option to choose a URL of a server to register against, together with a port and a prefix, during the registration process. Additionally, when registering on the command line, the --serverurl option can be used to specify the server to register against. For more information about this feature, refer to the section Registering, Unregistering, and Reregistering a System in the Subscription Management Guide . Usability Changes in the GUI The Subscription Manager GUI has been enhanced with various changes based on customer feedback. 7.2. Subscription Asset Manager Installation on Offline Systems Subscription Asset Manager is now available as an ISO image and can be obtained from Content Delivery Network and Red Hat Network. It is therefore possible to install Subscription Asset Manager on offline systems. Reduced System Registration Workload It is now possible to configure a kickstart file with instructions to connect to Subscription Asset Manager and to automatically register and subscribe the system. This significantly reduces workloads of registering a large number of systems. Migration Red Hat Enterprise Linux 6.4 provides subscription-manager which includes the rhn-migrate-classic-to-rhsm script. The script has the --serverurl parameter that allows the user to point the system to an existing or on-premise installation of Subscription Asset Manager, and automatically migrates the system to use Subscription Asset Manager for its content. Note For more information about the 1.2 release of Subscription Asset Manager, refer to the Red Hat Subscription Asset Manager 1.2 Release Notes located at: https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Asset_Manager/1.2/html-single/Release_Notes/index.html

Commands:
1.2. Before Setting Up GFS2 Before you install and set up GFS2, note the following key characteristics of your GFS2 file systems: GFS2 nodes Determine which nodes in the cluster will mount the GFS2 file systems. Number of file systems Determine how many GFS2 file systems to create initially. (More file systems can be added later.) File system name Determine a unique name for each file system. The name must be unique for all lock_dlm file systems over the cluster. Each file system name is required in the form of a parameter variable. For example, this book uses file system names mydata1 and mydata2 in some example procedures. Journals Determine the number of journals for your GFS2 file systems. One journal is required for each node that mounts a GFS2 file system. GFS2 allows you to add journals dynamically at a later point as additional servers mount a file system. For information on adding journals to a GFS2 file system, see Section 4.7, "Adding Journals to a File System" . Storage devices and partitions Determine the storage devices and partitions to be used for creating logical volumes (by means of CLVM) in the file systems. Note You may see performance problems with GFS2 when many create and delete operations are issued from more than one node in the same directory at the same time. If this causes performance problems in your system, you should localize file creation and deletions by a node to directories specific to that node as much as possible. For further recommendations on creating, using, and maintaining a GFS2 file system. see Chapter 2, GFS2 Configuration and Operational Considerations .

Commands:
Chapter 6. Known issues Sometimes a Cryostat release might contain an issue or issues that Red Hat acknowledges and might fix at a later stage during the product's development. Review each known issue for its description and its resolution. Subviews such as /recordings/create are not accessible when visited directly in URL paths Description The Cryostat web console is not accessible from a web browser when you attempt to access the console through a URL path that includes a subview such as /topology/create-custom-target , /rules/create , or /recordings/create . For example, if you enter a URL path such as https:// my_cryostat_domain /recordings/create , the Cryostat console shows a blank page. Workaround Do not specify subviews in URL paths. For example, if you want to access https:// my_cryostat_domain /recordings/create , enter a URL path of https:// my_cryostat_domain /recordings in your web browser, and then click Create in the Cryostat web console. Active Recordings table fails to update when restarting a recording with the replace=always parameter Description If a client sends a request that includes the replace=always parameter to recreate an existing recording, the Active Recordings table in the Cryostat web console is not updated to show details of the new recording. Even though a Recording created notification is displayed, the new recording does not automatically appear in the Active Recordings table. Workaround Reload the Active Recordings page or navigate away from then back to the current page. The Active Recordings table then correctly displays the new recording.

Commands:
7.229. wireless-tools 7.229.1. RHBA-2015:1386 - wireless-tools bug fix update Updated wireless-tools packages that fix one bug are now available for Red Hat Enterprise Linux 6. The wireless-tools packages contain tools used to manipulate the Wireless Extensions. The Wireless Extension is an interface that allows the user to set Wireless LAN specific parameters and to get statistics for wireless networking equipment. Bug Fix BZ# 857920 In an environment with a large number of wireless access points, using the wicd connection manager or the network-manager tool to connect to a wireless network previously failed. With this update, the buffer limit of the "iwlist scan" command has been adjusted not to exceed the maximum iwlist buffer amount, which prevents this problem from occurring. Users of wireless-tools are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.202. mt-st 5.202.1. RHBA-2012:1409 - mt-st bug fix update Updated mt-st packages that fix one bug are now available for Red Hat Enterprise Linux 6. The mt-st package contains the mt and st tape drive management programs. Mt (for magnetic tape drives) and st (for SCSI tape devices) can control rewinding, ejecting, skipping files and blocks and more. Bug Fix BZ# 820245 Prior this update, the stinit init script did not support standard actions like "status" or "restart". As a consequence, an error code was returned. This update modifies the underlying code to use all use all standard actions. All users of mt-st are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Installing RHEL image builder Before using RHEL image builder, you must install it. 2.1. RHEL image builder system requirements The host that runs RHEL image builder must meet the following requirements: Table 2.1. RHEL image builder system requirements Parameter Minimal Required Value System type A dedicated host or virtual machine. Note that RHEL image builder is not supported in containers, including Red Hat Universal Base Images (UBI). Processor 2 cores Memory 4 GiB Disk space 20 GiB of free space in the ` /var/cache/` filesystem Access privileges root Network Internet connectivity to the Red Hat Content Delivery Network (CDN). Note If you do not have internet connectivity, use RHEL image builder in isolated networks. For that, you must override the default repositories to point to your local repositories to not connect to Red Hat Content Delivery Network (CDN). Ensure that you have your content mirrored internally or use Red Hat Satellite. Additional resources Configuring RHEL image builder repositories Provisioning to Satellite using a Red Hat image builder image 2.2. Installing RHEL image builder Install RHEL image builder to have access to all the osbuild-composer package functionalities. Prerequisites You are logged in to the RHEL host on which you want to install RHEL image builder. The host is subscribed to Red Hat Subscription Manager (RHSM) or Red Hat Satellite. You have enabled the BaseOS and AppStream repositories to be able to install the RHEL image builder packages. Procedure Install RHEL image builder and other necessary packages: osbuild-composer - A service to build customized RHEL operating system images. composer-cli - This package enables access to the CLI interface. cockpit-composer - This package enables access to the Web UI interface. The web console is installed as a dependency of the cockpit-composer package. Enable and start RHEL image builder socket: If you want to use RHEL image builder in the web console, enable and start it. The osbuild-composer and cockpit services start automatically on first access. Load the shell configuration script so that the autocomplete feature for the composer-cli command starts working immediately without logging out and in: Verification Verify that the installation works by running composer-cli : Troubleshooting You can use a system journal to track RHEL image builder activities. Additionally, you can find the log messages in the file. To find the journal output for traceback, run the following commands: To show the local worker, such as the osbuild-worker@.service , a template service that can start multiple service instances: To show the running services:

Commands:
dnf install osbuild-composer composer-cli cockpit-composer
systemctl enable --now osbuild-composer.socket
systemctl enable --now cockpit.socket
source /etc/bash_completion.d/composer-cli
composer-cli status show
journalctl | grep osbuild
journalctl -u osbuild-worker*
journalctl -u osbuild-composer.service
4.354. xorg-x11-drv-mga 4.354.1. RHBA-2011:1620 - xorg-x11-drv-mga bug fix and enhancement update Updated xorg-x11-drv-mga packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-mga packages porvide a video driver for Matrox G-series chipsets for the X.Org implementation of the X Window System. The xorg-x11-drv-mga packages have been upgraded to upstream version 1.4.13, which provides a number of bug fixes over the version. (BZ# 713858 ) Bug Fixes BZ# 713388 Previously, the MGA driver rendered the image incorrectly on big-endian architectures, including PowerPC and 64-bit PowerPC. Consequently, the display showed altered colors. With this update, the colors are displayed correctly in the described scenario. BZ# 745080 Previously, the MGA driver caused a shift in the video screen. Consequently, the screen became corrupted and the windows were pushed around randomly. This update, modifies the code so that the MGA driver no longer causes problems for the video screen. Enhancement BZ# 526104 This update adds support for ServerEngines Pilot III to the xorg-x11-drv-mga packages. All users of the Xorg x11 MGA driver, are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 2. Upgrade requirements You must upgrade your custom resources to use API version v1beta2 before upgrading to AMQ Streams version 1.8. The v1beta2 API version for all custom resources was introduced with AMQ Streams 1.7. For AMQ Streams 1.8, v1alpha1 and v1beta1 API versions were removed from all AMQ Streams custom resources apart from KafkaTopic and KafkaUser . Upgrade of the custom resources to v1beta2 prepares AMQ Streams for a move to Kubernetes CRD v1 , which is required for Kubernetes v1.22. If you are upgrading from an AMQ Streams version prior to version 1.7: Upgrade to AMQ Streams 1.7 Convert the custom resources to v1beta2 Upgrade to AMQ Streams 1.8 See Deploying and upgrading AMQ Streams . 2.1. Upgrading custom resources to the v1beta2 version To support the upgrade of custom resources to v1beta2 , AMQ Streams provides an API conversion tool , which you can download from the AMQ Streams download site . You perform the custom resources upgrades in two steps. Step one: Convert the format of custom resources Using the API conversion tool, you can convert the format of your custom resources into a format applicable to v1beta2 in one of two ways: Converting the YAML files that describe the configuration for AMQ Streams custom resources Converting AMQ Streams custom resources directly in the cluster Alternatively, you can manually convert each custom resource into a format applicable to v1beta2 . Instructions for manually converting custom resources are included in the documentation. Step two: Upgrade CRDs to v1beta2 , using the API conversion tool with the crd-upgrade command, you must set v1beta2 as the storage API version in your CRDs. You cannot perform this step manually. For full instructions, see Upgrading AMQ Streams .

Commands: