mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Generating and maintaining the diagnostic reports using the RHEL web console Generate, download, and delete the diagnostic reports in the RHEL web console. 2.1. Generating diagnostic reports using the RHEL web console Prerequisites The RHEL web console has been installed. For details, see Installing the web console . The cockpit-storaged package is installed on your system. You have administrator privileges. Procedure Log in to the RHEL web console. For details, see Logging in to the web console . In the left side menu, select Tools >> Diagnostic reports . To generate a new diagnostic report, click the Run report button. Enter the label for the report you want to create. (Optional) Customize your report. Enter the encryption passphrase to encrypt your report. If you want to skip the encryption of the report, leave the field empty. Check the checkbox Obfuscate network addresses, hostnames, and usernames to obfuscate certain data. Check the checkbox Use verbose logging to increase logging verbosity. Click the Run report button to generate a report and wait for the process to complete. You can stop generating the report using the Stop report button. 2.2. Downloading diagnostic reports using the RHEL web console Prerequisites The RHEL web console has been installed. For details, see Installing the web console . You have administrator privileges. One or more diagnostic reports have been generated. Procedure Log in to the RHEL web console. For details, see Logging in to the web console . In the left side menu, select Tools >> Diagnostic reports . Click the Download button to the report that you want to download. The download will start automatically. steps For the methods on how to provide Red Hat Technical Support team with your diagnostic report, see Methods for providing an sos report to Red Hat technical support . 2.3. Deleting diagnostic reports using the RHEL web console Prerequisites The RHEL web console has been installed. For details, see Installing the web console . You have administrator privileges. One or more diagnostic reports have been generated. Procedure Log in to the RHEL web console. For details, see Logging in to the web console . In the left side menu, select Tools >> Diagnostic reports . Click the vertical ellipsis by the Download button to the report that you want to delete, then click on the Delete button. In the Delete report permanently? window, click the Delete button to delete the report.

Commands:
22.2. Persistent Module Loading Kernel modules are usually loaded directly by the facility that requires them, which is given correct settings in the /etc/modprobe.conf file. However, it is sometimes necessary to explicitly force the loading of a module at boot time. Red Hat Enterprise Linux checks for the existence of the /etc/rc.modules file at boot time, which contains various commands to load modules. The rc.modules should be used, and not rc.local because rc.modules is executed earlier in the boot process. For example, the following commands configure loading of the foo module at boot time (as root): Note This approach is not necessary for network and SCSI interfaces because they have their own specific mechanisms.

Commands:
echo modprobe foo >> /etc/rc.modules chmod +x /etc/rc.modules
Chapter 4. Advisories related to this release The following advisories have been issued to document bugfixes and CVE fixes included in this release: RHSA-2022:7002 RHSA-2022:7003 RHSA-2022:7004 RHSA-2022:7005 RHSA-2022:7006 RHSA-2022:7007 RHSA-2022:7049 RHSA-2022:7050 Revised on 2024-05-10 09:05:50 UTC

Commands:
14.5.20. Domain Retrieval Commands The following commands will display different information about a given domain virsh domhostname domain displays the host name of the specified domain provided the hypervisor can publish it. virsh dominfo domain displays basic information about a specified domain. virsh domuid domain|ID converts a given domain name or ID into a UUID. virsh domid domain|ID converts a given domain name or UUID into an ID. virsh domjobabort domain aborts the currently running job on the specified domain. virsh domjobinfo domain displays information about jobs running on the specified domain, including migration statistics virsh domname domain ID|UUID converts a given domain ID or UUID into a domain name. virsh domstate domain displays the state of the given domain. Using the --reason option will also display the reason for the displayed state. virsh domcontrol domain displays the state of an interface to VMM that were used to control a domain. For states that are not OK or Error, it will also print the number of seconds that have elapsed since the control interface entered the displayed state. Example 14.2. Example of statistical feedback In order to get information about the domain, run the following command:

Commands:
virsh domjobinfo rhel6 Job type: Unbounded Time elapsed: 1603 ms Data processed: 47.004 MiB Data remaining: 658.633 MiB Data total: 1.125 GiB Memory processed: 47.004 MiB Memory remaining: 658.633 MiB Memory total: 1.125 GiB Constant pages: 114382 Normal pages: 12005 Normal data: 46.895 MiB Expected downtime: 0 ms Compression cache: 64.000 MiB Compressed data: 0.000 B Compressed pages: 0 Compression cache misses: 12005 Compression overflows: 0
4.32. coreutils 4.32.1. RHBA-2011:1693 - coreutils bug fix update Updated coreutils packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The coreutils packages contain the core GNU utilities. These packages combine the old GNU fileutils, sh-utils, and textutils packages. Bug Fixes BZ# 691292 Prior to this update, SELinux appeared to be disabled when building coreutils in Mock. As a result, coreutils did not build. With this update, SELinux determines more precisely whether it is disabled or not. Now, the packages are built successfully. BZ# 703712 Previously, incorrect signal handling could cause various problems for tcsh users logging into the root shell using the su utility. Signal masking in the subshell called by the su utility has been modified to respect the SIGTSTP signal as well as the SIGSTOP signal. BZ# 715557 When using the "-Z/--context" option in the cp utility, the SELinux context of a file was not changed if the file destination already existed. The utility has been modified and the context is changed as expected. However, this option is not portable to other systems. BZ# 720325 Prior to this update, the acl_extended_file() function could cause unnecessary mounts of autofs when using the ls command on a directory with autofs mounted. This update adds the new acl function, acl_extended_file_nofollow(), to prevent unnecessary autofs mounts. BZ# 725618 The description of the "--sleep-interval" option in the tail(1) manual page has been improved to be clearer about the behavior and to match the upstream version of coreutils. All users of coreutils are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.7. Synchronizing Configuration Files After configuring the primary LVS router, there are several configuration files that must be copied to the backup LVS router before you start LVS. These files include: /etc/sysconfig/ha/lvs.cf - the configuration file for the LVS routers. /etc/sysctl - the configuration file that, among other things, turns on packet forwarding in the kernel. /etc/sysconfig/iptables - If you are using firewall marks, you should synchronize one of these files based on which network packet filter you are using. Important The /etc/sysctl.conf and /etc/sysconfig/iptables files do not change when you configure LVS using the Piranha Configuration Tool . 4.7.1. Synchronizing lvs.cf Anytime the LVS configuration file, /etc/sysconfig/ha/lvs.cf , is created or updated, you must copy it to the backup LVS router node. Warning Both the active and backup LVS router nodes must have identical lvs.cf files. Mismatched LVS configuration files between the LVS router nodes can prevent failover. The best way to do this is to use the scp command. Important To use scp the sshd must be running on the backup router, see Section 2.1, "Configuring Services on the LVS Routers" for details on how to properly configure the necessary services on the LVS routers. Issue the following command as the root user from the primary LVS router to sync the lvs.cf files between the router nodes: scp /etc/sysconfig/ha/lvs.cf n.n.n.n :/etc/sysconfig/ha/lvs.cf In the command, replace n.n.n.n with the real IP address of the backup LVS router.

Commands:
Chapter 18. Virtual Networking This chapter introduces the concepts needed to create, start, stop, remove, and modify virtual networks with libvirt. Additional information can be found in the libvirt reference chapter 18.1. Virtual Network Switches Libvirt virtual networking uses the concept of a virtual network switch . A virtual network switch is a software construct that operates on a host physical machine server, to which virtual machines (guests) connect. The network traffic for a guest is directed through this switch: Figure 18.1. Virtual network switch with two guests Linux host physical machine servers represent a virtual network switch as a network interface. When the libvirtd daemon ( libvirtd ) is first installed and started, the default network interface representing the virtual network switch is virbr0 . This virbr0 interface can be viewed with the ip command like any other interface:

Commands:
ip addr show virbr0 3: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN link/ether 1b:c4:94:cf:fd:17 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
Chapter 10. Supplementary Workstation Variant The following table lists all the packages in the Supplementary Workstation variant. For more information about support scope, see the Scope of Coverage Details document. Package Core Package? License acroread No Commercial acroread-plugin No Commercial chromium-browser No BSD and LGPLv2+ flash-plugin No Commercial java-1.5.0-ibm No IBM Binary Code License java-1.5.0-ibm-demo No IBM Binary Code License java-1.5.0-ibm-devel No IBM Binary Code License java-1.5.0-ibm-javacomm No IBM Binary Code License java-1.5.0-ibm-jdbc No IBM Binary Code License java-1.5.0-ibm-plugin No IBM Binary Code License java-1.5.0-ibm-src No IBM Binary Code License java-1.6.0-ibm No IBM Binary Code License java-1.6.0-ibm-demo No IBM Binary Code License java-1.6.0-ibm-devel No IBM Binary Code License java-1.6.0-ibm-javacomm No IBM Binary Code License java-1.6.0-ibm-jdbc No IBM Binary Code License java-1.6.0-ibm-plugin No IBM Binary Code License java-1.6.0-ibm-src No IBM Binary Code License java-1.7.1-ibm No IBM Binary Code License java-1.7.1-ibm-demo No IBM Binary Code License java-1.7.1-ibm-devel No IBM Binary Code License java-1.7.1-ibm-jdbc No IBM Binary Code License java-1.7.1-ibm-plugin No IBM Binary Code License java-1.7.1-ibm-src No IBM Binary Code License java-1.8.0-ibm No IBM Binary Code License java-1.8.0-ibm-demo No IBM Binary Code License java-1.8.0-ibm-devel No IBM Binary Code License java-1.8.0-ibm-jdbc No IBM Binary Code License java-1.8.0-ibm-plugin No IBM Binary Code License java-1.8.0-ibm-src No IBM Binary Code License kmod-kspiceusb-rhel60 No GPLv2 spice-usb-share No Redistributable, no modification permitted system-switch-java No GPLv2+ virtio-win No Red Hat Proprietary and GPLv2

Commands:
Chapter 1. Overview of Streams for Apache Kafka Streams for Apache Kafka supports highly scalable, distributed, and high-performance data streaming based on the Apache Kafka project. The main components comprise: Kafka Broker Messaging broker responsible for delivering records from producing clients to consuming clients. Kafka Streams API API for writing stream processor applications. Producer and Consumer APIs Java-based APIs for producing and consuming messages to and from Kafka brokers. Kafka Bridge Streams for Apache Kafka Bridge provides a RESTful interface that allows HTTP-based clients to interact with a Kafka cluster. Kafka Connect A toolkit for streaming data between Kafka brokers and other systems using Connector plugins. Kafka MirrorMaker Replicates data between two Kafka clusters, within or across data centers. Kafka Exporter An exporter used in the extraction of Kafka metrics data for monitoring. A cluster of Kafka brokers is the hub connecting all these components. Figure 1.1. Streams for Apache Kafka architecture 1.1. Using the Kafka Bridge to connect with a Kafka cluster You can use the Kafka Bridge API to create and manage consumers and send and receive records over HTTP rather than the native Kafka protocol. When you set up the Kafka Bridge you configure HTTP access to the Kafka cluster. You can then use the Kafka Bridge to produce and consume messages from the cluster, as well as performing other operations through its REST interface. Additional resources For information on installing and using the Kafka Bridge, see Using the Kafka Bridge . 1.2. Document conventions User-replaced values User-replaced values, also known as replaceables , are shown in with angle brackets (< >). Underscores ( _ ) are used for multi-word values. If the value refers to code or commands, monospace is also used. For example, the following code shows that <bootstrap_address> and <topic_name> must be replaced with your own address and topic name: bin/kafka-console-consumer.sh --bootstrap-server <broker_host>:<port> --topic <topic_name> --from-beginning

Commands:
bin/kafka-console-consumer.sh --bootstrap-server <broker_host>:<port> --topic <topic_name> --from-beginning
2.6. DeviceKit-power and devkit-power In Red Hat Enterprise Linux 6 DeviceKit-power assumes the power management functions that were part of HAL and some of the functions that were part of GNOME Power Manager in releases of Red Hat Enterprise Linux (refer also to Section 2.7, "GNOME Power Manager" ). DeviceKit-power provides a daemon, an API, and a set of command-line tools. Each power source on the system is represented as a device, whether it is a physical device or not. For example, a laptop battery and an AC power source are both represented as devices. You can access the command-line tools with the devkit-power command and the following options: --enumerate , -e displays an object path for each power devices on the system. Example 2.6. Sample Output of Object Paths --dump , -d displays the parameters for all power devices on the system. --wakeups , -w displays the CPU wakeups on the system. --monitor , -m monitors the system for changes to power devices, for example, the connection or disconnection of a source of AC power, or the depletion of a battery. Press Ctrl + C to stop monitoring the system. --monitor-detail monitors the system for changes to power devices, for example, the connection or disconnection of a source of AC power, or the depletion of a battery. The --monitor-detail option presents more detail than the --monitor option. Press Ctrl + C to stop monitoring the system. --show-info object_path , -i object_path displays all information available for a particular object path. Example 2.7. Using the -i option To obtain information about a battery on your system represented by the object path /org/freedesktop/UPower/DeviceKit/power/battery_BAT0 , run:

Commands:
devkit-power -e USD /org/freedesktop/DeviceKit/power/devices/line_power_AC USD /org/freedesktop/UPower/DeviceKit/power/battery_BAT0
devkit-power -i /org/freedesktop/UPower/DeviceKit/power/battery_BAT0
Appendix G. The Source-to-Image (S2I) build process Source-to-Image (S2I) is a build tool for generating reproducible Docker-formatted container images from online SCM repositories with application sources. With S2I builds, you can easily deliver the latest version of your application into production with shorter build times, decreased resource and network usage, improved security, and a number of other advantages. OpenShift supports multiple build strategies and input sources . For more information, see the Source-to-Image (S2I) Build chapter of the OpenShift Container Platform documentation. You must provide three elements to the S2I process to assemble the final container image: The application sources hosted in an online SCM repository, such as GitHub. The S2I Builder image, which serves as the foundation for the assembled image and provides the ecosystem in which your application is running. Optionally, you can also provide environment variables and parameters that are used by S2I scripts . The process injects your application source and dependencies into the Builder image according to instructions specified in the S2I script, and generates a Docker-formatted container image that runs the assembled application. For more information, check the S2I build requirements , build options and how builds work sections of the OpenShift Container Platform documentation.

Commands:
function::stringat Name function::stringat - Returns the char at a given position in the string. Synopsis Arguments str The string to fetch the character from. pos The position to get the character from. 0 = start of the string. General Syntax stringat:long(srt:string, pos:long) Description This function returns the character at a given position in the string or zero if thestring doesn't have as many characters.

Commands:
function stringat:long(str:string,pos:long)
14.8.11. Restore a Guest Virtual Machine Restore a guest virtual machine previously saved with the virsh save command ( Section 14.8.7, "Save a Guest Virtual Machine" ) using virsh : This restarts the saved guest virtual machine, which may take some time. The guest virtual machine's name and UUID are preserved but are allocated for a new id. The virsh restore state-file command can take the following options: --bypass-cache - causes the restore to avoid the file system cache but note that using this option may slow down the restore operation. --xml - this option must be used with an XML file name. Although this option is usually omitted, it can be used to supply an alternative XML file for use on a restored guest virtual machine with changes only in the host-specific portions of the domain XML. For example, it can be used to account for the file naming differences in underlying storage due to disk snapshots taken after the guest was saved. --running - overrides the state recorded in the save image to start the domain as running. --paused - overrides the state recorded in the save image to start the domain as paused.

Commands:
virsh restore state-file
Chapter 109. KafkaTopicSpec schema reference Used in: KafkaTopic Property Property type Description topicName string The name of the topic. When absent this will default to the metadata.name of the topic. It is recommended to not set this unless the topic name is not a valid OpenShift resource name. partitions integer The number of partitions the topic should have. This cannot be decreased after topic creation. It can be increased after topic creation, but it is important to understand the consequences that has, especially for topics with semantic partitioning. When absent this will default to the broker configuration for num.partitions . replicas integer The number of replicas the topic should have. When absent this will default to the broker configuration for default.replication.factor . config map The topic configuration.

Commands:
E.2.13. /proc/kcore This file represents the physical memory of the system and is stored in the core file format. Unlike most /proc/ files, kcore displays a size. This value is given in bytes and is equal to the size of the physical memory (RAM) used plus 4 KB. The contents of this file are designed to be examined by a debugger, such as gdb , and is not human readable. Warning Do not view the /proc/kcore virtual file. The contents of the file scramble text output on the terminal. If this file is accidentally viewed, press Ctrl + C to stop the process and then type reset to bring back the command line prompt.

Commands:
Appendix A. Component Versions This appendix provides a list of key components and their versions in the Red Hat Enterprise Linux 7.7 release. Table A.1. Component Versions Component Version kernel 3.10.0-1062 kernel-alt 4.14.0-115 QLogic qla2xxx driver 10.00.00.12.07.7-k QLogic qla4xxx driver 5.04.00.00.07.02-k0 Emulex lpfc driver 0:12.0.0.10 iSCSI initiator utils ( iscsi-initiator-utils ) 6.2.0.874-11 DM-Multipath ( device-mapper-multipath ) 0.4.9-127 LVM ( lvm2 ) 2.02.185-2 qemu-kvm [a] 1.5.3-167 qemu-kvm-ma [b] 2.12.0-18 [a] The qemu-kvm packages provide KVM virtualization on AMD64 and Intel 64 systems. [b] The qemu-kvm-ma packages provide KVM virtualization on IBM POWER8, IBM POWER9, and IBM Z. Note that KVM virtualization on IBM POWER9 and IBM Z also requires using the kernel-alt packages.

Commands:
8.119. librtas 8.119.1. RHBA-2014:1427 - librtas bug fix and enhancement update Updated librtas packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The librtas packages contain a set of libraries that allow access to the Run-Time Abstraction Services (RTAS) on 64-bit PowerPC architectures. The librtasevent library contains definitions and routines for analyzing RTAS events. Note The librtas packages have been upgraded to upstream version 1.3.10, which provides a number of bug fixes and enhancements over the version. Notably, this update adds RTAS support for PCI hot plug support on POWERPC 8 systems and improves support for RTAS Event parsing on little-endian POWERPC systems. In addition, the librtasevent library is now able to analyze hot plug events. (BZ# 1073037 ) Users of librtas are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
7.7. Networked Versus Local Printers Depending on organizational needs, it may be unnecessary to assign one printer to each member of your organization. Such overlap in expenditure can eat into allotted budgets, leaving less capital for other necessities. While local printers attached via a parallel or USB cable to every workstation are an ideal solution for the user, it is usually not economically feasible. Printer manufacturers have addressed this need by developing departmental (or workgroup) printers. These machines are usually durable, fast, and have long-life consumables. Workgroup printers usually are attached to a print server, a standalone device (such as a reconfigured workstation) that handles print jobs and routes output to the proper printer when available. More recent departmental printers include built-in or add-on network interfaces that eliminate the need for a dedicated print server.

Commands:
Chapter 3. Getting your cluster ID When providing information to Red Hat Support, it is helpful to provide the unique identifier of your cluster. For MicroShift, you can get your cluster ID manually by using the OpenShift CLI ( oc ) or by retrieving the ID from a file. Note A cluster ID is created only after the MicroShift service runs for the first time after installation. 3.1. Getting the cluster ID of a running cluster Use either the of the following steps to get the ID of a running cluster. Procedure Get the ID of a running cluster using oc get by entering the following command: USD oc get namespaces kube-system -o jsonpath={.metadata.uid} Example output 7cf13853-68f4-454e-8f5c-1af748cbfb1a Get the ID of a running cluster by retrieving it from the cluster-id file by entering the following command: USD sudo cat /var/lib/microshift/cluster-id Example output 7cf13853-68f4-454e-8f5c-1af748cbfb1a 3.2. Getting the cluster ID of a stopped cluster For a cluster that ran before, but is not running now, you can get the cluster ID from the cluster-id file in the /var/lib/microshift directory. Procedure Get the ID of a stopped cluster by retrieving it from the cluster-id file by entering the following command: USD sudo cat /var/lib/microshift/cluster-id Example output 7cf13853-68f4-454e-8f5c-1af748cbfb1a

Commands:
oc get namespaces kube-system -o jsonpath={.metadata.uid}
7cf13853-68f4-454e-8f5c-1af748cbfb1a
sudo cat /var/lib/microshift/cluster-id
7cf13853-68f4-454e-8f5c-1af748cbfb1a
sudo cat /var/lib/microshift/cluster-id
7cf13853-68f4-454e-8f5c-1af748cbfb1a