mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix B. Troubleshooting DNF modules If DNF modules fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows. List the enabled modules: B.1. Ruby If Ruby module fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows: List the enabled modules: If the Ruby 2.5 module has already been enabled, perform a module reset: B.2. PostgreSQL If PostgreSQL module fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows: List the enabled modules: If the PostgreSQL 10 module has already been enabled, perform a module reset: If you created a PostgreSQL 10 database, perform an upgrade: Enable the DNF modules: Install the PostgreSQL upgrade package: Perform the upgrade:

Commands:
dnf module list --enabled
dnf module list --enabled
dnf module reset ruby
dnf module list --enabled
dnf module reset postgresql
dnf module enable satellite-capsule:el8
dnf install postgresql-upgrade
postgresql-setup --upgrade
7.125. mdadm 7.125.1. RHBA-2015:1255 - mdadm bug fix and enhancement update Updated mdadm packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The mdadm packages contain a utility for creating, managing, and monitoring Linux multiple disk (MD) devices. Bug Fixes BZ# 1146536 Previously, installing the mdadm packages also installed a redundant udev rule file. With this update, the spec file of the mdadm packages has been adjusted to prevent the redundant rule file from being installed. BZ# 1159399 Prior to this update, when the "AUTO" keyword was configured in the mdadm.conf file, the mdadm utility did not behave accordingly. The parsing of "AUTO" has been corrected, and mdadm now respects this keyword as expected. BZ# 1146994 Prior to this update, when running an Internal Matrix Storage Manager (IMSM) volume as a non-root user, a race condition in some cases occurred that prevented the assembly of the volume. With this update, the mdadm packages have been fixed and this race condition no longer occurs, allowing the array to be assembled as expected. BZ# 1211564 Previously, mdadm was unintentionally capable of creating more Internal Matrix Storage Manager (IMSM) raid volumes than was allowed by the "Max volumes" option in mdadm configuration. This update corrects the bug, and attempting to create a more IMSM raid volumes than set by "Max volumes" now generates an error and does not create the raid volumes. Enhancement BZ# 1211500 Internal Matrix Storage Manager (IMSM) now supports SATA and Non-volatile memory Express (NVMe) spanning. Users of mdadm are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
D.6. Outline Thumbnail View The Outline View also offers you a way to view a thumbnail sketch of your diagram regardless of its size. To view this diagram thumbnail from the Outline panel, click the Diagram Overview button at the top of the view. The diagram overview displays in the Outline View . Figure D.7. Outline View The view contains a thumbnail of your entire diagram. The shaded portion represents the portion visible in the Diagram Editor view. To move to a specific portion of your diagram, click the shaded area and drag to the position you want displayed in the Diagram Editor view. Figure D.8.

Commands:
Chapter 4. Deploying Red Hat Quay After you have configured your Red Hat Quay deployment, you can deploy it using the following procedures. Prerequisites The Red Hat Quay database is running. The Redis server is running. 4.1. Creating the YAML configuration file Use the following procedure to deploy Red Hat Quay locally. Procedure Enter the following command to create a minimal config.yaml file that is used to deploy the Red Hat Quay container: USD touch config.yaml Copy and paste the following YAML configuration into the config.yaml file: BUILDLOGS_REDIS: host: quay-server.example.com password: strongpassword port: 6379 DATABASE_SECRET_KEY: a8c2744b-7004-4af2-bcee-e417e7bdd235 DB_URI: postgresql://quayuser:quaypass@quay-server.example.com:5432/quay DISTRIBUTED_STORAGE_CONFIG: default: - LocalStorage - storage_path: /datastorage/registry DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS: [] DISTRIBUTED_STORAGE_PREFERENCE: - default SECRET_KEY: e9bd34f4-900c-436a-979e-7530e5d74ac8 SERVER_HOSTNAME: quay-server.example.com SETUP_COMPLETE: true USER_EVENTS_REDIS: host: quay-server.example.com password: strongpassword port: 6379 Create a directory to copy the Red Hat Quay configuration bundle to: USD mkdir USDQUAY/config Copy the Red Hat Quay configuration file to the directory: USD cp ~/Downloads/quay-config.tar.gz USDQUAY/config 4.2. Prepare local storage for image data Use the following procedure to set your local file system to store registry images. Procedure Create a local directory that will store registry images by entering the following command: USD mkdir USDQUAY/storage Set the directory to store registry images: USD setfacl -m u:1001:-wx USDQUAY/storage 4.3. Deploy the Red Hat Quay registry Use the following procedure to deploy the Quay registry container. Procedure Enter the following command to start the Quay registry container, specifying the appropriate volumes for configuration data and local storage for image data:

Commands:
touch config.yaml
BUILDLOGS_REDIS: host: quay-server.example.com password: strongpassword port: 6379 DATABASE_SECRET_KEY: a8c2744b-7004-4af2-bcee-e417e7bdd235 DB_URI: postgresql://quayuser:quaypass@quay-server.example.com:5432/quay DISTRIBUTED_STORAGE_CONFIG: default: - LocalStorage - storage_path: /datastorage/registry DISTRIBUTED_STORAGE_DEFAULT_LOCATIONS: [] DISTRIBUTED_STORAGE_PREFERENCE: - default SECRET_KEY: e9bd34f4-900c-436a-979e-7530e5d74ac8 SERVER_HOSTNAME: quay-server.example.com SETUP_COMPLETE: true USER_EVENTS_REDIS: host: quay-server.example.com password: strongpassword port: 6379
mkdir USDQUAY/config
cp ~/Downloads/quay-config.tar.gz USDQUAY/config
mkdir USDQUAY/storage
setfacl -m u:1001:-wx USDQUAY/storage
sudo podman run -d --rm -p 80:8080 -p 443:8443 --name=quay -v USDQUAY/config:/conf/stack:Z -v USDQUAY/storage:/datastorage:Z registry.redhat.io/quay/quay-rhel8:v3.10.9
14.3. Displaying Currently Assigned ID Ranges To display which ID ranges are configured for a server, use the following commands: ipa-replica-manage dnarange-show displays the current ID range that is set on all servers or, if you specify a server, only on the specified server, for example: ipa-replica-manage dnanextrange-show displays the ID range currently set on all servers or, if you specify a server, only on the specified server, for example: For more information about these two commands, see the ipa-replica-manage (1) man page.

Commands:
ipa-replica-manage dnarange-show masterA.example.com: 1001-1500 masterB.example.com: 1501-2000 masterC.example.com: No range set ipa-replica-manage dnarange-show masterA.example.com masterA.example.com: 1001-1500
ipa-replica-manage dnanextrange-show masterA.example.com: 1001-1500 masterB.example.com: No on-deck range set masterC.example.com: No on-deck range set ipa-replica-manage dnanextrange-show masterA.example.com masterA.example.com: 1001-1500
Chapter 1. Disaster recovery tools in IdM A good disaster recovery strategy combines the following tools to recover from a disaster as soon as possible with minimal data loss: Replication Replication copies database contents between IdM servers. If an IdM server fails, you can replace the lost server by creating a new replica based on one of the remaining servers. Virtual machine (VM) snapshots A snapshot is a view of a VM's operating system and applications on any or all available disks at a given point in time. After taking a VM snapshot, you can use it to return a VM and its IdM data to a state. IdM backups The ipa-backup utility allows you to take a backup of an IdM server's configuration files and its data. You can later use a backup to restore an IdM server to a state.

Commands:
3.4.2. Sharing a website It may not be possible to label files with the samba_share_t type, for example, when wanting to share a website in /var/www/html/ . For these cases, use the samba_export_all_ro Boolean to share any file or directory (regardless of the current label), allowing read only permissions, or the samba_export_all_rw Boolean to share any file or directory (regardless of the current label), allowing read and write permissions. The following example creates a file for a website in /var/www/html/ , and then shares that file through Samba, allowing read and write permissions. This example assumes the httpd , samba , samba-common , samba-client , and wget packages are installed: As the root user, create a /var/www/html/file1.html file. Copy and paste the following content into /var/www/html/file1.html : Run the ls -Z /var/www/html/file1.html command to view the SELinux context of file1.html : file1.index.html is labeled with the httpd_sys_content_t . By default, the Apache HTTP Server can access this type, but Samba cannot. Run the service httpd start command as the root user to start the Apache HTTP Server: Change into a directory your user has write access to, and run the wget http://localhost/file1.html command. Unless there are changes to the default configuration, this command succeeds: Edit /etc/samba/smb.conf as the root user. Add the following to the bottom of this file to share the /var/www/html/ directory through Samba: The /var/www/html/ directory is labeled with the httpd_sys_content_t type. By default, Samba cannot access files and directories labeled with the httpd_sys_content_t type, even if Linux permissions allow it. To allow Samba access, run the following command as the root user to enable the samba_export_all_ro Boolean: Do not use the -P option if you do not want the change to persist across reboots. Note that enabling the samba_export_all_ro Boolean allows Samba to access any type. Run service smb start as the root user to start smbd :

Commands:
<html> <h2>File being shared through the Apache HTTP Server and Samba.</h2> </html>
~]USD ls -Z /var/www/html/file1.html -rw-r--r--. root root unconfined_u:object_r:httpd_sys_content_t:s0 /var/www/html/file1.html
~]# service httpd start Starting httpd: [ OK ]
~]USD wget http://localhost/file1.html Resolving localhost... 127.0.0.1 Connecting to localhost|127.0.0.1|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 84 [text/html] Saving to: `file1.html.1' 100%[=======================>] 84 --.-K/s in 0s `file1.html.1' saved [84/84]
[website] comment = Sharing a website path = /var/www/html/ public = no writable = no
~]# setsebool -P samba_export_all_ro on
~]# service smb start Starting SMB services: [ OK ]
Appendix A. Getting More Information For more information on Software Collection packaging, Red Hat Developers, the Red Hat Software Collections and Red Hat Developer Toolset offerings, and Red Hat Enterprise Linux, see the resources listed below. A.1. Red Hat Developers Overview of Red Hat Software Collections on Red Hat Developers - The Red Hat Developers portal provides a number of tutorials to get you started with developing code using different development technologies. This includes the Node.js, Perl, PHP, Python, and Ruby Software Collection. Red Hat Developer Blog - The Red Hat Developer Blog contains up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources for those who are designing and developing applications based on Red Hat technologies.

Commands:
Chapter 2. Performance Monitoring Tools This chapter briefly describes some of the performance monitoring and configuration tools available for Red Hat Enterprise Linux 7. Where possible, this chapter directs readers to further information about how to use the tool, and examples of real life situations that the tool can be used to resolve. The following knowledge base article provides a more comprehensive list of performance monitoring tools suitable for use with Red Hat Enterprise Linux: https://access.redhat.com/site/solutions/173863 . 2.1. /proc The /proc "file system" is a directory that contains a hierarchy of files that represent the current state of the Linux kernel. It allows users and applications to see the kernel's view of the system. The /proc directory also contains information about system hardware and any currently running processes. Most files in the /proc file system are read-only, but some files (primarily those in /proc/sys) can be manipulated by users and applications to communicate configuration changes to the kernel. For further information about viewing and editing files in the /proc directory, refer to the Red Hat Enterprise Linux 7 System Administrator's Guide .

Commands:
7.101. kdelibs 7.101.1. RHBA-2012:1251 - kdelibs bug fix update Updated kdelibs packages that fix various bugs are now available for Red Hat Enterprise Linux 6. The kdelibs packages provide libraries for the K Desktop Environment (KDE). Bug Fixes BZ# 587016 Prior to this update, the KDE Print dialog did not remember settings, nor did it allow the user to save the settings. Consequent to this, when printing several documents, users were forced to manually change settings for each printed document. With this update, the KDE Print dialog retains settings as expected. BZ# 682611 When the system was configured to use the Traditional Chinese language (the zh_TW locale), Konqueror incorrectly used a Chinese (zh_CN) version of its splash page. This update ensures that Konqueror uses the correct locale. BZ#734734 Previously, clicking the system tray to display hidden icons could cause the Plasma Workspaces to consume an excessive amount of CPU time. This update applies a patch that fixes this error. BZ#754161 When using Konqueror to recursively copy files and directories, if one of the subdirectories was not accessible, no warning or error message was reported to the user. This update ensures that Konqueror displays a proper warning message in this scenario. BZ#826114 Prior to this update, an attempt to add "Terminal Emulator" to the Main Toolbar caused Konqueror to terminate unexpectedly with a segmentation fault. With this update, the underlying source code has been corrected to prevent this error so that users can now use this functionality as expected. All users of kdelibs are advised to upgrade to these updated packages, which fix these bugs. 7.101.2. RHSA-2012:1418 - Critical: kdelibs security update Updated kdelibs packages that fix two security issues are now available for Red Hat Enterprise Linux 6 FasTrack. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The kdelibs packages provide libraries for the K Desktop Environment (KDE). Konqueror is a web browser. CVE-2012-4512 A heap-based buffer overflow flaw was found in the way the CSS (Cascading Style Sheets) parser in kdelibs parsed the location of the source for font faces. A web page containing malicious content could cause an application using kdelibs (such as Konqueror) to crash or, potentially, execute arbitrary code with the privileges of the user running the application. CVE-2012-4513 A heap-based buffer over-read flaw was found in the way kdelibs calculated canvas dimensions for large images. A web page containing malicious content could cause an application using kdelibs to crash or disclose portions of its memory. Users should upgrade to these updated packages, which contain backported patches to correct these issues. The desktop must be restarted (log out, then log back in) for this update to take effect.

Commands:
Chapter 1. Overview of Kaoto Important The VS Code extensions for Apache Camel are listed as development support. For more information about the scope of development support, see Development Support Scope of Coverage for Red Hat Build of Apache Camel . Kaoto is an acronym for K amel O rchestration T ool. It is a low code and no code integration designer to create and edit integrations based on Apache Camel . Kaoto is extendable, flexible, and adaptable to different use cases. For more information about the history of Kaoto, see Statistics and History of Kaoto . Kaoto offers a rich catalog of building blocks for use in graphical design. By default, Kaoto loads the official upstream Camel Catalog and Kamelet Catalog. Benefits of using Kaoto can be listed as follows: Enhanced Visual Development Experience By leveraging Kaoto's visual designing capabilities, users can intuitively create, view, and edit Camel integrations through the user interface. This low-code/no-code approach significantly reduces the learning curve for new users and accelerates the development process for seasoned developers. Comprehensive Component Catalog Accessibility Kaoto provides immediate access to a rich catalog of Camel components, enterprise integration patterns (EIPs), and Kamelets. This extensive Catalog enables developers to easily find and implement the necessary components for their integration solutions. By having these resources readily available, developers can focus more on solving business problems rather than spending time searching for and learning about different components. Streamlined Integration Development Process The platform is designed with an efficient user experience in mind, optimizing the steps required to create comprehensive integrations. This efficiency is achieved through features like auto-completion, configuration forms, and interactive feedback mechanisms. As a result, developers can quickly assemble and configure integrations, reducing the overall development time. This streamlined process encourages experimentation and innovation by making it easier to prototype and test different approaches. 1.1. Why Kaoto? Camel at Heart Using the power of Apache Camel: Kaoto utilizes the Apache Camel models and schemas to always offer you all available Camel features. Local Development VS Code Extension: We provide Kaoto as an extension you can install from the Microsoft Marketplace and also from the Open VSX Marketplace . LCNC: Low Code and No Code Care about developers: You can seamlessly switch between any IDE and Kaoto, allowing mixed teams and converting low-code integrators to developers. FLOSS heart Free Libre and Open Source Forever: Truly open with no vendor lock-in. Use, reuse, share, modify, and resell to the users' needs.

Commands:
Appendix A. Initialization Script for Provisioning Examples If you have not followed the examples in Managing Content , you can use the following initialization script to create an environment for provisioning examples. Procedure Create a script file ( content-init.sh ) and include the following: Set executable permissions on the script: Download a copy of your Red Hat Subscription Manifest from the Red Hat Customer Portal and run the script on the manifest: This imports the necessary Red Hat content for the provisioning examples in this guide.

Commands:
#!/bin/bash MANIFEST=USD1 Import the content from Red Hat CDN hammer organization create --name "ACME" --label "ACME" --description "Our example organization for managing content." hammer subscription upload --file ~/USDMANIFEST --organization "ACME" hammer repository-set enable --name "Red Hat Enterprise Linux 7 Server (RPMs)" --releasever "7Server" --basearch "x86_64" --product "Red Hat Enterprise Linux Server" --organization "ACME" hammer repository-set enable --name "Red Hat Enterprise Linux 7 Server (Kickstart)" --releasever "7Server" --basearch "x86_64" --product "Red Hat Enterprise Linux Server" --organization "ACME" hammer repository-set enable --name "Red Hat Satellite Client 6 (for RHEL 7 Server) (RPMs)" --basearch "x86_64" --product "Red Hat Enterprise Linux Server" --organization "ACME" hammer product synchronize --name "Red Hat Enterprise Linux Server" --organization "ACME" Create our application life cycle hammer lifecycle-environment create --name "Development" --description "Environment for ACME's Development Team" --prior "Library" --organization "ACME" hammer lifecycle-environment create --name "Testing" --description "Environment for ACME's Quality Engineering Team" --prior "Development" --organization "ACME" hammer lifecycle-environment create --name "Production" --description "Environment for ACME's Product Releases" --prior "Testing" --organization "ACME" Create and publish our Content View hammer content-view create --name "Base" --description "Base operating system" --repositories "Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server,Red Hat Satellite Client 6 for RHEL 7 Server RPMs x86_64" --organization "ACME" hammer content-view publish --name "Base" --description "Initial Content View for our operating system" --organization "ACME" hammer content-view version promote --content-view "Base" --version 1 --to-lifecycle-environment "Development" --organization "ACME" hammer content-view version promote --content-view "Base" --version 1 --to-lifecycle-environment "Testing" --organization "ACME" hammer content-view version promote --content-view "Base" --version 1 --to-lifecycle-environment "Production" --organization "ACME"
chmod +x content-init.sh
./content-init.sh manifest_98f4290e-6c0b-4f37-ba79-3a3ec6e405ba.zip
5.27. cluster-glue 5.27.1. RHBA-2012:0942 - cluster-glue bug fix update Updated cluster-glue packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The cluster-glue packages contain a collection of common tools that are useful for writing cluster managers such as Pacemaker. Bug Fixes BZ# 758127 Previously, the environment variable "LRMD_MAX_CHILDREN" from the program /etc/sysconfig/pacemaker was not properly evaluated. As a result, the "max_child_count" variable in the Local Resource Management Daemon (lrmd) was not modified. With this update, the bug has been fixed so that the environment variable "LRMD_MAX_CHILDREN" is evaluated as expected. BZ# 786746 Previously, if Pacemaker attempted to cancel a recurring operation while the operation was executed, the Local Resource Management Daemon (lrmd) did not cancel the operation correctly. As a result the operation was not removed from the repeat list. With this update, a canceled operation is now marked to be removed from the repeat operation list if it is canceled during the execution so that recurring canceled operations are never executed again. All cluster-glue users are advised to upgrade to these updated packages, which fix these bugs.

Commands:
3.7. Configure Pass-Through Authentication Procedure 3.1. Configure Pass-Through Authentication Set the security domain Change the JBoss Data Virtualization security domain to the same name as your application's security domain name in the transport section of the server configuration file. Note For this to work, the security domain must be a JAAS based login module and your client application must obtain its JBoss Data Virtualization connection using a local connection with the PassthroughAuthentication=true connection flag set.

Commands: