mtpti5iD/redhat-docs_dataset huggingface dataset:
A.3. PCP Installation The most recent tested version of PCP should be available to download from the Red Hat Enterprise Linux 7 repositories. The debugfs file system must be mounted in order for the GFS2 PMDA to operate correctly. If the debugfs file system is not mounted, run the following commands commands before installing the GFS2 PMDA. The GFS2 PMDA is not enabled by default upon installation. In order use GFS2 metric monitoring through PCP, you must enable the GFS2 domain agent. Use the following commands to install PCP and the GFS2 PMDA module and to enable GFS2 PMDA. Note that the PMDA install script must be run as root. When running the PMDA installation script, you will be prompted for which role you would like the PMDA to take: collector allows the collection of performance metrics on the current system monitor only allows the system to monitor local system or remote systems or both local and remote system both enables both the collector and monitor configurations In most cases the default choice (both collector and monitor) is sufficient to allow the PMDA to operate correctly. If there are any errors or warning with the installation of the GFS2 PMDA, make sure that PMCD is started and running and that debugfs is mounted (there may be warnings in the event that there is not at least one GFS2 file system loaded on the system). Note When installing the GFS2 PMDA on cluster nodes the default choice for PMDA configuration (both) will be sufficient to allow the PMDA to run correctly. On workstation machines where you intend just to monitor the data from remote PCP installations, it is recommended you you install the PMDA as a monitor.

Commands:
mkdir /sys/kernel/debug mount -t debugfs none /sys/kernel/debug
yum install pcp pcp-gui pcp-pmda-gfs2 cd /var/lib/pcp/pmdas/gfs2 ./Install
./Install You will need to choose an appropriate configuration for installation of the "gfs2" Performance Metrics Domain Agent (PMDA). collector collect performance statistics on this system monitor allow this system to monitor local and/or remote systems both collector and monitor configuration for this system Please enter c(ollector) or m(onitor) or b(oth) [ b ] Updating the Performance Metrics Name Space (PMNS) Terminate PMDA if already installed Updating the PMCD control file, and notifying PMCD Waiting for pmcd to terminate Starting pmcd Starting pmlogger Check gfs2 metrics have appeared ... 316 metrics and 205 values
C.4. Example User Interface Plug-in Deployment Follow these instructions to create a user interface plug-in that runs a Hello World! program when you sign in to the Red Hat Virtualization Manager Administration Portal. Deploying a Hello World! Plug-in Create a plug-in descriptor by creating the following file in the Manager at /usr/share/ovirt-engine/ui-plugins/helloWorld.json : Create the plug-in host page by creating the following file in the Manager at /usr/share/ovirt-engine/ui-plugins/hello-files/start.html : If you have successfully implemented the Hello World! plug-in, you will see this screen when you sign in to the Administration Portal: Figure C.1. A Successful Implementation of the Hello World! Plug-in

Commands:
name: HelloWorld
url: /ovirt-engine/webadmin/plugin/HelloWorld/start.html
resourcePath: hello-files
<!DOCTYPE html><html><head> <script> var api = parent.pluginApi('HelloWorld'); api.register({ UiInit: function() { window.alert('Hello world'); } }); api.ready(); </script> </head><body></body></html>
Chapter 3. Deploying Kafka components using the Streams for Apache Kafka operator When installed on Openshift, the Streams for Apache Kafka operator makes Kafka components available for installation from the user interface. The following Kafka components are available for installation: Kafka Kafka Connect Kafka MirrorMaker Kafka MirrorMaker 2 Kafka Topic Kafka User Kafka Bridge Kafka Connector Kafka Rebalance You select the component and create an instance. As a minimum, you create a Kafka instance. This procedure describes how to create a Kafka instance using the default settings. You can configure the default installation specification before you perform the installation. The process is the same for creating instances of other Kafka components. Prerequisites The Streams for Apache Kafka operator is installed on the OpenShift cluster . Procedure Navigate in the web console to the Operators > Installed Operators page and click Streams for Apache Kafka to display the operator details. From Provided APIs , you can create instances of Kafka components. Click Create instance under Kafka to create a Kafka instance. By default, you'll create a Kafka cluster called my-cluster with three Kafka broker nodes and three ZooKeeper nodes. The cluster uses ephemeral storage. Click Create to start the installation of Kafka. Wait until the status changes to Ready .

Commands:
Chapter 1. About Red Hat AMQ 7 Red Hat AMQ provides fast, lightweight, and secure messaging for Internet-scale applications. AMQ Broker supports multiple protocols and fast message persistence. AMQ Interconnect leverages the AMQP protocol to distribute and scale your messaging resources across the network. AMQ Clients provides a suite of messaging APIs for multiple languages and platforms. Think of the AMQ components as tools inside a toolbox. They can be used together or separately to build and maintain your messaging application, and AMQP is the glue in the toolbox that binds them together. AMQ components share a common management console, so you can manage them from a single interface. Note Red Hat AMQ 7 includes AMQ Streams, which provides container images and Operators for running Apache Kafka on OpenShift Container Platform. AMQ Streams does not support AMQP. 1.1. Key features AMQ enables developers to build messaging applications that are fast, reliable, and easy to administer. Messaging at internet scale AMQ contains the tools to build advanced, multi-datacenter messaging networks. It can connect clients, brokers, and stand-alone services in a seamless messaging fabric. Top-tier security and performance AMQ offers modern SSL/TLS encryption and extensible SASL authentication. AMQ delivers fast, high-volume messaging and class-leading JMS performance. Broad platform and language support AMQ works with multiple languages and operating systems, so your diverse application components can communicate. AMQ supports C++, Java, JavaScript, Python, Ruby, and .NET applications, as well as Linux, Windows, and JVM-based environments. Focused on standards AMQ implements the Java JMS 1.1 and 2.0 API specifications. Its components support the ISO-standard AMQP 1.0 and MQTT messaging protocols, as well as STOMP and WebSocket. Centralized management With AMQ, you can administer all AMQ components from a single management interface. You can use JMX or the REST interface to manage servers programmatically.

Commands:
5.3. Starting JBoss Data Virtualization as Managed Domain Order of Operations The domain controller must be started before any slave servers in any server groups in the domain. Use this procedure first on the domain controller, and then on each associated host controller and each other host associated with the domain. Please refer to the https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/6.4/html-single/administration_and_configuration_guide/index for more information. Procedure 5.1. Start the Platform Service as a Managed Domain For Red Hat Enterprise Linux, run this command: EAP_HOME /bin/domain.sh For Microsoft Windows, run this command: EAP_HOME \bin\domain.bat To list all available parameters for the start-up scripts, use the -h parameter.

Commands:
Chapter 6. Conversion rollback The Convert2RHEL utility provides a limited rollback functionality under the following conditions: If Convert2RHEL has been run in the analyze mode, the utility performs a rollback of all changes it made. If the utility fails or is stopped by the user, only changes performed until Convert2RHEL starts replacing packages from the original distribution with RHEL packages can be reverted. This moment is indicated by the warning message: followed by a question whether you wish to continue with the process. Note If the -y option is used with the convert2rhel command, the question indicating the moment after which the automated rollback is no longer possible is skipped. Warning If the conversion process is canceled or fails after Convert2RHEL has started the package replacement phase, the system can become dysfunctional. In such a case, manual fixes will be needed. Please contact Red Hat Consulting services for assistance.

Commands:
The tool allows rollback of any action until this point. By continuing all further changes on the system will need to be reverted manually by the user, if necessary.
Chapter 5. New features Red Hat 3scale API Management 2.15 provides the following new features and enhancements: Support for Red Hat build of Keycloak ( THREESCALE-10712 ) Support for Redis 7.2 as an external datastore ( THREESCALE-10735 ) API gateway (APIcast) enhancements: APIcast compatibility with ARM64 architecture ( THREESCALE-10586 ) Added support for chunked requests ( THREESCALE-9542 ) Ability to use Basic Authentication on the HTTP proxy ( THREESCALE-4393 ) 3scale Operator Enhancements: Allow enabling OpenTelemetry on APIcast ( THREESCALE-10643 ) Auth-keys support for Application CR ( THREESCALE-10613 ) Improved status reporting ( THREESCALE-10037 ) Improved proxy configuration promotion ( THREESCALE-10381 ) Extended capabilities in Tenant CR ( THREESCALE-10525 ) Security, performance, and other general improvements: Introducing Openshift APIs for Data Protection as the standard backup and restore mechanism in 3scale ( THREESCALE-9326 ) Horizontal Pod Autoscaling for Backend Listener, Backend worker and APIcast ( THREESCALE-5894 ) Transitioned from using DeploymentConfigs to Deployments for improved alignment with OpenShift standards ( THREESCALE-10163 ) Enable support for the content-type 'application/problem+json' in the Error Responses ( THREESCALE-8909 ) Improved user experience in login page preventing automatic re-entries ( THREESCALE-10797 ) Improvements in the User Interface ( THREESCALE-9847 , THREESCALE-8748 , THREESCALE-8747 , THREESCALE-10455 )

Commands:
22.7. Managing the Time on Virtual Machines Virtual machines cannot access a real hardware clock and a virtual clock is not stable enough as the stability is dependent on the host systems work load. For this reason, para-virtualized clocks should be provided by the virtualization application in use. On Red Hat Enterprise Linux with KVM the default clock source is kvm-clock . See the KVM guest timing management chapter of the Virtualization Host Configuration and Guest Installation Guide .

Commands:
7.274. x3270 7.274.1. RHBA-2013:0383 - x3270 bug fix update Updated x3270 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The x3270 packages provide an emulator for the IBM 3278 (monochrome) and 3279 (color) terminals. Bug Fix BZ#801139 Prior to this update, the x3270 emulator failed to support the double-byte character set (DBCS). As a consequence, the character sets option for Japanese was disabled. This update modifies the underlying code to enable DBCS and adds the icu packages as a dependency. Now, Japanese character sets are again available. All users of x3270 are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 6. Managed KIE Server A managed instance requires an available Process Automation Manager controller to start KIE Server. A Process Automation Manager controller manages KIE Server configuration in a centralized way. Each Process Automation Manager controller can manage multiple configurations at once, and there can be multiple Process Automation Manager controllers in the environment. Managed KIE Server can be configured with a list of Process Automation Manager controllers, but will only connect to one at a time. Important All Process Automation Manager controllers should be synchronized to ensure that the same set of configuration is provided to the server, regardless of the Process Automation Manager controller to which it connects. When KIE Server is configured with a list of Process Automation Manager controllers, it will attempt to connect to each of them at startup until a connection is successfully established with one of them. If a connection cannot be established, the server will not start, even if there is a local storage available with configuration. This ensures consistency and prevents the server from running with redundant configuration. Note To run KIE Server in standalone mode without connecting to Process Automation Manager controllers, see Chapter 7, Unmanaged KIE Server .

Commands:
Chapter 4. External storage services Red Hat OpenShift Data Foundation can use IBM FlashSystems or make services from an external Red Hat Ceph Storage cluster available for consumption through OpenShift Container Platform clusters running on the following platforms: VMware vSphere Bare metal Red Hat OpenStack platform (Technology Preview) IBM Power IBM Z The OpenShift Data Foundation operators create and manage services to satisfy Persistent Volume (PV) and Object Bucket Claims (OBCs) against the external services. External cluster can serve block, file, and object storage classes for applications that run on OpenShift Container Platform. The operators do not deploy or manage the external clusters.

Commands:
Preface Red Hat Fuse provides two enterprise monitoring tools for viewing and managing Fuse integrations: The Fuse Console is a web-based console that you access from a browser to monitor and manage a running Fuse container. The Fuse Console is based on Hawtio open source software ( https://hawt.io/ ). This guide describes how to use the Fuse Console. Prometheus stores system and integration-level metrics for Fuse distributions. You can use a graphical analytics interface, such as Grafana, to view and analyze the stored historical data. To learn more about using Prometheus, see the the Prometheus documentation . The audience for this guide is Red Hat Fuse on JBoss EAP administrators. This guide assumes that you are familiar with the Red Hat Fuse platform, Apache Camel, and the processing requirements for your organization.

Commands:
probe::nfs.proc.write Name probe::nfs.proc.write - NFS client synchronously writes file to server Synopsis nfs.proc.write Values size read bytes in this execution flags used to set task->tk_flags in rpc_init_task function prot transfer protocol version NFS version bitmask1 V4 bitmask representing the set of attributes supported on this filesystem offset the file offset bitmask0 V4 bitmask representing the set of attributes supported on this filesystem server_ip IP address of server Description All the nfs.proc.write kernel functions were removed in kernel commit 200baa in December 2006, so these probes do not exist on Linux 2.6.21 and newer kernels.

Commands:
Chapter 7. Asynchronous errata updates 7.1. RHSA-2025:0079 OpenShift Data Foundation 4.17.2 bug fixes and security updates OpenShift Data Foundation release 4.17.2 is now available. The bug fixes that are included in the update are listed in the RHSA-2025:0079 advisory. 7.2. RHSA-2024:10986 OpenShift Data Foundation 4.17.1 bug fixes and security updates OpenShift Data Foundation release 4.17.1 is now available. The bug fixes that are included in the update are listed in the RHSA-2024:10986 advisory.

Commands:
Chapter 21. Manually configuring the /etc/resolv.conf file By default, NetworkManager dynamically updates the /etc/resolv.conf file with the DNS settings from active NetworkManager connection profiles. However, you can disable this behavior and manually configure DNS settings in /etc/resolv.conf . Note Alternatively, if you require a specific order of DNS servers in /etc/resolv.conf , see Configuring the order of DNS servers . 21.1. Disabling DNS processing in the NetworkManager configuration By default, NetworkManager manages DNS settings in the /etc/resolv.conf file, and you can configure the order of DNS servers. Alternatively, you can disable DNS processing in NetworkManager if you prefer to manually configure DNS settings in /etc/resolv.conf . Procedure As the root user, create the /etc/NetworkManager/conf.d/90-dns-none.conf file with the following content by using a text editor: Reload the NetworkManager service: Note After you reload the service, NetworkManager no longer updates the /etc/resolv.conf file. However, the last contents of the file are preserved. Optional: Remove the Generated by NetworkManager comment from /etc/resolv.conf to avoid confusion. Verification Edit the /etc/resolv.conf file and manually update the configuration. Reload the NetworkManager service: Display the /etc/resolv.conf file: If you successfully disabled DNS processing, NetworkManager did not override the manually configured settings. Troubleshooting Display the NetworkManager configuration to ensure that no other configuration file with a higher priority overrode the setting: Additional resources NetworkManager.conf(5) man page on your system Configuring the order of DNS servers using NetworkManager 21.2. Replacing /etc/resolv.conf with a symbolic link to manually configure DNS settings By default, NetworkManager manages DNS settings in the /etc/resolv.conf file, and you can configure the order of DNS servers. Alternatively, you can disable DNS processing in NetworkManager if you prefer to manually configure DNS settings in /etc/resolv.conf . For example, NetworkManager does not automatically update the DNS configuration if /etc/resolv.conf is a symbolic link. Prerequisites The NetworkManager rc-manager configuration option is not set to file . To verify, use the NetworkManager --print-config command. Procedure Create a file, such as /etc/resolv.conf.manually-configured , and add the DNS configuration for your environment to it. Use the same parameters and syntax as in the original /etc/resolv.conf . Remove the /etc/resolv.conf file: Create a symbolic link named /etc/resolv.conf that refers to /etc/resolv.conf.manually-configured : Additional resources resolv.conf(5) and NetworkManager.conf(5) man pages on your system Configuring the order of DNS servers using NetworkManager

Commands:
[main] dns=none
systemctl reload NetworkManager
systemctl reload NetworkManager
cat /etc/resolv.conf
NetworkManager --print-config dns=none
rm /etc/resolv.conf
ln -s /etc/resolv.conf.manually-configured /etc/resolv.conf
2.4. Multipath Devices in Logical Volumes After creating multipath devices, you can use the multipath device names just as you would use a physical device name when creating an LVM physical volume. For example, if /dev/mapper/mpath0 is the name of a multipath device, the following command will mark /dev/mapper/mpath0 as a physical volume. You can use the resulting LVM physical device when you create an LVM volume group just as you would use any other LVM physical device. When you create an LVM logical volume that uses active/passive multipath arrays as the underlying physical devices, you should include filters in the lvm.conf file to exclude the disks that underlie the multipath devices. This is because if the array automatically changes the active path to the passive path when it receives I/O, multipath will failover and failback whenever LVM scans the passive path if these devices are not filtered. For active/passive arrays that require a command to make the passive path active, LVM prints a warning message when this occurs. To filter all SCSI devices in the multipath configuration file ( lvm.conf ), include the following filter in the devices section of the file.

Commands:
pvcreate /dev/mapper/mpath0
filter = [ "r/disk/", "r/sd.*/", "a/.*/" ]
5.8. audit 5.8.1. RHBA-2012:0929 - audit bug fix and enhancement update Updated audit packages that fix multiple bugs and add several enhancements are now available for Red Hat Enterprise Linux 6. The audit packages contain the user space utilities for storing and searching the audit records which have been generated by the audit subsystem in the Linux 2.6 kernel. The audit packages have been upgraded to upstream version 2.2, which provides a number of bug fixes and enhancements over the version. The version 2.2 packages introduce the following enhancements: The "auditctl" command now allows shell-escaped file names for better handling of file names with spaces in them. There is a new utility, auvirt, that extracts a report about the virtualization events. The auditd.conf configuration option, "tcp_max_per_addr", now allows up to 1024 concurrent connections from the same IP address. While this is not recommended for normal use, it helps in situations where a number of client systems are behind a NAT, which causes them to appear to have the same IP address. Bug Fixes BZ# 803349 Previously, not enough information was parsed to determine whether audit records are part of the same event if the server's node name was longer than approximately 80 characters. With this update, the problem has been fixed. BZ# 797848 This update fixes a typo in the audit.rules(7) man page. Enhancements BZ# 658630 Prior to this update, if the audit rules had a typo or the command was not supported by the Linux kernel, either an error was triggered and you were able to stop processing the rules or, as the other option, you were able to ignore any errors in which case it completed everything it could but returned success. This update introduces the "-c" option to auditctl which works like the ignore option, but instead of returning success, the "-c" option returns failure if any rule triggers an error. Note that like the ignore option, the "-c" option continues to process all audit rules. BZ# 766920 This release adds support for a new kernel auditing feature that allows for inter-field comparisons. For each audit event, the Linux kernel collects information about what is causing the event. Now, you can use the "-C" option to compare: "auid", "uid", "euid", "suid", "fsuid", or "obj_uid"; and "gid", "egid", "sgid", "fsgid", or "obj_gid". The two groups cannot be mixed. Comparisons can use either the equal or not equal operators. Note that for this enhancement to work, the system must boot the Linux 2.6.32-244 kernel or later. All audit users are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 16. Debug Modes You can enable and disable the DEBUG level logging mode for certain services in the overcloud. To configure debug mode for a service, set the respective debug parameter. For example, OpenStack Identity (keystone) uses the KeystoneDebug parameter. Create a debug.yaml environment file to store debug parameters and set the KeystoneDebug parameter in the parameter_defaults section: After you have set the KeystoneDebug parameter to True , the /var/log/containers/keystone/keystone.log standard keystone log file is updated with DEBUG level logs. For a full list of debug parameters, see "Debug Parameters" in the Overcloud Parameters guide.

Commands:
parameter_defaults: KeystoneDebug: True
16.3. About REPEATABLE_READ REPEATABLE_READ is one of two isolation modes available in Red Hat JBoss Data Grid. Traditionally, REPEATABLE_READ does not allow write operations while read operations are in progress, nor does it allow read operations when write operations occur. This prevents the "non-repeatable read" phenomenon, which occurs when a single transaction has two read operations on the same row but the retrieved values differ (possibly due to a write operation modifying the value between the two read operations). JBoss Data Grid's REPEATABLE_READ isolation mode preserves the value of an entry before a modification occurs. As a result, the "non-repeatable read" phenomenon is avoided because a second read operation on the same entry retrieves the preserved value rather than the new modified value. As a result, the two values retrieved by the two read operations in a single transaction will always match, even if a write operation occurs in a different transaction between the two reads. Report a bug

Commands: