mtpti5iD/redhat-docs_dataset huggingface dataset:
37.3. Updating the Size of Your Multipath Device If multipathing is enabled on your system, you will also need to reflect the change in logical unit size to the logical unit's corresponding multipath device ( after resizing the logical unit). For Red Hat Enterprise Linux 5.3 (or later), you can do this through multipathd . To do so, first ensure that multipathd is running using service multipathd status . Once you've verified that multipathd is operational, run the following command: The multipath_device variable is the corresponding multipath entry of your device in /dev/mapper . Depending on how multipathing is set up on your system, multipath_device can be either of two formats: mpath X , where X is the corresponding entry of your device (for example, mpath0 ) a WWID; for example, 3600508b400105e210000900000490000 To determine which multipath entry corresponds to your resized logical unit, run multipath -ll . This displays a list of all existing multipath entries in the system, along with the major and minor numbers of their corresponding devices. Important Do not use multipathd -k"resize map multipath_device " if there are any commands queued to multipath_device . That is, do not use this command when the no_path_retry parameter (in /etc/multipath.conf ) is set to "queue" , and there are no active paths to the device. If your system is using Red Hat Enterprise Linux 5.0-5.2, you will need to perform the following procedure to instruct the multipathd daemon to recognize (and adjust to) the changes you made to the resized logical unit: Procedure 37.1. Resizing the Corresponding Multipath Device (Required for Red Hat Enterprise Linux 5.0 - 5.2) Dump the device mapper table for the multipathed device using: dmsetup table multipath_device Save the dumped device mapper table as table_name . This table will be re-loaded and edited later. Examine the device mapper table. Note that the first two numbers in each line correspond to the start and end sectors of the disk, respectively. Suspend the device mapper target: dmsetup suspend multipath_device Open the device mapper table you saved earlier (i.e. table_name ). Change the second number (i.e. the disk end sector) to reflect the new number of 512 byte sectors in the disk. For example, if the new disk size is 2GB, change the second number to 4194304. Reload the modified device mapper table: dmsetup reload multipath_device table_name Resume the device mapper target: dmsetup resume multipath_device For more information about multipathing, refer to the Red Hat Enterprise Linux 6 DM Multipath guide.

Commands:
multipathd -k"resize map multipath_device "
Chapter 1. Introduction This document clarifies some important information related to features and support for Red Hat JBoss Data Grid, such as: The two JBoss Data Grid Usage Modes Supported JBoss Data Grid features JBoss Data Grid features that are limited to a technology preview. Report a bug 1.1. About Usage Modes Red Hat JBoss Data Grid offers two usage modes: Remote Client-Server mode Library mode Remote Client-Server mode, which provides a managed, distributed and clusterable data grid server. Applications can remotely access the data grid server using Hot Rod , memcached or REST client APIs. Library mode allows the user to build and deploy a custom runtime environment. The Library usage mode hosts a single data grid node in the applications process, with remote access to nodes hosted in other JVMs. Tested containers for JBoss Data Grid Library mode includes JBoss Enterprise Web Server and JBoss Enterprise Application Platform (see https://access.redhat.com/articles/115883 for details about supported containers). Additionally, Library mode is supported outside the listed containers as a standalone application. Report a bug

Commands:
5.145. liberation-fonts 5.145.1. RHBA-2012:0384 - liberation-fonts bug fix update Updated liberation-fonts packages that fix one bug are now available for Red Hat Enterprise Linux 6. The liberation-fonts packages provide fonts intended to replace the three most commonly used fonts on Microsoft systems: Times New Roman, Arial, and Courier New. Bug Fix BZ# 772165 Previously, the "fonts.dir" file provided with the liberation-fonts packages was empty. As a consequence, legacy applications were not able to make use of liberation-fonts even when the package was installed. This was because the "mkfontscale" command was run after the "mkfontdir" command. The order of running the commands has been changed and legacy applications can use liberation-fonts as expected. All users of liberation-fonts are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.213. tcpdump 7.213.1. RHBA-2015:1294 - tcpdump bug fix and enhancement update Updated tcpdump packages that fix two bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The tcpdump packages contain a command-line tool for monitoring network traffic. Tcpdump can capture and display the packet headers on a particular network interface or on all interfaces. Tcpdump can display all of the packet headers, or just the ones that match particular criteria. Bug Fixes BZ# 972396 Previously, the tcpdump utility was treating the argument for the "-i" option as a number if it contained a numeric prefix and other characters, not as a string. Consequently, packet capturing was not started on a specified interface at all or could get started on a incorrect interface. With this update, the argument for "-i" is treated as a number only if it contains only numerals 0-9; otherwise, the argument is treated as a string. For example, interface names such as "192_1_2" are no longer treated as interface number 192, but as a string. As a result, tcpdump starts correctly on a specified interface even if the interface name contains a numeric prefix. BZ# 1130111 The tcpdump Cisco Discovery Protocol (CDP) dissector previously stopped parsing packet prematurely after encountering Type-Length-Value (TLV) field which had the length of 0 and no data associated with it. Consequently, some CDP packets were not completely dissected. A patch which alters code deciding when to stop parsing the packet has been applied to fix this bug. Now, zero length data TLVs are allowed, and CDP packets containing such TLVs are parsed correctly. Enhancements BZ# 1045601 The kernel, glibc, and libpcap utilities now provide APIs to obtain nanosecond resolutions timestamps. The user can thus query which timestamp sources are available ("-J"), set a specific timestamp source ("-j"), and request timestamps with a specified resolution ("--time-stamp-precision"). BZ# 1099701 This update adds the new "-P" command-line argument for capturing packets in certain direction, which can ease debugging networking-related problems. Users of tcpdump are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
4.10. Detaching the Disks for the Image Creation Process Now that the disks have been set up, they must be detached from the VM instances so that they can be used for the step. The VM instance is deleted in the process. In the Google Developers Console, click Compute > Compute Engine > VM instances > rhgs-primary-n01 . Scroll down to the Disks section (there should be one for the boot disk and one for the additional disks). Ensure that the checkbox delete boot disk when instance is deleted is unchecked and the option for When deleting instance is selected the additional disk shows Keep disk . Now, click Delete on the top to delete the VM instance.

Commands:
function::str_replace Name function::str_replace - str_replace Replaces all instances of a substring with another Synopsis Arguments prnt_str the string to search and replace in srch_str the substring which is used to search in prnt_str string rplc_str the substring which is used to replace srch_str Description This function returns the given string with substrings replaced.

Commands:
str_replace:string(prnt_str:string,srch_str:string,rplc_str:string)
Chapter 3. Red Hat build of OpenJDK 8.0.412 release notes The latest Red Hat build of OpenJDK 8 release might include new features. Additionally, the latest release might enhance, deprecate, or remove features that originated from Red Hat build of OpenJDK 8 releases. Note For all the other changes and security fixes, see OpenJDK 8u412 Released . Red Hat build of OpenJDK new features and enhancements Review the following release notes to understand new features and feature enhancements that Red Hat build of OpenJDK 8.0.412 provides: Kerberos 5 replay cache interoperability with MIT krb5-1.15 In Red Hat build of OpenJDK 8.0.412, the Kerberos 5 replay cache file ( rcache ) uses the SHA256 algorithm. This supersedes the behavior in releases where rcache used the MD5 algorithm. The Massachusetts Institute of Technology (MIT) Kerberos 5 Release 1.15 (krb5-1.15) also uses the SHA256 algorithm, which is interoperable with earlier releases of MIT krb5. If you want to continue using the MD5 algorithm, ensure that the new system property jdk.krb5.rcache.useMD5 is set to true . The MD5 algorithm is useful in the following situations: If your system has a coarse clock and depends on hash values in replay attack detection If your system needs to interoperate with the rcache files in older OpenJDK releases See JDK-8168518 (JDK Bug System) . SystemTray.isSupported() method returns false on most Linux desktops In Red Hat build of OpenJDK 8.0.412, the java.awt.SystemTray.isSupported() method returns false on systems that do not support the SystemTray API correctly. This enhancement is in accordance with the SystemTray API specification. The SystemTray API is used to interact with the taskbar in the system desktop to provide notifications. SystemTray might also include an icon representing an application. Due to an underlying platform issue, GNOME desktop support for taskbar icons has not worked correctly for several years. This platform issue affects the JDK's ability to provide SystemTray support on GNOME desktops. This issue typically affects systems that use GNOME Shell 44 or earlier. Note Because the lack of correct SystemTray support is a long-standing issue on some systems, this API enhancement to return false on affected systems is likely to have a minimal impact on users. See JDK-8322750 (JDK Bug System) . Certainly R1 and E1 root certificates added In Red Hat build of OpenJDK 8.0.412, the cacerts truststore includes two Certainly root certificates: Certificate 1 Name: Certainly Alias name: certainlyrootr1 Distinguished name: CN=Certainly Root R1, O=Certainly, C=US Certificate 2 Name: Certainly Alias name: certainlyroote1 Distinguished name: CN=Certainly Root E1, O=Certainly, C=US See JDK-8321408 (JDK Bug System) .

Commands:
14.5.15. Using blockcommit to Shorten a Backing Chain This section demonstrates how to use virsh blockcommit to shorten a backing chain. For more background on backing chains, see Section 14.5.18, "Disk Image Management with Live Block Copy" . blockcommit copies data from one part of the chain down into a backing file, allowing you to pivot the rest of the chain in order to bypass the committed portions. For example, suppose this is the current state: Using blockcommit moves the contents of snap2 into snap1, allowing you to delete snap2 from the chain, making backups much quicker. Procedure 14.2. virsh blockcommit Run the following command: The contents of snap2 are moved into snap1, resulting in: base <- snap1 <- active . Snap2 is no longer valid and can be deleted Warning blockcommit will corrupt any file that depends on the -base option (other than files that depend on the -top option, as those files now point to the base). To prevent this, do not commit changes into files shared by more than one guest. The -verbose option allows the progress to be printed on the screen.

Commands:
base <- snap1 <- snap2 <- active .
virsh blockcommit USDdom USDdisk -base snap1 -top snap2 -wait -verbose
Chapter 3. Recreating the fapolicyd trust files when updating SAP HANA Prerequisites The fapolicyd package is installed on your system. You have verified that there are no new executables in the SAP HANA software directories, so you do not accidentally add software from unknown sources. For more information, refer to Marking the SAP HANA files as trusted . Procedure Stop fapolicyd before performing the SAP HANA software update: Create a backup of the existing fapolicyd trust files /etc/fapolicyd/trust.d/hana and /etc/fapolicyd/trust.d/usr_sap , and then remove these files. Perform the SAP HANA software update. Repeat procedure section's step 2 of Marking the SAP HANA files as trusted , to recreate the fapolicyd trust files for SAP HANA. Start fapolicyd :

Commands:
systemctl stop fapolicyd
systemctl start fapolicyd
Appendix A. Troubleshooting: General Guidelines This appendix describes general steps for determining the root cause of a problem, for example by querying logs and service statuses. Note For lists of specific problems and their solutions, see Appendix B, Troubleshooting: Solutions to Specific Problems . What were you doing when you encountered the problem? Executing a command using the ipa utility Authenticating Using kinit Authenticating to the IdM web UI Authenticating with a Smart Card Starting a Service If you know which specific area of IdM is causing the problem, follow these links: DNS Replication If this guide does not help you find and fix the problem and you proceed to file a customer case, include any notable error output that you determined using these troubleshooting procedures in the case report. See also Contacting Red Hat Technical Support . A.1. Investigating Failures when Executing the ipa Utility Basic Troubleshooting Add the --verbose ( -v ) option to the command. This displays debug information. Add the -vv option to the command. This displays the JSON response and request. Advanced Troubleshooting Figure A.1, "The architecture of executing the ipa cert-show command" shows which components interact when the user uses the IdM command-line utility. Querying these components can help you investigate where the problem occurred and what caused it. Use the following utilities: host to check the DNS resolution of the IdM server or client ping to check if the IdM server is available iptables to check the current firewall configuration on the IdM server date to check the current time nc to try to connect to the required ports, as listed in Section 2.1.6, "Port Requirements" For details on using these utilities, see their man pages. Set the KRB5_TRACE environment variable to the /dev/stdout file to send trace-logging output to /dev/stdout : Review the Kerberos key distribution center (KDC) log: /var/log/krb5kdc.log . Review the Apache error log: Enable debug level on the server: Open the /etc/ipa/server.conf file, and add the debug=True option to the [global] section. Restart the httpd service: Run the command that failed again. Review the httpd error log on the server: /var/log/httpd/error_log . Run the command with the -vvv option to display the HTTP request and response. Review the Apache access log: /var/log/httpd/access_log . Review the logs for the Certificate System component: /var/log/pki/pki-ca-spawn. time_of_installation .log /var/log/pki/pki-tomcat/ca/debug /var/log/pki/pki-tomcat/ca/system /var/log/pki/pki-tomcat/ca/selftests.log Use the # journalctl -u pki-tomcatd@pki-tomcat.service command to review the journal log. Review the Directory Server access log: /var/log/dirsrv/slapd- IPA-EXAMPLE-COM /access . Figure A.1. The architecture of executing the ipa cert-show command Related Information See Section C.2, "Identity Management Log Files and Directories" for descriptions of various Identity Management log files.

Commands:
KRB5_TRACE=/dev/stdout ipa cert-find
systemctl restart httpd.service
B.82. rsync B.82.1. RHSA-2011:0390 - Moderate: rsync security update An updated rsync package that fixes one security issue is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A 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. rsync is a program for synchronizing files over a network. CVE-2011-1097 A memory corruption flaw was found in the way the rsync client processed malformed file list data. If an rsync client used the "--recursive" and "--delete" options without the "--owner" option when connecting to a malicious rsync server, the malicious server could cause rsync on the client system to crash or, possibly, execute arbitrary code with the privileges of the user running rsync. Red Hat would like to thank Wayne Davison and Matt McCutchen for reporting this issue. Users of rsync should upgrade to this updated package, which contains a backported patch to resolve this issue.

Commands:
Chapter 1. Overview Note The Ruby software development kit (SDK) is deprecated. Support for Ruby SDK will be removed in a later release. The Ruby software development kit is a Ruby gem that allows you to interact with the Red Hat Virtualization Manager in Ruby projects. By downloading these classes and adding them to your project, you can access a range of functionality for high-level automation of administrative tasks. 1.1. Prerequisites To install the Ruby software development kit, you must have: A system with Red Hat Enterprise Linux 8 installed. Both the Server and Workstation variants are supported. A subscription to Red Hat Virtualization entitlements.

Commands:
Chapter 23. KafkaAuthorizationKeycloak schema reference Used in: KafkaClusterSpec The type property is a discriminator that distinguishes use of the KafkaAuthorizationKeycloak type from KafkaAuthorizationSimple , KafkaAuthorizationOpa , KafkaAuthorizationCustom . It must have the value keycloak for the type KafkaAuthorizationKeycloak . Property Property type Description type string Must be keycloak . clientId string OAuth Client ID which the Kafka client can use to authenticate against the OAuth server and use the token endpoint URI. tokenEndpointUri string Authorization server token endpoint URI. tlsTrustedCertificates CertSecretSource array Trusted certificates for TLS connection to the OAuth server. disableTlsHostnameVerification boolean Enable or disable TLS hostname verification. Default value is false . delegateToKafkaAcls boolean Whether authorization decision should be delegated to the 'Simple' authorizer if DENIED by Red Hat build of Keycloak Authorization Services policies. Default value is false . grantsRefreshPeriodSeconds integer The time between two consecutive grants refresh runs in seconds. The default value is 60. grantsRefreshPoolSize integer The number of threads to use to refresh grants for active sessions. The more threads, the more parallelism, so the sooner the job completes. However, using more threads places a heavier load on the authorization server. The default value is 5. grantsMaxIdleTimeSeconds integer The time, in seconds, after which an idle grant can be evicted from the cache. The default value is 300. grantsGcPeriodSeconds integer The time, in seconds, between consecutive runs of a job that cleans stale grants from the cache. The default value is 300. grantsAlwaysLatest boolean Controls whether the latest grants are fetched for a new session. When enabled, grants are retrieved from Red Hat build of Keycloak and cached for the user. The default value is false . superUsers string array List of super users. Should contain list of user principals which should get unlimited access rights. connectTimeoutSeconds integer The connect timeout in seconds when connecting to authorization server. If not set, the effective connect timeout is 60 seconds. readTimeoutSeconds integer The read timeout in seconds when connecting to authorization server. If not set, the effective read timeout is 60 seconds. httpRetries integer The maximum number of retries to attempt if an initial HTTP request fails. If not set, the default is to not attempt any retries. enableMetrics boolean Enable or disable OAuth metrics. The default value is false . includeAcceptHeader boolean Whether the Accept header should be set in requests to the authorization servers. The default value is true .

Commands:
6.4.2.2. Adding the New Physical Volume to the Volume Group Add /dev/sdd1 to the existing volume group myvg .

Commands:
vgextend myvg /dev/sdd1 Volume group "myvg" successfully extended pvs -o+pv_used PV VG Fmt Attr PSize PFree Used /dev/sda1 myvg lvm2 a- 17.15G 7.15G 10.00G /dev/sdb1 myvg lvm2 a- 17.15G 15.15G 2.00G /dev/sdc1 myvg lvm2 a- 17.15G 15.15G 2.00G /dev/sdd1 myvg lvm2 a- 17.15G 17.15G 0
Appendix D. Proficiency levels Each available example teaches concepts that require certain minimum knowledge. This requirement varies by example. The minimum requirements and concepts are organized in several levels of proficiency. In addition to the levels described here, you might need additional information specific to each example. Foundational The examples rated at Foundational proficiency generally require no prior knowledge of the subject matter; they provide general awareness and demonstration of key elements, concepts, and terminology. There are no special requirements except those directly mentioned in the description of the example. Advanced When using Advanced examples, the assumption is that you are familiar with the common concepts and terminology of the subject area of the example in addition to Kubernetes and OpenShift. You must also be able to perform basic tasks on your own, for example, configuring services and applications, or administering networks. If a service is needed by the example, but configuring it is not in the scope of the example, the assumption is that you have the knowledge to properly configure it, and only the resulting state of the service is described in the documentation. Expert Expert examples require the highest level of knowledge of the subject matter. You are expected to perform many tasks based on feature-based documentation and manuals, and the documentation is aimed at most complex scenarios.

Commands:
3.4. Example: List Logical Networks Collection Red Hat Virtualization Manager creates a default ovirtmgmt network on installation. This network acts as the management network for Red Hat Virtualization Manager to access hosts. This network is associated with our Default cluster and is a member of the Default data center. This example uses the ovirtmgmt network to connect our virtual machines. The following request retrieves a representation of the logical networks collection: Example 3.4. List logical networks collection Request: cURL command: Result: The ovirtmgmt network is attached to the Default data center through a relationship using the data center's id code. The ovirtmgmt network is also attached to the Default cluster through a relationship in the cluster's network sub-collection.

Commands:
GET /ovirt-engine/api/networks HTTP/1.1 Accept: application/xml
curl -X GET -H "Accept: application/xml" -u [USER:PASS] --cacert [CERT] https:// [RHEVM Host] :443/ovirt-engine/api/networks
HTTP/1.1 200 OK Content-Type: application/xml <networks> <network id="00000000-0000-0000-0000-000000000009" href="/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000009"> <name>ovirtmgmt</name> <description>Management Network</description> <data_center id="01a45ff0-915a-11e0-8b87-5254004ac988" href="/ovirt-engine/api/datacenters/01a45ff0-915a-11e0-8b87-5254004ac988"/> <stp>false</stp> <status> <state>operational</state> </status> <display>false</display> </network> </networks>