mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 146. KafkaRebalanceStatus schema reference Used in: KafkaRebalance Property Property type Description conditions Condition array List of status conditions. observedGeneration integer The generation of the CRD that was last reconciled by the operator. sessionId string The session identifier for requests to Cruise Control pertaining to this KafkaRebalance resource. This is used by the Kafka Rebalance operator to track the status of ongoing rebalancing operations. optimizationResult map A JSON object describing the optimization result.

Commands:
5.8. Highly Available Virtual Machine Reservation A highly available (HA) virtual machine reservation policy enables the Red Hat Virtualization Manager to monitor cluster capacity for highly available virtual machines. The Manager has the capability to flag individual virtual machines for High Availability, meaning that in the event of a host failure, these virtual machines will be rebooted on an alternative host. This policy balances highly available virtual machines across the hosts in a cluster. If any host in the cluster fails, the remaining hosts can support the migrating load of highly available virtual machines without affecting cluster performance. When highly available virtual machine reservation is enabled, the Manager ensures that appropriate capacity exists within a cluster for HA virtual machines to migrate in the event that their existing host fails unexpectedly.

Commands:
Chapter 15. Stopping the Camel Debugger Overview To stop the Camel debugger, click on the menu bar once if the debugging session has ended. Otherwise, click twice: once to terminate the currently running node thread and once to terminate the Camel Context thread (both displayed in the Debug view). + Note Terminating the Camel debugger also terminates the console but does not clear its output. To clear the output, click (Clear Console) on the Console view's menu bar. Closing the Camel debugger After you have finished debugging your project, you may want to close the Debug perspective to make more space for your workbench. To do so, right-click on the toolbar, and then select Close . Related topics Chapter 14, Running the Camel Debugger

Commands:
Chapter 23. Red Hat Enterprise Linux for SAP Solutions Red Hat Enterprise Linux for SAP Solutions provides a consistent foundation for SAP workloads. For a list of features and benefits provided by the RHEL for SAP Solutions subscription for business critical IT landscapes, like SAP environments, see Overview of the Red Hat Enterprise Linux for SAP Solutions subscription . The following resources provide an overview of the changes between RHEL 7 and RHEL 8. For information regarding the RHEL for SAP Solutions life cycle, see Red Hat Enterprise Linux Life Cycle . For details regarding RHEL 8 usage, see RHEL 8 product documentation . For guidance regarding an in-place upgrade from RHEL 7 to RHEL 8, see Upgrading from RHEL 7 to RHEL 8 . In addition to the two main RHEL repositories, BaseOS and AppStream, the RHEL 8 for SAP Solutions subscription includes the SAP Solutions and SAP NetWeaver repositories. Both repositories are required for SAP environments and workloads. Repository name changes between RHEL 7 and RHEL 8 The following table lists the repositories that were renamed between RHEL 7 for SAP HANA / Solutions, and RHEL 8 for SAP Solutions: Original repository name(s) New repository name(s) [a] Changed since Note rhel-sap-hana-for-rhel-7-<server|for-power-le>-rpms rhel-8-for- <arch> -sap-solutions-rpms RHEL 8.0 Also applies to Extended Update Support (EUS) and Update Services for SAP Solutions (E4S) repositories rhel-sap-for-rhel-7-<server|for-power-le>-rpms rhel-8-for- <arch> -sap-netweaver-rpms RHEL 8.0 Also applies to Extended Update Support (EUS) and Update Services for SAP Solutions (E4S) repositories [a] This table uses examples to help identify the full repository ID, where <arch> is the specific architecture.

Commands:
4.317. t1lib 4.317.1. RHSA-2012:0062 - Moderate: t1lib security update Updated t1lib packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate 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 t1lib library allows you to rasterize bitmaps from PostScript Type 1 fonts. Security Fixes CVE-2010-2642 , CVE-2011-0433 Two heap-based buffer overflow flaws were found in the way t1lib processed Adobe Font Metrics (AFM) files. If a specially-crafted font file was opened by an application linked against t1lib, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application. CVE-2011-0764 An invalid pointer dereference flaw was found in t1lib. A specially-crafted font file could, when opened, cause an application linked against t1lib to crash or, potentially, execute arbitrary code with the privileges of the user running the application. CVE-2011-1553 A use-after-free flaw was found in t1lib. A specially-crafted font file could, when opened, cause an application linked against t1lib to crash or, potentially, execute arbitrary code with the privileges of the user running the application. CVE-2011-1554 An off-by-one flaw was found in t1lib. A specially-crafted font file could, when opened, cause an application linked against t1lib to crash or, potentially, execute arbitrary code with the privileges of the user running the application. CVE-2011-1552 An out-of-bounds memory read flaw was found in t1lib. A specially-crafted font file could, when opened, cause an application linked against t1lib to crash. Red Hat would like to thank the Evince development team for reporting CVE-2010-2642 . Upstream acknowledges Jon Larimer of IBM X-Force as the original reporter of CVE-2010-2642 . All users of t1lib are advised to upgrade to these updated packages, which contain backported patches to correct these issues. All applications linked against t1lib must be restarted for this update to take effect.

Commands:
Chapter 25. Networking The keyingtries libreswan option set to 0 is mistakenly interpreted as 1 The default value of keyingtries is 0 which means 'retry forever'. Due to this bug, if a temporary problem occurs during an active negotiation, the connection will not be attempted more than once. To work around this problem, set the keyingtries option to a sufficiently large number. (BZ# 1289498 )

Commands:
2.5. turbostat Turbostat is provided by the kernel-tools package. It reports on processor topology, frequency, idle power-state statistics, temperature, and power usage on Intel (R) 64 processors. Turbostat is useful for identifying servers that are inefficient in terms of power usage or idle time. It also helps to identify the rate of system management interrupts (SMIs) occurring on the system. It can also be used to verify the effects of power management tuning. Turbostat requires root privileges to run. It also requires processor support for the following: invariant time stamp counters APERF model-specific registers MPERF model-specific registers For more details about turbostat output and how to read it, see Section A.10, "turbostat" . For more information about turbostat , see the man page:

Commands:
man turbostat
Chapter 3. Selecting an installed Red Hat build of OpenJDK version for a specific application Some applications require a specific Red Hat build of OpenJDK version to run. If multiple versions of Red Hat build of OpenJDK are installed on the system using the yum package manager or portable bundle, you can select a Red Hat build of OpenJDK version for each application where necessary by setting the value of the JAVA_HOME environment variable or using a wrapper script. Prerequisites Multiple versions of Red Hat build of OpenJDK installed on the machine. Ensure that the application you want to run is installed. Procedure Set the JAVA_HOME environment variable. For example, if Red Hat build of OpenJDK 21 was installed using yum : USD JAVA_HOME=/usr/lib/jvm/java-17-openjdk Note The symbolic link java-17-openjdk is controlled by the alternatives command. Do one of the following: Launch the application using the default, system-wide configuration. Launch the application specifying the JAVA_HOME variable:

Commands:
mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 11.0.9, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.10-0.el8_0.x86_644/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-144.el8.x86_64", arch: "amd64", family: "unix"
JAVA_HOME=/usr/lib/jvm/java-17-openjdk-17.0.0.0.35-4.el8.x86_64/ mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 17, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-17-openjdk-17.0.0.0.35-4.el8.x86_64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-305.19.1.el8_4.x86_64", arch: "amd64", family: "unix"
Key migration terminology While the following migration terms are commonly used in the software industry, these definitions are specific to Red Hat Enterprise Linux (RHEL). Update Sometimes called a software patch, an update is an addition to the current version of the application, operating system, or software that you are running. A software update addresses any issues or bugs to provide a better experience of working with the technology. In RHEL, an update relates to a minor release, for example, updating from RHEL 8.1 to 8.2. Upgrade An upgrade is when you replace the application, operating system, or software that you are currently running with a newer version. Typically, you first back up your data according to instructions from Red Hat. When you upgrade RHEL, you have two options: In-place upgrade: During an in-place upgrade, you replace the earlier version with the new version without removing the earlier version first. The installed applications and utilities, along with the configurations and preferences, are incorporated into the new version. Clean install: A clean install removes all traces of the previously installed operating system, system data, configurations, and applications and installs the latest version of the operating system. A clean install is ideal if you do not need any of the data or applications on your systems or if you are developing a new project that does not rely on prior builds. Operating system conversion A conversion is when you convert your operating system from a different Linux distribution to Red Hat Enterprise Linux. Typically, you first back up your data according to instructions from Red Hat. Migration Typically, a migration indicates a change of platform: software or hardware. Moving from Windows to Linux is a migration. Moving a user from one laptop to another or a company from one server to another is a migration. However, most migrations also involve upgrades, and sometimes the terms are used interchangeably. Migration to RHEL: Conversion of an existing operating system to RHEL Migration across RHEL: Upgrade from one version of RHEL to another

Commands:
Chapter 8. Configuring the OpenTelemetry Collector metrics The following list shows some of these metrics: Collector memory usage CPU utilization Number of active traces and spans processed Dropped spans, logs, or metrics Exporter and receiver statistics The Red Hat build of OpenTelemetry Operator automatically creates a service named <instance_name>-collector-monitoring that exposes the Collector's internal metrics. This service listens on port 8888 by default. You can use these metrics for monitoring the Collector's performance, resource consumption, and other internal behaviors. You can also use a Prometheus instance or another monitoring tool to scrape these metrics from the mentioned <instance_name>-collector-monitoring service. Note When the spec.observability.metrics.enableMetrics field in the OpenTelemetryCollector custom resource (CR) is set to true , the OpenTelemetryCollector CR automatically creates a Prometheus ServiceMonitor or PodMonitor CR to enable Prometheus to scrape your metrics. Prerequisites Monitoring for user-defined projects is enabled in the cluster. Procedure To enable metrics of an OpenTelemetry Collector instance, set the spec.observability.metrics.enableMetrics field to true : apiVersion: opentelemetry.io/v1beta1 kind: OpenTelemetryCollector metadata: name: <name> spec: observability: metrics: enableMetrics: true Verification You can use the Administrator view of the web console to verify successful configuration: Go to Observe Targets . Filter by Source: User . Check that the ServiceMonitors or PodMonitors in the opentelemetry-collector-<instance_name> format have the Up status. Additional resources Enabling monitoring for user-defined projects

Commands:
apiVersion: opentelemetry.io/v1beta1 kind: OpenTelemetryCollector metadata: name: <name> spec: observability: metrics: enableMetrics: true
13.2. Managing Disk Quotas If quotas are implemented, they need some maintenance - mostly in the form of watching to see if the quotas are exceeded and making sure the quotas are accurate. Of course, if users repeatedly exceeds their quotas or consistently reaches their soft limits, a system administrator has a few choices to make depending on what type of users they are and how much disk space impacts their work. The administrator can either help the user determine how to use less disk space or increase the user's disk quota if needed. 13.2.1. Enabling and Disabling It is possible to disable quotas without setting them to be 0. To turn all user and group quotas off, use the following command: If neither the -u or -g options are specified, only the user quotas are disabled. If only -g is specified, only group quotas are disabled. To enable quotas again, use the quotaon command with the same options. For example, to enable user and group quotas for all file systems, use the following command: To enable quotas for a specific file system, such as /home , use the following command: If neither the -u or -g options are specified, only the user quotas are enabled. If only -g is specified, only group quotas are enabled.

Commands:
quotaoff -vaug
quotaon -vaug
quotaon -vug /home
2.8. General Configuration Considerations You can configure a Red Hat Cluster in a variety of ways to suit your needs. Take into account the following considerations when you plan, configure, and implement your Red Hat Cluster. No-single-point-of-failure hardware configuration Clusters can include a dual-controller RAID array, multiple bonded network channels, multiple paths between cluster members and storage, and redundant un-interruptible power supply (UPS) systems to ensure that no single failure results in application down time or loss of data. Alternatively, a low-cost cluster can be set up to provide less availability than a no-single-point-of-failure cluster. For example, you can set up a cluster with a single-controller RAID array and only a single Ethernet channel. Certain low-cost alternatives, such as host RAID controllers, software RAID without cluster support, and multi-initiator parallel SCSI configurations are not compatible or appropriate for use as shared cluster storage. Data integrity assurance To ensure data integrity, only one node can run a cluster service and access cluster-service data at a time. The use of power switches in the cluster hardware configuration enables a node to power-cycle another node before restarting that node's cluster services during a failover process. This prevents two nodes from simultaneously accessing the same data and corrupting it. It is strongly recommended that fence devices (hardware or software solutions that remotely power, shutdown, and reboot cluster nodes) are used to guarantee data integrity under all failure conditions. Watchdog timers provide an alternative way to to ensure correct operation of cluster service failover. Ethernet channel bonding Cluster quorum and node health is determined by communication of messages among cluster nodes via Ethernet. In addition, cluster nodes use Ethernet for a variety of other critical cluster functions (for example, fencing). With Ethernet channel bonding, multiple Ethernet interfaces are configured to behave as one, reducing the risk of a single-point-of-failure in the typical switched Ethernet connection among cluster nodes and other cluster hardware.

Commands:
5.5. J2EE Usage Models J2EE provides three ways to manage transactions for beans: Client-Controlled The client of a bean begins and ends a transaction explicitly. Bean-Managed The bean itself begins and ends a transaction explicitly. Container-Managed The application server container begins and ends a transaction automatically. In any of these cases, transactions may be either local or XA transactions, depending on how the code and descriptors are written. Some kinds of beans (stateful session beans and entity beans) are not required by the spec to support non-transactional sources, although the spec does allow an application server to optionally support this with the caution that this is not portable or predictable. Generally speaking, to support most typical EJB activities in a portable fashion requires some kind of transaction support.

Commands:
11.14. Deleting Volumes Important Volumes must be unmounted and stopped before you can delete them. Ensure that you also remove entries relating to this volume from the /etc/fstab file after the volume has been deleted. To delete a volume, use the following command: For example, to delete test-volume:

Commands:
gluster volume delete VOLNAME
gluster volume delete test-volume Deleting volume will erase all information about the volume. Do you want to continue? (y/n) y Deleting volume test-volume has been successful
7.5. Viruses and Spoofed IP Addresses More elaborate rules can be created that control access to specific subnets, or even specific nodes, within a LAN. You can also restrict certain dubious services such as trojans, worms, and other client/server viruses from contacting their server. For example, there are some trojans that scan networks for services on ports from 31337 to 31340 (called the elite ports in cracking terminology). Since there are no legitimate services that communicate via these non-standard ports, blocking it can effectively diminish the chances that potentially infected nodes on your network independently communicate with their remote master servers. You can also block outside connections that attempt to spoof private IP address ranges to infiltrate your LAN. For example, if your LAN uses the 192.168.1.0/24 range, a rule can set the Internet facing network device (for example, eth0) to drop any packets to that device with an address in your LAN IP range. Because it is recommended to reject forwarded packets as a default policy, any other spoofed IP address to the external-facing device (eth0) is rejected automatically. Note There is a distinction between the DROP and REJECT targets when dealing with appended rules. The REJECT target denies access and returns a connection refused error to users who attempt to connect to the service. The DROP target, as the name implies, drops the packet without any warning. Administrators can use their own discretion when using these targets. However, to avoid user confusion and attempts to continue connecting, the REJECT target is recommended.

Commands:
iptables -A OUTPUT -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP
Chapter 8. Optional - Enable SAP HA interface for Management of Cluster-controlled ASCS/ERS instances using SAP Management Tools When a system admin controls a SAP instance that is running inside the Pacemaker cluster, either manually or using tools such as SAP Management Console (MC/MMC), the change needs to be done through the HA interface that's provided by the HA cluster software. SAP Start Service sapstartsrv controls the SAP instances and needs to be configured to communicate with the pacemaker cluster software through the HA interface. Please follow the kbase article to configure the HAlib : How to enable the SAP HA Interface for SAP ABAP application server instances managed by the RHEL HA Add-On? .

Commands:
2.30. RHEA-2011:0612 - new package: python-kerberos A new python-kerberos package is now available for Red Hat Enterprise Linux 6. This new python-kerberos package contains a high-level wrapper for Kerberos (GSSAPI) operations. This limited set provides all needed functions for client-server Kerberos authentication. (BZ# 601111 ) Users who require Kerberos authentication for or from Python programs are advised to install this new python-kerberos package.

Commands:
7.205. subversion 7.205.1. RHBA-2015:1388 - subversion bug fix update Updated subversion packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Subversion (SVN) is a concurrent version control system which enables one or more users to collaborate in developing and maintaining a hierarchy of files and directories while keeping a history of all changes. Bug Fixes BZ# 922718 Previously, properties were lost when merging new files from a foreign repository in Subversion. The underlying source code has been patched to fix this bug, and newly added files retain their properties after a foreign repository merge, as expected. BZ# 1039085 Prior to this update, enabling memcached caching with a Subversion server on Red Hat Enterprise Linux led to excessive socket use, which had a detrimental performance impact. This bug has been fixed, and server performance no longer suffers in this configuration. Users of subversion are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 13. Adding custom SSL/TLS certificates when Red Hat Quay is deployed on Kubernetes When deployed on Kubernetes, Red Hat Quay mounts in a secret as a volume to store config assets. Currently, this breaks the upload certificate function of the superuser panel. As a temporary workaround, base64 encoded certificates can be added to the secret after Red Hat Quay has been deployed. Use the following procedure to add custom SSL/TLS certificates when Red Hat Quay is deployed on Kubernetes. Prerequisites Red Hat Quay has been deployed. You have a custom ca.crt file. Procedure Base64 encode the contents of an SSL/TLS certificate by entering the following command: USD cat ca.crt | base64 -w 0 Example output ...c1psWGpqeGlPQmNEWkJPMjJ5d0pDemVnR2QNCnRsbW9JdEF4YnFSdVd3PT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo= Enter the following kubectl command to edit the quay-enterprise-config-secret file: USD kubectl --namespace quay-enterprise edit secret/quay-enterprise-config-secret Add an entry for the certificate and paste the full base64 encoded stringer under the entry. For example: custom-cert.crt: c1psWGpqeGlPQmNEWkJPMjJ5d0pDemVnR2QNCnRsbW9JdEF4YnFSdVd3PT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo= Use the kubectl delete command to remove all Red Hat Quay pods. For example: USD kubectl delete pod quay-operator.v3.7.1-6f9d859bd-p5ftc quayregistry-clair-postgres-7487f5bd86-xnxpr quayregistry-quay-app-upgrade-xq2v6 quayregistry-quay-database-859d5445ff-cqthr quayregistry-quay-redis-84f888776f-hhgms Afterwards, the Red Hat Quay deployment automatically schedules replace pods with the new certificate data.

Commands:
cat ca.crt | base64 -w 0
...c1psWGpqeGlPQmNEWkJPMjJ5d0pDemVnR2QNCnRsbW9JdEF4YnFSdVd3PT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
kubectl --namespace quay-enterprise edit secret/quay-enterprise-config-secret
custom-cert.crt: c1psWGpqeGlPQmNEWkJPMjJ5d0pDemVnR2QNCnRsbW9JdEF4YnFSdVd3PT0KLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo=
kubectl delete pod quay-operator.v3.7.1-6f9d859bd-p5ftc quayregistry-clair-postgres-7487f5bd86-xnxpr quayregistry-quay-app-upgrade-xq2v6 quayregistry-quay-database-859d5445ff-cqthr quayregistry-quay-redis-84f888776f-hhgms