mtpti5iD/redhat-docs_dataset huggingface dataset:
7.307. db4 7.307.1. RHBA-2013:1258 - db4 bug fix update Updated db4 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Berkeley Database (Berkeley DB) is a programmatic toolkit that provides embedded database support for both traditional and client/server applications. The Berkeley DB includes B+tree, Extended Linear Hashing, Fixed and Variable-length record access methods, transactions, locking, logging, shared memory caching, and database recovery. The Berkeley DB supports C, C++, Java, and Perl APIs. It is used by many applications, including Python and Perl, so this should be installed on all systems. Bug Fix BZ# 1005826 Due to an incorrect order of the mutex initialization calls, the rpm utility became unresponsive under certain circumstances, until it was terminated. With this update, the order of mutex initialization calls has been revised. As a result, the rpm utility no longer becomes unresponsive. Users of db4 are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 7. Premigration checklists Before you migrate your application workloads with the Migration Toolkit for Containers (MTC), review the following checklists. 7.1. Cluster health checklist ❏ The clusters meet the minimum hardware requirements for the specific platform and installation method, for example, on bare metal . ❏ All MTC prerequisites are met. ❏ All nodes have an active OpenShift Container Platform subscription. ❏ You have verified node health . ❏ The identity provider is working. ❏ The migration network has a minimum throughput of 10 Gbps. ❏ The clusters have sufficient resources for migration. Note Clusters require additional memory, CPUs, and storage in order to run a migration on top of normal workloads. Actual resource requirements depend on the number of Kubernetes resources being migrated in a single migration plan. You must test migrations in a non-production environment in order to estimate the resource requirements. ❏ The etcd disk performance of the clusters has been checked with fio . 7.2. Source cluster checklist ❏ You have checked for persistent volumes (PVs) with abnormal configurations stuck in a Terminating state by running the following command: USD oc get pv ❏ You have checked for pods whose status is other than Running or Completed by running the following command: USD oc get pods --all-namespaces | egrep -v 'Running | Completed' ❏ You have checked for pods with a high restart count by running the following command: USD oc get pods --all-namespaces --field-selector=status.phase=Running \ -o json | jq '.items[]|select(any( .status.containerStatuses[]; \ .restartCount > 3))|.metadata.name' Even if the pods are in a Running state, a high restart count might indicate underlying problems. ❏ The cluster certificates are valid for the duration of the migration process. ❏ You have checked for pending certificate-signing requests by running the following command: USD oc get csr -A | grep pending -i ❏ The registry uses a recommended storage type . ❏ You can read and write images to the registry. ❏ The etcd cluster is healthy. ❏ The average API server response time on the source cluster is less than 50 ms. 7.3. Target cluster checklist ❏ The cluster has the correct network configuration and permissions to access external services, for example, databases, source code repositories, container image registries, and CI/CD tools. ❏ External applications and services that use services provided by the cluster have the correct network configuration and permissions to access the cluster. ❏ Internal container image dependencies are met. ❏ The target cluster and the replication repository have sufficient storage space.

Commands:
oc get pv
oc get pods --all-namespaces | egrep -v 'Running | Completed'
oc get pods --all-namespaces --field-selector=status.phase=Running -o json | jq '.items[]|select(any( .status.containerStatuses[]; .restartCount > 3))|.metadata.name'
oc get csr -A | grep pending -i
Application development Red Hat OpenShift Service on AWS 4 Configuring Red Hat OpenShift Service on AWS for your applications Red Hat OpenShift Documentation Team

Commands:
oc create secret tls <name>-tls --cert=fullchain.pem --key=privkey.pem -n <my_project>
apiVersion: managed.openshift.io/v1alpha1 kind: CustomDomain metadata: name: <company_name> spec: domain: apps.<company_name>.io 1 scope: External loadBalancerType: Classic 2 certificate: name: <name>-tls 3 namespace: <my_project> routeSelector: 4 matchLabels: route: acme namespaceSelector: 5 matchLabels: type: sharded
oc apply -f <company_name>-custom-domain.yaml
oc get customdomains
NAME ENDPOINT DOMAIN STATUS <company_name> xxrywp.<company_name>.cluster-01.opln.s1.openshiftapps.com *.apps.<company_name>.io Ready
*.apps.<company_name>.io -> xxrywp.<company_name>.cluster-01.opln.s1.openshiftapps.com
oc new-app --docker-image=docker.io/openshift/hello-openshift -n my-project
oc create route <route_name> --service=hello-openshift hello-openshift-tls --hostname hello-openshift-tls-my-project.apps.<company_name>.io -n my-project
oc get route -n my-project
curl https://hello-openshift-tls-my-project.apps.<company_name>.io Hello OpenShift!
oc create secret tls <secret-new> --cert=fullchain.pem --key=privkey.pem -n <my_project>
oc patch customdomain <company_name> --type='merge' -p '{"spec":{"certificate":{"name":"<secret-new>"}}}'
oc delete secret <secret-old> -n <my_project>
3.6. Using stunnel The stunnel program is an encryption wrapper between a client and a server. It listens on the port specified in its configuration file, encrypts the communication with the client, and forwards the data to the original daemon listening on its usual port. This way, you can secure any service that itself does not support any type of encryption, or improve the security of a service that uses a type of encryption that you want to avoid for security reasons, such as SSL versions 2 and 3, affected by the POODLE SSL vulnerability (CVE-2014-3566). See Resolution for POODLE SSLv3.0 vulnerability (CVE-2014-3566) for components that do not allow SSLv3 to be disabled via configuration settings . OpenLDAP older than 2.4.39 (before Red Hat Enterprise Linux 6.6) and CUPS are examples of components that do not provide a way to disable SSL in their own configuration. 3.6.1. Installing stunnel Install the stunnel package by running the following command as root :

Commands:
~]# yum install stunnel
Providing feedback on Red Hat Ceph Storage documentation We appreciate your input on our documentation. Please let us know how we could make it better. To do so, create a Bugzilla ticket: Go to the Bugzilla website. In the Component drop-down, select Documentation . In the Sub-Component drop-down, select the appropriate sub-component. Select the appropriate version of the document. Fill in the Summary and Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation. Optional: Add an attachment, if any. Click Submit Bug .

Commands:
Chapter 9. Logging Logging is important in troubleshooting and debugging. By default logging is turned off. To enable logging, you must set a logging level and provide a delegate function to receive the log messages. 9.1. Setting the log output level The library emits log traces at different levels: Error Warning Information Verbose The lowest log level, Error , traces only error events and produces the fewest log messages. A higher log level includes all the log levels below it and generates a larger volume of log messages. 9.2. Enabling protocol logging The Log level Frame is handled differently. Setting trace level Frame enables tracing outputs for AMQP protocol headers and frames. Tracing at one of the other log levels must be logically ORed with Frame to get normal tracing output and AMQP frame tracing at the same time. For example The following code writes AMQP frames to the console. Example: Logging delegate Trace.TraceLevel = TraceLevel.Frame; Trace.TraceListener = (f, a) => Console.WriteLine( DateTime.Now.ToString("[hh:mm:ss.fff]") + " " + string.Format(f, a));

Commands:
// Enable Error logs only. Trace.TraceLevel = TraceLevel.Error
// Enable Verbose logs. This includes logs at all log levels. Trace.TraceLevel = TraceLevel.Verbose
// Enable just AMQP frame tracing Trace.TraceLevel = TraceLevel.Frame;
// Enable AMQP Frame logs, and Warning and Error logs Trace.TraceLevel = TraceLevel.Frame | TraceLevel.Warning;
Trace.TraceLevel = TraceLevel.Frame; Trace.TraceListener = (f, a) => Console.WriteLine( DateTime.Now.ToString("[hh:mm:ss.fff]") + " " + string.Format(f, a));
Chapter 22. Samba Samba uses the SMB protocol to share files and printers across a network connection. Operating systems that support this protocol include Microsoft Windows, OS/2, and Linux. The Red Hat Enterprise Linux 4 kernel contains Access Control List (ACL) support for ext3 file systems. If the Samba server shares an ext3 file system with ACLs enabled for it, and the kernel on the client system contains support for reading ACLs from ext3 file systems, the client automatically recognizes and uses the ACLs. Refer to Chapter 14, Access Control Lists for more information on ACLs. 22.1. Why Use Samba? Samba is useful if you have a network of both Windows and Linux machines. Samba allows files and printers to be shared by all the systems in a network. To share files between Linux machines only, use NFS as discussed in Chapter 21, Network File System (NFS) . To share printers between Linux machines only, you do not need to use Samba; refer to Chapter 33, Printer Configuration .

Commands:
5.3. Supported Installation Targets An installation target is a storage device that will store Red Hat Enterprise Linux and boot the system. Red Hat Enterprise Linux supports the following installation targets for AMD, Intel, and ARM systems: Storage connected by a standard internal interface, such as SCSI, SATA, or SAS BIOS/firmware RAID devices NVDIMM devices in sector mode on the Intel64 and AMD64 architectures, supported by the nd_pmem driver. Fibre Channel Host Bus Adapters and multipath devices. Some can require vendor-provided drivers. Xen block devices on Intel processors in Xen virtual machines. VirtIO block devices on Intel processors in KVM virtual machines. Red Hat does not support installation to USB drives or SD memory cards. For information about the support for third-party virtualization technologies, see the Red Hat Hardware Compatibility List , available online at https://hardware.redhat.com .

Commands:
4.6. Configuring Fingerprints Using authconfig 4.6.1. Using Fingerprint Authentication in the UI When there is appropriate hardware available, the Enable fingerprint reader support option allows fingerprint scans to be used to authenticate local users in addition to other credentials. Figure 4.4. Fingerprint Options 4.6.2. Configuring Fingerprint Authentication in the Command Line There is one option to enable support for fingerprint readers. This option can be used alone or in conjunction with other authconfig settings, like LDAP user stores.

Commands:
authconfig --enablefingerprint --update
5.40. cryptsetup-luks 5.40.1. RHBA-2012:0886 - cryptsetup-luks bug fix update Updated cryptsetup-luks packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The cryptsetup-luks packages provide a utility which allows users to set up encrypted devices with the Device Mapper and the dm-crypt target. Bug Fix BZ# 746648 For some configurations, the cryptsetup utility incorrectly translated major:minor device pairs to device names in the /dev/ directory (for example, on HP Smart Array devices). With this update, the underlying source code has been modified to address this issue, and the cryptsetup utility now works as expected. (BZ# 755478 ) * If a device argument for the "cryptsetup status" command included a /dev/mapper/ prefix, the prefix was duplicated in the command's output. The output was fixed and no longer includes duplicated strings. All users of cryptsetup-luks are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 6. References 6.1. Red Hat Installing RHEL 9 for SAP Solutions Configuring and managing high availability clusters on RHEL 9 Support Policies for RHEL High Availability Clusters Support Policies for RHEL High Availability Clusters - Fencing/STONITH Support Policies for RHEL High Availability Clusters - Management of SAP HANA in a Cluster Red Hat HA Solutions for SAP HANA, S/4HANA and NetWeaver based SAP Applications 6.2. SAP SAP HANA Server Installation and Update Guide SAP HANA System Replication Implementing a HA/DR Provider SAP Note 2057595 - FAQ: SAP HANA High Availability SAP Note 2063657 - SAP HANA System Replication Takeover Decision Guideline SAP Note 3007062 - FAQ: SAP HANA & Third Party Cluster Solutions 6.3. Other Be Prepared for Using Pacemaker Cluster for SAP HANA - Part 1: Basics Be Prepared for Using Pacemaker Cluster for SAP HANA - Part 2: Failure of Both Nodes

Commands:
Chapter 3. Installing web console add-ons and creating custom pages Depending on how you want to use your Red Hat Enterprise Linux system, you can add additional available applications to the web console or create custom pages based on your use case. 3.1. Add-ons for the RHEL web console While the cockpit package is a part of Red Hat Enterprise Linux by default, you can install add-on applications on demand by using the following command: In the command, replace <add-on> by a package name from the list of available add-on applications for the RHEL web console. Feature name Package name Usage Composer cockpit-composer Building custom OS images Machines cockpit-machines Managing libvirt virtual machines PackageKit cockpit-packagekit Software updates and application installation (usually installed by default) PCP cockpit-pcp Persistent and more fine-grained performance data (installed on demand from the UI) Podman cockpit-podman Managing containers and managing container images (available from RHEL 8.1) Session Recording cockpit-session-recording Recording and managing user sessions Storage cockpit-storaged Managing storage through udisks 3.2. Creating new pages in the web console If you want to add customized functions to your Red Hat Enterprise Linux web console, you must add the package directory that contains the HTML and JavaScript files for the page that runs the required function. For detailed information about adding custom pages, see Creating Plugins for the Cockpit User Interface on the Cockpit Project website. Additional resources Cockpit Packages section in the Cockpit Project Developer Guide 3.3. Overriding the manifest settings in the web console You can modify the menu of the web console for a particular user and all users of the system. In the cockpit project, a package name is a directory name. A package contains the manifest.json file along with other files. Default settings are present in the manifest.json file. You can override the default cockpit menu settings by creating a <package-name> .override.json file at a specific location for the specified user. Prerequisites You have installed the RHEL 8 web console. For instructions, see Installing and enabling the web console . Procedure Override manifest settings in the <systemd> .override.json file in a text editor of your choice, for example: To edit for all users, enter: To edit for a single user, enter: Edit the required file with the following details: { "menu": { "services": null, "logs": { "order": -1 } } } The null value hides the services tab The -1 value moves the logs tab to the first place. Restart the cockpit service: Additional resources cockpit(1) man page on your system Manifest overrides

Commands:
yum install <add-on>
vi /etc/cockpit/ <systemd> .override.json
vi ~/.config/cockpit/ <systemd> .override.json
{ "menu": { "services": null, "logs": { "order": -1 } } }
systemctl restart cockpit.service
Chapter 1. Keyboard Configuration This chapter describes how to change the keyboard layout, as well as how to add the Keyboard Indicator applet to the panel. It also covers the option to enforce a typing break, and explains both advantages and disadvantages of doing so. 1.1. Changing the Keyboard Layout The installation program has allowed you to configure a keyboard layout for your system. However, the default settings may not always suit your current needs. To configure a different keyboard layout after the installation, use the Keyboard Preferences tool. To open Keyboard Layout Preferences , select System Preferences Keyboard from the panel, and click the Layouts tab. Figure 1.1. Keyboard Layout Preferences You will be presented with a list of available layouts. To add a new one, click the Add button below the list, and you will be prompted to choose which layout you want to add. Figure 1.2. Choosing a layout Currently, there are two ways how to choose the keyboard layout: you can either find it by the country it is associated with (the By country tab), or you can select it by language (the By language tab). In either case, first select the desired country or language from the Country or Language pulldown menu, then specify the variant from the Variants menu. The preview of the layout changes immediately. To confirm the selection, click Add . Figure 1.3. Selecting the default layout The layout should appear in the list. To make it the default, select the radio button to its name. The changes take effect immediately. Note that there is a text-entry field at the bottom of the window where you can safely test your settings. Once you are satisfied, click Close to close the window. Figure 1.4. Testing the layout Note By default, changing the keyboard layout affects the active window only. This means that if you change the layout and switch to another window, this window will use the old one, which might be confusing. To turn this behavior off, clear the Separate layout for each window check box. Doing this has its drawbacks though, as you will no longer be able to choose the default layout by selecting the radio button as shown in Figure 1.3, "Selecting the default layout" . To make the layout the default, drag it to the beginning of the list.

Commands:
probe::nfs.proc.rename_done Name probe::nfs.proc.rename_done - NFS client response to a rename RPC task Synopsis nfs.proc.rename_done Values timestamp V4 timestamp, which is used for lease renewal status result of last operation server_ip IP address of server prot transfer protocol version NFS version old_fh file handle of old parent dir new_fh file handle of new parent dir Description Fires when a reply to a rename RPC task is received or some rename error occurs (timeout or socket shutdown).

Commands:
Chapter 28. Hardware Enablement The lsslot -cpci command now correctly reports PCI slot types Prior to this update, the lsslot -cpci command reported PCI slot types as <literal>Unknown slot type</literal>. With this update, the bug has been fixed, and lsslot utility reports PCI slot types correctly. (BZ#1592429) The drmgr -C command now loads the rpadlpar_io kernel module Previously, the drmgr -C command did not select hotplug types. As a consequence, the rpadlpar_io kernel module was loaded only when one of the following hotplug types was explicitly selected: pci , phb or slot . With this update, the underlying source code has been fixed, and the command drmgr -C now loads rpadlpar_io . (BZ#1540067) Diagnostic utilities now display CPU frequency values correctly Due to a delay in the CPU cycle counter, diagnostic utilites, such as lscpu , in some cases reported an incorrect CPU frequency value. With this update, the affected utilities display correct values and report an error if the accurate value currently cannot be detected. (BZ#1596121) The ppc64_cpu utility no longer fails when reading CPU frequency Previously, the ppc64_cpu utility failed when reading CPU frequency. With this update, a thread is created for each of the CPUs if the number of CPUs in the system is less than CPU_SETSIZE, or only CPU_SETSIZE threads are created. As a result, the described problem no longer occurs, and ppc64_cpu no longer fails. (BZ#1628907)

Commands:
5.330. tcpdump 5.330.1. RHBA-2012:0414 - tcpdump bug fix update An updated tcpdump package that fixes one bug is now available for Red Hat Enterprise Linux 6. The tcpdump tool is a command line utility for monitoring network traffic. Bug Fix BZ# 684005 Previously, the "start-time" command-line argument of the tcpslice utility was parsed incorrectly. As a consequence, the utility produced error messages every time the command-line argument was used. With this update, the "start-time" command-line argument is parsed correctly, and an error message is displayed only if "start-time" is defined in an incorrect format. All users of tcpdump are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 2. Differences from upstream OpenJDK 11 Red Hat build of OpenJDK in Red Hat Enterprise Linux (RHEL) contains a number of structural changes from the upstream distribution of OpenJDK. The Microsoft Windows version of Red Hat build of OpenJDK attempts to follow RHEL updates as closely as possible. The following list details the most notable Red Hat build of OpenJDK 11 changes: FIPS support. Red Hat build of OpenJDK 11 automatically detects whether RHEL is in FIPS mode and automatically configures Red Hat build of OpenJDK 11 to operate in that mode. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows. Cryptographic policy support. Red Hat build of OpenJDK 11 obtains the list of enabled cryptographic algorithms and key size constraints from RHEL. These configuration components are used by the Transport Layer Security (TLS) encryption protocol, the certificate path validation, and any signed JARs. You can set different security profiles to balance safety and compatibility. This change does not apply to Red Hat build of OpenJDK builds for Microsoft Windows. Red Hat build of OpenJDK on RHEL dynamically links against native libraries such as zlib for archive format support and libjpeg-turbo , libpng , and giflib for image support. RHEL also dynamically links against Harfbuzz and Freetype for font rendering and management. The src.zip file includes the source for all the JAR libraries shipped with Red Hat build of OpenJDK. Red Hat build of OpenJDK on RHEL uses system-wide timezone data files as a source for timezone information. Red Hat build of OpenJDK on RHEL uses system-wide CA certificates. Red Hat build of OpenJDK on Microsoft Windows includes the latest available timezone data from RHEL. Red Hat build of OpenJDK on Microsoft Windows uses the latest available CA certificate from RHEL. Additional resources For more information about detecting if a system is in FIPS mode, see the Improve system FIPS detection example on the Red Hat RHEL Planning Jira. For more information about cryptographic policies, see Using system-wide cryptographic policies .

Commands:
C.3.2. Saving Passphrases If you use a kickstart file during installation, you can automatically save the passphrases used during installation to an encrypted file (an escrow packet ) on the local file system. To use this feature, you must have an X.509 certificate available at a location that anaconda can access. To specify the URL of this certificate, add the --escrowcert parameter to any of the autopart , logvol , part or raid commands. During installation, the encryption keys for the specified devices are saved in files in /root , encrypted with the certificate. You can save escrow packets during installation only with the use of a kickstart file - refer to Chapter 32, Kickstart Installations for more detail. You cannot save an escrow packet during an interactive installation, although you can create one on an installed system with the volume_key tool. The volume_key tool also allows you to use the information stored in an escrow packet to restore access to an encrypted volume. Refer to the volume_key manpage for more information.

Commands: