mtpti5iD/redhat-docs_dataset huggingface dataset:
B.17.2.3. Opening and ending tag mismatch Symptom The following error occurs: Investigation The error message above contains three clues to identify the offending tag: The message following the last colon, clock line 16 and domain , reveals that <clock> contains a mismatched tag on line 16 of the document. The last hint is the pointer in the context part of the message, which identifies the second offending tag. Unpaired tags must be closed with /> . The following snippet does not follow this rule and has produced the error message shown above: This error is caused by mismatched XML tags in the file. Every XML tag must have a matching start and end tag. Other examples of mismatched XML tags The following examples produce similar error messages and show variations of mismatched XML tags. This snippet contains an unended pair tag for <features> : This snippet contains an end tag ( </name> ) without a corresponding start tag: Solution Ensure all XML tags start and end correctly.

Commands:
error: ( name_of_guest.xml ):61: Opening and ending tag mismatch: clock line 16 and domain </domain> ---------^
<domain type='kvm'> <clock offset='utc'>
<domain type='kvm'> <features> <acpi/> <pae/> </domain>
<domain type='kvm'> </name> </domain>
Deploying and managing OpenShift Container Storage using Red Hat OpenStack Platform Red Hat OpenShift Container Storage 4.8 How to install and manage Red Hat Storage Documentation Team Abstract Read this document for instructions on installing and managing Red Hat OpenShift Container Storage on Red Hat OpenStack Platform (RHOSP). Important Deploying and managing OpenShift Container Storage on Red Hat OpenStack Platform is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Commands:
29.2. The TCPGOSSIP JGroups Protocol The TCPGOSSIP discovery protocol uses one or more configured GossipRouter processes to store information about the nodes in the cluster. Important It is vital that the GossipRouter process consistently be available to all nodes in the cluster, as without this process it will not be possible to add additional nodes. For this reason it is strongly recommended to deploy this process in a highly available method; for example, an Availability Set with multiple virtual machines may be used. Running the GossipRouter The GossipRouter is included in the JGroups jar file, and must be running before any nodes are started. This process may be started by pointing to the GossipRouter class in the JGroups jar file included with JBoss Data Grid: In the event that multiple GossipRouters are available, and specified, a node will always register with all specified GossipRouters; however, it will only retrieve information from the first available GossipRouter. If a GossipRouter is unavailable it will be marked as failed and removed from the list, with a background thread started to periodically attempt reconnecting to the failed GossipRouter. Once the thread successfully reconnects the GossipRouter will be reinserted into the list. Configuring JBoss Data Grid to use TCPGOSSIP (Library Mode) In Library Mode the JGroups xml file should be used to configure TCPGOSSIP ; however, there is no TCPGOSSIP configuration included by default. It is recommended to use one of the preexisting files specified in Section 26.2.2, "Pre-Configured JGroups Files" and then adjust the configuration to include TCPGOSSIP . For instance, default-configs/default-jgroups-ec2.xml could be selected and the S3_PING protocol removed, and then the following block added in its place: Configuring JBoss Data Grid to use TCPGOSSIP (Remote Client-Server Mode) In Remote Client-Server Mode a stack may be defined for TCPGOSSIP in the jgroups subsystem of the server's configuration file. The following configuration snippet contains an example of this: Report a bug

Commands:
java -classpath jgroups-USD{jgroups.version}.jar org.jgroups.stack.GossipRouter -bindaddress IP_ADDRESS -port PORT
<TCPGOSSIP initial_hosts="IP_ADDRESS_0[PORT_0],IP_ADDRESS_1[PORT_1]" />
<subsystem xmlns="urn:infinispan:server:jgroups:6.1" default-stack="USD{jboss.default.jgroups.stack:tcpgossip}"> [...] <stack name="jdbc_ping"> <transport type="TCP" socket-binding="jgroups-tcp"/> <protocol type="TCPGOSSIP"> <property name="initial_hosts">IP_ADDRESS_0[PORT_0],IP_ADDRESS_1[PORT_1]</property> </protocol> <protocol type="MERGE3"/> <protocol type="FD_SOCK" socket-binding="jgroups-tcp-fd"/> <protocol type="FD_ALL"/> <protocol type="VERIFY_SUSPECT"/> <protocol type="pbcast.NAKACK2"> <property name="use_mcast_xmit">false</property> </protocol> <protocol type="UNICAST3"/> <protocol type="pbcast.STABLE"/> <protocol type="pbcast.GMS"/> <protocol type="MFC"/> <protocol type="FRAG2"/> </stack> [...] </subsystem>
Chapter 16. Installing and configuring RH-SSO A realm is a security policy domain defined for a web or application server. Security realms are used to restrict access for different application resources. You should create a new realm whether your RH-SSO instance is private or shared with other products. You can keep the master realm as a place for super administrators to create and manage the realms in your system. If you are integrating with an RH-SSO instance that is shared with other product installations to achieve single sign-on with those applications, all of those applications must use the same realm. To create an RH-SSO realm, download, install, and configure RH-SSO 7.5. Note If Business Central and KIE Server are installed on different servers, complete this procedure on both servers. Procedure Navigate to the Software Downloads page in the Red Hat Customer Portal (login required) and then select the product and version from the drop-down options: Product: Red Hat Single Sign-On Version: 7.5 Download Red Hat Single Sign-On 7.5.0 Server ( rh-sso-7.5.0.zip ) and the latest server patch. To install and configure a basic RH-SSO standalone server, follow the instructions in the Red Hat Single Sign On Getting Started Guide . For advanced settings for production environments, see the Red Hat Single Sign On Server Administration Guide . Note If you want to run both RH-SSO and Red Hat Process Automation Manager servers on the same system, ensure that you avoid port conflicts by taking one of the following actions: Update the RHSSO_HOME /standalone/configuration/standalone-full.xml file and set the port offset to 100. For example: Use an environment variable to set the port offset when running the server:

Commands:
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="USD{jboss.socket.binding.port-offset:100}">
bin/standalone.sh -Djboss.socket.binding.port-offset=100
Chapter 1. Supported platforms This section describes the availability and the supported installation methods of CodeReady Workspaces 2.15 on OpenShift Container Platform 4.10 4.8, 3.11, and OpenShift Dedicated. Table 1.1. Supported deployment environments for CodeReady Workspaces 2.15 on OpenShift Container Platform and OpenShift Dedicated Platform Architecture Deployment method OpenShift Container Platform 3.11 AMD64 and Intel 64 (x86_64) crwctl OpenShift Container Platform 4.8 to 4.10 AMD64 and Intel 64 (x86_64) OperatorHub, crwctl OpenShift Container Platform 4.8 to 4.10 IBM Z (s390x) OperatorHub, crwctl OpenShift Container Platform 4.8 to 4.10 IBM Power (ppc64le) OperatorHub, crwctl OpenShift Dedicated 4.10 AMD64 and Intel 64 (x86_64) Add-on service Red Hat OpenShift Service on AWS (ROSA) AMD64 and Intel 64 (x86_64) Add-on service

Commands:
Chapter 3. Deprecated functionalities This section lists deprecated functionalities in Red Hat Developer Hub 1.4. 3.1. ./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic plugin is deprecated The ./dynamic-plugins/dist/janus-idp-backstage-plugin-aap-backend-dynamic plugin has been deprecated and will be removed in the release. You can use Ansible plug-ins for Red Hat Developer Hub instead. Additional resources RHIDP-3545 3.2. Audit log rotation is deprecated With this update, you can evaluate your platform's log forwarding solutions to align with your security and compliance needs. Most of these solutions offer configurable options to minimize the loss of logs in the event of an outage. Additional resources RHIDP-4913 3.3. Red Hat Single-Sign On 7.6 is deprecated as an authentication provider Red Hat Single-Sign On (RHSSO) 7.6 is deprecated as an authentication provider. You can continue to use RHSSO until the end of maintenance support. For details, see RHSSO lifecycle dates . As an alternative, migrate to Red Hat Build of Keycloak v24 . Additional resources RHIDP-5218

Commands:
16.5.2. Configuring a DHCPv6 Client The default configuration of the DHCPv6 client works fine in the most cases. However, to configure a DHCP client manually, create and modify the /etc/dhcp/dhclient.conf file. See the /usr/share/doc/dhclient-4.1.1/dhclient6.conf.sample for a client configuration file example. For advanced configurations of DHCPv6 client options such as protocol timing, lease requirements and requests, dynamic DNS support, aliases, as well as a wide variety of values to override, prepend, or append to client-side configurations, see the dhclient.conf(5) man page and the STANDARD DHCPV6 OPTIONS section in the dhcpd-options(5) man page. Important In Red Hat Enterprise Linux 6, a DHCPv6 client is correctly handled only by NetworkManager and should not generally be run separately. That is because DHCPv6, unlike DHCPv4, is not a standalone network configuration protocol but is always supposed to be used together with router discovery.

Commands:
7.103. libdrm 7.103.1. RHBA-2015:1301 - libdrm, mesa, xorg-x11-drv-ati, and xorg-x11-drv-intel update Updated libdrm, mesa, xorg-x11-drv-ati, and xorg-x11-drv-intel packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libdrm packages comprise a runtime library for the Direct Rendering Manager. Mesa provides a 3D graphics API that is compatible with Open Graphics Library (OpenGL) and hardware-accelerated drivers for many popular graphics chips. The xorg-x11-drv-ati packages include a driver for ATI graphics cards for the X.Org implementation of the X Window System. The xorg-x11-drv-intel packages contain an Intel integrated graphics video driver for the X.Org implementation of the X Window System. Note The libdrm packages have been upgraded to upstream version 2.4.59, which provides a number of bug fixes and enhancements over the version. (BZ# 1186821 ) * The mesa packages have been upgraded to upstream version 10.4.3, which provides a number of bug fixes and enhancements over the version. Among other changes, this version includes support for new Intel 3D graphic chip sets. (BZ# 1032663 ) * Support for new Intel 3D graphic chip sets has been backported to the xorg-x11-drv-intel packages. * The xorg-x11-drv-ati packages have been upgraded to upstream version 7.5.99, which contains a number of bug fixes and enhancements over the version. Among other changes, this version includes support for new AMD 3D graphic chip sets. (BZ# 1176666 ) Bug Fixes BZ# 1186821 The libdrm packages have been upgraded to upstream version 2.4.59, which provides a number of bug fixes and enhancements over the version. BZ# 1032663 The mesa packages have been upgraded to upstream version 10.4.3, which provides a number of bug fixes and enhancements over the version. Among other changes, this version includes support for new Intel 3D graphic chip sets. BZ# 1176666 Support for new Intel 3D graphic chip sets has been backported to the xorg-x11-drv-intel packages. * The xorg-x11-drv-ati packages have been upgraded to upstream version 7.5.99, which contains a number of bug fixes and enhancements over the version. Among other changes, this version includes support for new AMD 3D graphic chip sets. BZ# 1084104 Previously, the radeon driver did not work correctly with the Virtual Network Computing (VNC) module if hardware acceleration was enabled. Consequently, a VNC client connected to a computer set up this way only displayed a blank screen. With this update, this problem has been resolved, and it is now possible to use VNC with the aforementioned setup. Users of libdrm, mesa, xorg-x11-drv-ati, and xorg-x11-drv-intel are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Appendix A. Technical Users Provided and Required by Satellite During the installation of Satellite, system accounts are created. They are used to manage files and process ownership of the components integrated into Satellite. Some of these accounts have fixed UIDs and GIDs, while others take the available UID and GID on the system instead. To control the UIDs and GIDs assigned to accounts, you can define accounts before installing Satellite. Because some of the accounts have hard-coded UIDs and GIDs, it is not possible to do this with all accounts created during Satellite installation. The following table lists all the accounts created by Satellite during installation. You can predefine accounts that have Yes in the Flexible UID and GID column with custom UID and GID before installing Satellite. Do not change the home and shell directories of system accounts because they are requirements for Satellite to work correctly. Because of potential conflicts with local users that Satellite creates, you cannot use external identity providers for the system users of the Satellite base operating system. Table A.1. Technical Users Provided and Required by Satellite User name UID Group name GID Flexible UID and GID Home Shell foreman N/A foreman N/A yes /usr/share/foreman /sbin/nologin foreman-proxy N/A foreman-proxy N/A yes /usr/share/foreman-proxy /sbin/nologin puppet N/A puppet N/A yes /opt/puppetlabs/server/data/puppetserver /sbin/nologin qdrouterd N/A qdrouterd N/A yes N/A /sbin/nologin qpidd N/A qpidd N/A yes /var/lib/qpidd /sbin/nologin unbound N/A unbound N/A yes /etc/unbound /sbin/nologin postgres 26 postgres 26 no /var/lib/pgsql /bin/bash apache 48 apache 48 no /usr/share/httpd /sbin/nologin tomcat 53 tomcat 53 no /usr/share/tomcat /bin/nologin saslauth N/A saslauth 76 no N/A /sbin/nologin

Commands:
B.34. java-1.6.0-sun B.34.1. RHSA-2011:0282 - Critical: java-1.6.0-sun security update Updated java-1.6.0-sun packages that fix several security issues are now available for Red Hat Enterprise Linux 4 Extras, and Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The Sun 1.6.0 Java release includes the Sun Java 6 Runtime Environment and the Sun Java 6 Software Development Kit. CVE-2010-4422 , CVE-2010-4447 , CVE-2010-4448 , CVE-2010-4450 , CVE-2010-4451 , CVE-2010-4452 , CVE-2010-4454 , CVE-2010-4462 , CVE-2010-4463 , CVE-2010-4465 , CVE-2010-4466 , CVE-2010-4467 , CVE-2010-4468 , CVE-2010-4469 , CVE-2010-4470 , CVE-2010-4471 , CVE-2010-4472 , CVE-2010-4473 , CVE-2010-4475 , CVE-2010-4476 This update fixes several vulnerabilities in the Sun Java 6 Runtime Environment and the Sun Java 6 Software Development Kit. Further information about these flaws can be found on the Oracle Java SE and Java for Business Critical Patch Update Advisory page. All users of java-1.6.0-sun are advised to upgrade to these updated packages, which resolve these issues. All running instances of Sun Java must be restarted for the update to take effect.

Commands:
Chapter 2. Before You Begin 2.1. Update the target server The target server contains the JBoss EAP Migration Tool and includes the latest bug fixes for the tool. You can use the JBoss EAP Migration Tool to migrate from one minor release of JBoss EAP to another minor release. Before the migration process, you must ensure the JBoss EAP Migration Tool receives the latest JBoss EAP updates to prevent re-introducing bugs that might already be fixed for the tool. You can update the tool by applying the latest JBoss EAP updates to the target server. For example, if you want to migrate your existing source server configuration from JBoss EAP 6.4 to JBoss EAP 7.4 then you must apply the latest JBoss EAP Migration Tool updates to JBoss EAP 7.4 before you can run the tool. Otherwise, after you migrate from JBoss EAP 6.4 to JBoss EAP 7.4, you might introduce issues to the new source server configuration. Note Releases before JBoss EAP 6.4 do not support the JBoss EAP Migration Tool. If you want to use the tool with JBoss EAP 6.4 then you must upgrade to JBoss EAP 6.4. Further, you must copy the source configuration files from JBoss EAP 6.0 to JBoss EAP 6.4. Additional resources For information about how to upgrade your server configuration, see the Patching and Upgrading Guide for JBoss EAP. 2.2. Run With a Clean Target Server Installation Because the JBoss Server Migration Tool creates the configuration files based on the configuration of a release, it is intended to be run on a clean and unconfigured target server installation. The JBoss Server Migration Tool creates a backup of the target server's configuration files by appending .beforeMigration to the file names. It then creates totally new configuration files for the target server using the source server's configuration files, and migrates the configuration to run in target server configuration. Warning When you run the JBoss Server Migration Tool, all changes on the target server made between installation and running the migrate tool are lost. Also, be aware that if you run the tool against the target server directory more than once, the subsequent runs will overwrite the original target configuration files that were backed up on the first run of the tool. This is because each run of the tool backs up the configuration files by appending .beforeMigration , resulting in the loss of any existing backed up configuration files. 2.3. Customize the Migration The JBoss Server Migration Tool provides the ability to configure logging, reporting, and the execution of migration tasks. By default, when you run the JBoss Server Migration Tool in non-interactive mode, it migrates the entire server configuration. You can configure the JBoss Server Migration Tool to customize logging and reporting output. You can also configure it to skip any part of the configuration that you do not want to migrate. For instructions on how to configure properties to control the migration process, see Configuring the JBoss Server Migration Tool .

Commands:
Chapter 65. ListenerStatus schema reference Used in: KafkaStatus Property Description type The type property has been deprecated, and should now be configured using name . The name of the listener. string name The name of the listener. string addresses A list of the addresses for this listener. ListenerAddress array bootstrapServers A comma-separated list of host:port pairs for connecting to the Kafka cluster using this listener. string certificates A list of TLS certificates which can be used to verify the identity of the server when connecting to the given listener. Set only for tls and external listeners. string array

Commands:
Providing feedback on Red Hat documentation We appreciate your input on our documentation. Do let us know how we can make it better. To give feedback: For simple comments on specific passages: Make sure you are viewing the documentation in the HTML format. In addition, ensure you see the Feedback button in the upper right corner of the document. Use your mouse cursor to highlight the part of text that you want to comment on. Click the Add Feedback pop-up that appears below the highlighted text. Follow the displayed instructions. For submitting more complex feedback, create a Bugzilla ticket: Go to the Bugzilla website. In the Component section, choose documentation . Fill in the Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation. Click Submit Bug . Red Hat OpenShift Data Foundation 4.9 supports deployment of Red Hat OpenShift on IBM Cloud clusters in connected environments.

Commands:
7.10. RHEA-2014:1519 - new package: ksc A new ksc package is now available for Red Hat Enterprise Linux 6. The ksc package contains KSC, a kernel module source code checker to find usage of non-whitelist symbols. This enhancement update adds the ksc package to Red Hat Enterprise Linux 6. (BZ# 1085004 ) All users who require ksc are advised to install this new package.

Commands:
Chapter 3. Updating Red Hat build of OpenJDK 21 for Microsoft Windows using the archive Red Hat build of OpenJDK 21 for Microsoft Windows can be manually updated using the archive. Procedure Download the archive of Red Hat build of OpenJDK 21. Extract the contents of an archive to a directory of your choice. Note Extracting the contents of an archive to a directory path that does not contain spaces is recommended. On Command Prompt, update JAVA_HOME environment variable as follows: Open Command Prompt as an administrator. Set the value of the environment variable to your Red Hat build of OpenJDK 21 for Microsoft Windows installation path: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables. Set the value of PATH variable if it is not set already: Restart Command Prompt to reload the environment variables. Verify that java -version works without supplying the full path.

Commands:
C:\> setx /m JAVA_HOME "C:\Progra~1\RedHat\java-21-openjdk-<version>"
C:\> setx -m PATH "%PATH%;%JAVA_HOME%\bin";
C:\> java -version
7.106. ksh 7.106.1. RHBA-2013:0430 - ksh bug fix and enhancement update Updated ksh packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. KSH-93 is the most recent version of the KornShell by David Korn of AT&T Bell Laboratories. KornShell is a shell programming language which is also compatible with sh, the original Bourne Shell. Bug Fixes BZ#827512 Originally, ksh buffered output of a subshell, flushing it when the subshell completed. This slowed certain processes that waited for a particular output, because they had to wait for the subshell to complete. Moreover, it made it difficult to determine the order of events. The new version of ksh flushes output of the subshell every time the subshell executes a new command. Thanks to this change, processes waiting for the subshell output receive their data after every subshell command and the order of events is preserved. BZ#846663 Previously, the sfprints() function was unsafe to be called during the shell initialization, which could corrupt the memory. Consequently, assigning a right-aligned variable to a smaller size could result in inappropriate output format. With this update, the sfprints() call is no longer used in the described scenario, which fixes the format of the output. BZ#846678 Due to a bug in the typeset command, when executed with the -Z option, output was being formatted to an incorrect width. As a result, exporting a right-aligned variable of a smaller size than the predefined field size caused it to not be prepended with the "0" character. A patch has been provided and the typeset command now works as expected in the aforementioned scenario. Enhancement BZ#869155 With this update, ksh has been enhanced to support logging of the shell output. Users of ksh are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
2.3. Checking the Status of NetworkManager To check whether NetworkManager is running: Note that the systemctl status command displays Active: inactive (dead) when NetworkManager is not running.

Commands:
~]USD systemctl status NetworkManager NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Fri, 08 Mar 2013 12:50:04 +0100; 3 days ago