mtpti5iD/redhat-docs_dataset huggingface dataset:
5.252. procps 5.252.1. RHBA-2012:1463 - procps bug fix update Updated procps packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The procps packages provide a set of system utilities to provide system information using the /proc file system. The procps package includes the free, pgrep, pkill, pmap, ps, pwdx, skill, slabtop, snice, sysctl, tload, top, uptime, vmstat, w, and watch utilities. Bug Fixes BZ# 851664 Prior to this update, the 'si' and 'so' values were always zero for "m" or "M" units. This was caused by an arithmetic precision loss in the expressions used for the calculations. This update modifies the expressions to avoid precision losses. BZ# 875077 Prior to this update, the vmstat tool could be terminated unexpectedly raising the SIGFPE exception when the total sum of 'us', 'sy', 'id', 'wa' and 'st' values returned by the kernel was zero. This situation could only appear on certain specific platforms. this update modifies the internal evaluation so that the vmstat tool is more robust and does no longer terminate. All users of procps are advised to upgrade to these updated packages, which fix these bugs. 5.252.2. RHBA-2012:0461 - procps bug fix update An updated procps package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The procps package contains a set of system utilities that provide system information using the /proc file system. The procps package includes the free, pgrep, pkill, pmap, ps, pwdx, skill, slabtop, snice, sysctl, tload, top, uptime, vmstat, w, and watch utilities. Bug Fixes BZ# 746997 Prior to this update, it was not possible to instruct the "top" utility by using command-line options to sort processes according to the memory consumption. This was possible only in interactive mode (by using the "Shift+M" key combination). This update introduces a new command-line option, "-a", that instructs the "top" utility to sort processes according to the memory consumption in batch mode. Note that in Red Hat Enterprise Linux 5, this functionality is provided by the "-m" option whereas the same option is used for another feature in Red Hat Enterprise Linux 6. BZ# 751475 Previously, the CPULOOP variable effected only the statistical lines representing the particular CPU cores. With this update, the "top" command additionally applies the CPULOOP variable on the CPU summary line (that represents all the CPU cores). BZ# 766792 Prior to this update, no development package was generated for procps. With this update, a separate procps-devel package containing a set of procps development headers is available. All users of procps are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 12. Viewing and managing your OSGI environment For Apache Karaf standalone distributions, you can view and manage the Red Hat Fuse OSGi environment. You can view and manage container bundles, features, and configurations, as well as Java packages and OSGi services. The OSGi tab contains a series of subtabs with options for each container component: Bundles List of installed bundles. You can install and uninstall bundles, start and stop bundles, and edit bundle properties. You can also filter the list and toggle between list and grid view. Features List of available features. You can install and uninstall features or feature repositories, and drill down to view feature details. Packages List of installed Java packages. You can view package versions and associated bundles. Services List of running services. You can view service IDs, associated bundles and object classes. Declarative Services List of declarative OSGi services. You can view the service state and drill down to view service details. You can also activate and deactivate services. Server Detailed information about the local or remote host in read-only mode. Framework Configuration options for the container OSGi framework. You can set the framework start level and the initial bundle start level. Configuration List of configuration objects. You can view the state of each object and drill down to view or edit object details. You can also create a new configuration object.

Commands:
Chapter 45. Storage LVM RAID-level takeover is now available RAID-level takeover, the ability to switch between RAID types, is now available as a Technology Preview. With RAID-level takeover, the user can decide based on their changing hardware characteristics what type of RAID configuration best suits their needs and make the change without having to deactivate the logical volume. For example, if a striped logical volume is created, it can be later converted to a RAID4 logical volume if an additional device is available. Starting with Red Hat Enterprise Linux 7.3, the following conversions are available as a Technology Preview: striped <-> RAID4 linear <-> RAID1 mirror <-> RAID1 (mirror is a legacy type, but still supported) (BZ# 1191630 ) Multi-queue I/O scheduling for SCSI Red Hat Enterprise Linux 7 includes a new multiple-queue I/O scheduling mechanism for block devices known as blk-mq. The scsi-mq package allows the Small Computer System Interface (SCSI) subsystem to make use of this new queuing mechanism. This functionality is provided as a Technology Preview and is not enabled by default. To enable it, add scsi_mod.use_blk_mq=Y to the kernel command line. (BZ#1109348) Targetd plug-in from the libStorageMgmt API Since Red Hat Enterprise Linux 7.1, storage array management with libStorageMgmt, a storage array independent API, has been fully supported. The provided API is stable, consistent, and allows developers to programmatically manage different storage arrays and utilize the hardware-accelerated features provided. System administrators can also use libStorageMgmt to manually configure storage and to automate storage management tasks with the included command-line interface. The Targetd plug-in is not fully supported and remains a Technology Preview. (BZ#1119909) Support for Data Integrity Field/Data Integrity Extension (DIF/DIX) DIF/DIX is a new addition to the SCSI Standard. It is fully supported in Red Hat Enterprise Linux 7.3 for the HBAs and storage arrays specified in the Features chapter, but it remains in Technology Preview for all other HBAs and storage arrays. DIF/DIX increases the size of the commonly used 512 byte disk block from 512 to 520 bytes, adding the Data Integrity Field (DIF). The DIF stores a checksum value for the data block that is calculated by the Host Bus Adapter (HBA) when a write occurs. The storage device then confirms the checksum on receipt, and stores both the data and the checksum. Conversely, when a read occurs, the checksum can be verified by the storage device, and by the receiving HBA. (BZ#1072107)

Commands:
Chapter 76. KafkaClientAuthenticationScramSha512 schema reference Used in: KafkaBridgeSpec , KafkaConnectSpec , KafkaMirrorMaker2ClusterSpec , KafkaMirrorMakerConsumerSpec , KafkaMirrorMakerProducerSpec Full list of KafkaClientAuthenticationScramSha512 schema properties To configure SASL-based SCRAM-SHA-512 authentication, set the type property to scram-sha-512 . The SCRAM-SHA-512 authentication mechanism requires a username and password. 76.1. username Specify the username in the username property. 76.2. passwordSecret In the passwordSecret property, specify a link to a Secret containing the password. You can use the secrets created by the User Operator. If required, you can create a text file that contains the password, in cleartext, to use for authentication: echo -n PASSWORD > MY-PASSWORD .txt You can then create a Secret from the text file, setting your own field name (key) for the password: oc create secret generic MY-CONNECT-SECRET-NAME --from-file= MY-PASSWORD-FIELD-NAME =./ MY-PASSWORD .txt Example Secret for SCRAM-SHA-512 client authentication for Kafka Connect apiVersion: v1 kind: Secret metadata: name: my-connect-secret-name type: Opaque data: my-connect-password-field: LFTIyFRFlMmU2N2Tm The secretName property contains the name of the Secret , and the password property contains the name of the key under which the password is stored inside the Secret . Important Do not specify the actual password in the password property. Example SASL-based SCRAM-SHA-512 client authentication configuration for Kafka Connect authentication: type: scram-sha-512 username: my-connect-username passwordSecret: secretName: my-connect-secret-name password: my-connect-password-field 76.3. KafkaClientAuthenticationScramSha512 schema properties Property Property type Description passwordSecret PasswordSecretSource Reference to the Secret which holds the password. type string Must be scram-sha-512 . username string Username used for the authentication.

Commands:
echo -n PASSWORD > MY-PASSWORD .txt
create secret generic MY-CONNECT-SECRET-NAME --from-file= MY-PASSWORD-FIELD-NAME =./ MY-PASSWORD .txt
apiVersion: v1 kind: Secret metadata: name: my-connect-secret-name type: Opaque data: my-connect-password-field: LFTIyFRFlMmU2N2Tm
authentication: type: scram-sha-512 username: my-connect-username passwordSecret: secretName: my-connect-secret-name password: my-connect-password-field
Preface This guide provides the information to upgrade Red Hat 3scale API Management to the latest version via the 3scale operator. You will find details required to upgrade your 3scale installation from 2.14 to 2.15, as well as the steps to upgrade APIcast in an operator-based deployment. To upgrade your 3scale On-premises deployment, refer to the following guide: 3scale operator-based upgrade guide To upgrade APIcast in an operator-based deployment, refer to the following guide: APIcast upgrade guide

Commands:
Chapter 24. Installing and running the IdM Healthcheck tool Learn more about the IdM Healthcheck tool and how to install and run it. 24.1. Healthcheck in IdM The Healthcheck tool in Identity Management (IdM) helps find issues that might impact the health of your IdM environment. Note The Healthcheck tool is a command line tool that can be used without Kerberos authentication. Modules are Independent Healthcheck consists of independent modules which test for: Replication issues Certificate validity Certificate Authority infrastructure issues IdM and Active Directory trust issues Correct file permissions and ownership settings Two output formats Healthcheck generates the following outputs, which you can set using the output-type option: json : Machine-readable output in JSON format (default) human : Human-readable output You can specify a different file destination with the --output-file option. Results Each Healthcheck module returns one of the following results: SUCCESS configured as expected WARNING not an error, but worth keeping an eye on or evaluating ERROR not configured as expected CRITICAL not configured as expected, with a high possibility for impact 24.2. Installing IdM Healthcheck You can install the IdM Healthcheck tool. Procedure Install the ipa-healthcheck package: Verification Use the --failures-only option to have ipa-healthcheck only report errors. A fully-functioning IdM installation returns an empty result of [] . Additional resources Use ipa-healthcheck --help to see all supported arguments. 24.3. Running IdM Healthcheck Healthcheck can be run manually or automatically using log rotation Prerequisites The Healthcheck tool must be installed. See Installing IdM Healthcheck . Procedure To run healthcheck manually, enter the ipa-healthcheck command. Additional resources For all options, see the man page: man ipa-healthcheck . 24.4. Additional resources See the following sections of the Using IdM Healthcheck to monitor your IdM environment guide for examples of using IdM Healthcheck. Checking services Verifying your IdM and AD trust configuration Verifying certificates Verifying system certificates Checking disk space Verifying permissions of IdM configuration files Checking replication

Commands:
dnf install ipa-healthcheck
ipa-healthcheck --failures-only []
ipa-healthcheck
8.57. gpxe 8.57.1. RHBA-2013:1628 - gpxe bug fix update Updated gpxe packages that fix one bug are now available for Red Hat Enterprise Linux 6. The gpxe packages provide gPXE, an open source Pre-boot Execution Environment (PXE) implementation and bootloader. Bug Fix BZ# 972671 A DHCP server can be configured to use the Pre-Boot Execution Environment (PXE) to boot virtual machines using the gPXE utility. Previously, PXE boot failed when the -server details had come from a different DHCP server. This update applies a patch to fix this bug and PXE boot now works as expected in the described scenario. Users of gpxe are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 3. Minimum Hardware Requirements 16 GB Java Virtual Machine memory size A modern multi-core processor or a multi-socket system with multi-core processors 20 GB or more disk space for the JBoss server product and DV components. This will consist of: 1 GB disk for installed product files 5 GB or more for log files and deployed artifacts 15 GB (default) for BufferManager maxBufferSpace If Modeshape is used, you will need an additional 5 GB or more of filespace. This will suffice for your development or testing system. For a more detailed discussion of system requirements when you later go to install Red Hat JBoss Data Virtualization on a production system, please refer to the Installation Guide.

Commands:
Chapter 8. Using Redis Cache with dynamic plugins You can use the Redis cache store to improve RHDH performance and reliability. Plugins in RHDH receive dedicated cache connections, which are powered by Keyv. 8.1. Installing Redis Cache in Red Hat Developer Hub Prerequisites You have installed Red Hat Developer Hub by using either the Operator or Helm chart. You have an active Redis server. For more information on setting up an external Redis server, see the Redis official documentation . Procedure Add the following code to your app-config.yaml file: backend: cache: store: redis connection: redis://user:pass@cache.example.com:6379 useRedisSets: true 8.2. Configuring Redis Cache in Red Hat Developer Hub 8.2.1. useRedisSets The useRedisSets option lets you decide whether to use Redis sets for key management. By default, this option is set to true . When useRedisSets is enabled ( true ): A namespace for the Redis sets is created, and all generated keys are added to that namespace, enabling group management of the keys. When a key is deleted, it's removed from the main storage and the Redis set. When using the clear function to delete all keys, every key in the Redis set is checked for deletion, and the set itself is also removed. Note In high-performance scenarios, enabling useRedisSets can result in memory leaks. If you are running a high-performance application or service, you must set useRedisSets to false . When you set useRedisSets to false , the keys are handled individually and Redis sets are not utilized. This configuration might lead to performance issues in production when using the clear function, as it requires iterating over all keys for deletion.

Commands:
backend: cache: store: redis connection: redis://user:pass@cache.example.com:6379 useRedisSets: true
Chapter 8. Monitoring Infinispan Query provides access to statistics and operations related to indexing. The statistics provide information about classes being indexed and entities stored in the index. Lucene query and object loading times can also be determined by specifying the generate_statistics property in the configuration. Report a bug 8.1. About Java Management Extensions (JMX) Java Management Extension (JMX) is a Java based technology that provides tools to manage and monitor applications, devices, system objects, and service oriented networks. Each of these objects is managed, and monitored by MBeans . JMX is the de facto standard for middleware management and administration. As a result, JMX is used in Red Hat JBoss Data Grid to expose management and statistical information. Report a bug 8.1.1. Using JMX with Red Hat JBoss Data Grid Management in Red Hat JBoss Data Grid instances aims to expose as much relevant statistical information as possible. This information allows administrators to view the state of each instance. While a single installation can comprise of tens or hundreds of such instances, it is essential to expose and present the statistical information for each of them in a clear and concise manner. In JBoss Data Grid, JMX is used in conjunction with JBoss Operations Network (JON) to expose this information and present it in an orderly and relevant manner to the administrator. Report a bug

Commands:
Appendix A. Using your subscription Streams for Apache Kafka 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 Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2025-03-05 17:09:55 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 5. Configuring automation controller websocket connections You can configure automation controller in order to align the websocket configuration with your nginx or load balancer configuration. 5.1. Websocket configuration for automation controller Automation controller nodes are interconnected through websockets to distribute all websocket-emitted messages throughout your system. This configuration setup enables any browser client websocket to subscribe to any job that might be running on any automation controller node. Websocket clients are not routed to specific automation controller nodes. Instead, any automation controller node can handle any websocket request and each automation controller node must know about all websocket messages destined for all clients. You can configure websockets at /etc/tower/conf.d/websocket_config.py in all of your automation controller nodes and the changes will be effective after the service restarts. Automation controller automatically handles discovery of other automation controller nodes through the Instance record in the database. Important Your automation controller nodes are designed to broadcast websocket traffic across a private, trusted subnet (and not the open Internet). Therefore, if you turn off HTTPS for websocket broadcasting, the websocket traffic, composed mostly of Ansible playbook stdout, is sent unencrypted between automation controller nodes. 5.1.1. Configuring automatic discovery of other automation controller nodes You can configure websocket connections to enable automation controller to automatically handle discovery of other automation controller nodes through the Instance record in the database. Edit automation controller websocket information for port and protocol, and confirm whether to verify certificates with True or False when establishing the websocket connections: BROADCAST_WEBSOCKET_PROTOCOL = 'http' BROADCAST_WEBSOCKET_PORT = 80 BROADCAST_WEBSOCKET_VERIFY_CERT = False Restart automation controller with the following command: USD automation-controller-service restart

Commands:
BROADCAST_WEBSOCKET_PROTOCOL = 'http' BROADCAST_WEBSOCKET_PORT = 80 BROADCAST_WEBSOCKET_VERIFY_CERT = False
automation-controller-service restart
21.2.3. SELinux Utilities The following are some of the most commonly used SELinux utilities: /usr/bin/setenforce - Modifies in real-time the mode SELinux is running. By executing setenforce 1 , SELinux is put in enforcing mode. By executing setenforce 0 , SELinux is put in permissive mode. To actually disable SELinux, you need to either set the parameter in /etc/sysconfig/selinux or pass the parameter selinux=0 to the kernel, either in /etc/grub.conf or at boot time. /usr/bin/sestatus -v - Gets the detailed status of a system running SELinux. The following example shows an excerpt of sestatus output: /usr/bin/newrole - Runs a new shell in a new context, or role. Policy must allow the transition to the new role. /sbin/restorecon - Sets the security context of one or more files by marking the extended attributes with the appropriate file or security context. /sbin/fixfiles - Checks or corrects the security context database on the file system. Refer to the man page associated with these utilities for more information. For more information on all binary utilities available, refer to the setools or policycoreutils package contents by running rpm -ql <package-name> , where <package-name> is the name of the specific package.

Commands:
SELinux status: enabled SELinuxfs mount: /selinux Current mode: enforcing Policy version: 18
Chapter 12. Configuring the node port service range As a cluster administrator, you can expand the available node port range. If your cluster uses of a large number of node ports, you might need to increase the number of available ports. The default port range is 30000-32767 . You can never reduce the port range, even if you first expand it beyond the default range. 12.1. Prerequisites Your cluster infrastructure must allow access to the ports that you specify within the expanded range. For example, if you expand the node port range to 30000-32900 , the inclusive port range of 32768-32900 must be allowed by your firewall or packet filtering configuration. 12.2. Expanding the node port range You can expand the node port range for the cluster. Prerequisites Install the OpenShift CLI ( oc ). Log in to the cluster with a user with cluster-admin privileges. Procedure To expand the node port range, enter the following command. Replace <port> with the largest port number in the new range. USD oc patch network.config.openshift.io cluster --type=merge -p \ '{ "spec": { "serviceNodePortRange": "30000-<port>" } }' Tip You can alternatively apply the following YAML to update the node port range: apiVersion: config.openshift.io/v1 kind: Network metadata: name: cluster spec: serviceNodePortRange: "30000-<port>" Example output network.config.openshift.io/cluster patched To confirm that the configuration is active, enter the following command. It can take several minutes for the update to apply. USD oc get configmaps -n openshift-kube-apiserver config \ -o jsonpath="{.data['config\.yaml']}" | \ grep -Eo '"service-node-port-range":["[[:digit:]]+-[[:digit:]]+"]' Example output "service-node-port-range":["30000-33000"] 12.3. Additional resources Configuring ingress cluster traffic using a NodePort Network [config.openshift.io/v1 ] Service [core/v1 ]

Commands:
oc patch network.config.openshift.io cluster --type=merge -p '{ "spec": { "serviceNodePortRange": "30000-<port>" } }'
apiVersion: config.openshift.io/v1 kind: Network metadata: name: cluster spec: serviceNodePortRange: "30000-<port>"
network.config.openshift.io/cluster patched
oc get configmaps -n openshift-kube-apiserver config -o jsonpath="{.data['config\.yaml']}" | grep -Eo '"service-node-port-range":["[[:digit:]]+-[[:digit:]]+"]'
"service-node-port-range":["30000-33000"]