mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix A. Reference material A.1. Additional resources A.1.1. Contributing to the project To help the Migration Toolkit for Runtimes cover most application constructs and server configurations, including yours, you can help with any of the following items: Send an email to jboss-migration-feedback@redhat.com and let us know what MTR migration rules must cover. Provide example applications to test migration rules. Identify application components and problem areas that might be difficult to migrate: Write a short description of the problem migration areas. Write a brief overview describing how to solve the problem in migration areas. Try Migration Toolkit for Runtimes on your application. Make sure to report any issues you meet. Contribute to the Migration Toolkit for Runtimes rules repository: Write a Migration Toolkit for Runtimes rule to identify or automate a migration process. Create a test for the new rule. For more information, see Rule Development Guide . Contribute to the project source code: Create a core rule. Improve MTR performance or efficiency. Any level of involvement is greatly appreciated! A.1.2. Migration Toolkit for Runtimes development resources Use the following resources to learn and contribute to the Migration Toolkit for Runtimes development: MTR forums: https://developer.jboss.org/en/windup Jira issue tracker: https://issues.redhat.com/projects/WINDUP MTR mailing list: jboss-migration-feedback@redhat.com A.1.3. Reporting issues MTR uses Jira as its issue tracking system. If you encounter an issue executing MTR, submit a Jira issue . Revised on 2024-09-12 13:52:31 UTC

Commands:
5.3.4. Assign Static Ports and Use IPTables Rules All of the servers related to NIS can be assigned specific ports except for rpc.yppasswdd - the daemon that allows users to change their login passwords. Assigning ports to the other two NIS server daemons, rpc.ypxfrd and ypserv , allows for the creation of firewall rules to further protect the NIS server daemons from intruders. To do this, add the following lines to /etc/sysconfig/network : The following IPTables rules can be issued to enforce which network the server listens to for these ports: Note Refer to Chapter 7, Firewalls for more information about implementing firewalls with IPTables commands.

Commands:
YPSERV_ARGS="-p 834" YPXFRD_ARGS="-p 835"
iptables -A INPUT -p ALL -s! 192.168.0.0/24 --dport 834 -j DROP iptables -A INPUT -p ALL -s! 192.168.0.0/24 --dport 835 -j DROP
4.47. dmidecode 4.47.1. RHEA-2011:1555 - dmidecode bug fix and enhancement update An updated dmidecode package that fixes one bug and adds one enhancement is now available for Red Hat Enterprise Linux 6. The dmidecode package provides utilities for extracting x86 and Intel Itanium hardware information from the system BIOS or EFI (Extensible Firmware Interface), depending on the SMBIOS/DMI standard. This information typically includes system manufacturer, model name, serial number, BIOS version, and asset tag as well as other details, depending on the manufacturer. This often includes usage status for the CPU sockets, expansion slots such as AGP, PCI and ISA, among others, memory module slots, and many different kinds of I/O ports, such as serial, parallel and USB. Prior to this update, the extended records for the DMI types Memory Device (DMI type 17) and Memory Array Mapped Address (DMI type 19) were missing from the dmidecode utility output. With this update, dmidecode has been upgraded to upstream version 2.11, which updates support for the SMBIOS specification to version 2.7.1, thus fixing this bug. Now, the dmidecode output contains the extended records for DMI type 17 and DMI type 19. (BZ# 654833 ) All users of dmidecode are advised to upgrade to this updated package, which fixes this bug and adds this enhancement.

Commands:
probe::socket.sendmsg.return Name probe::socket.sendmsg.return - Return from socket.sendmsg. Synopsis Values success Was send successful? (1 = yes, 0 = no) protocol Protocol value flags Socket flags value name Name of this probe state Socket state value size Size of message sent (in bytes) or error code if success = 0 type Socket type value family Protocol family value Context The message sender. Description Fires at the conclusion of sending a message on a socket via the sock_sendmsg function

Commands:
socket.sendmsg.return
4.201. nss_db 4.201.1. RHBA-2012:0346 - nss_db bug fix update An updated nss_db package that fixes one bug is now available for Red Hat Enterprise Linux 6. The nss_db package contains a set of C library extensions, such as the Name Service Switch (nsswitch) module, which allow Berkeley Databases to be used as a primary source of aliases, groups, hosts, networks, protocols, users, services, or shadow passwords instead of, or in addition to, using flat files or the Network Information Service (NIS). Bug Fix BZ# 788668 The update of nss_db attempted to fix a bug, which under certain circumstances prevented multi-threaded applications from obtaining complete lists of user's supplemental group memberships. This problem was not completely fixed due to an internal error that occurred when using an insufficiently large temporary buffer to parse a group entry with a large list of users. This update resolves the issue by resetting the buffer's contents after the buffer has been resized. Large group lists are thus correctly parsed and the entire list of user's supplemental groups is now correctly listed in this scenario. All users of nss_db are advised to upgrade to this updated package, which fixes this bug.

Commands:
20.13. Power Management It is possible to forcibly enable or disable BIOS advertisements to the guest virtual machine OS using conventional management tools which effects the following section of the domain XML: ... <pm> <suspend-to-disk enabled='no'/> <suspend-to-mem enabled='yes'/> </pm> ... Figure 20.19. Power management The <pm> element can be enabled using the arguement yes or disabled using the argument no . BIOS support can be implemented for S3 using the argument suspend-to-disk and S4 using the argument suspend-to-mem ACPI sleep states. If nothing is specified, the hypervisor will be left with its default value.

Commands:
<pm> <suspend-to-disk enabled='no'/> <suspend-to-mem enabled='yes'/> </pm>
Chapter 3. Standalone upgrade In general, Red Hat Quay supports upgrades from a prior (N-1) minor version only. For example, upgrading directly from Red Hat Quay 3.0.5 to the latest version of 3.5 is not supported. Instead, users would have to upgrade as follows: 3.0.5 3.1.3 3.1.3 3.2.2 3.2.2 3.3.4 3.3.4 3.4.z 3.4.z 3.5.z This is required to ensure that any necessary database migrations are done correctly and in the right order during the upgrade. In some cases, Red Hat Quay supports direct, single-step upgrades from prior (N-2, N-3) minor versions. This exception to the normal, prior minor version-only, upgrade simplifies the upgrade procedure for customers on older releases. The following upgrade paths are supported for Red Hat Quay 3.12: 3.10.z 3.12.z 3.11.z 3.12.z For users wanting to upgrade the Red Hat Quay Operator, see Upgrading the Red Hat Quay Operator Overview . This document describes the steps needed to perform each individual upgrade. Determine your current version and then follow the steps in sequential order, starting with your current version and working up to your desired target version. Upgrade to 3.12.z from 3.11.z Upgrade to 3.12.z from 3.10.z Upgrade to 3.11.z from 3.10.z Upgrade to 3.11.z from 3.9.z See the Red Hat Quay Release Notes for information on features for individual releases. The general procedure for a manual upgrade consists of the following steps: Stop the Quay and Clair containers. Backup the database and image storage (optional but recommended). Start Clair using the new version of the image. Wait until Clair is ready to accept connections before starting the new version of Quay. 3.1. Accessing images Red Hat Quay image from version 3.4.0 and later are available from registry.redhat.io and registry.access.redhat.com , with authentication set up as described in Red Hat Container Registry Authentication . 3.2. Upgrade to 3.12.z from 3.11.z 3.2.1. Target images Quay: registry.redhat.io/quay/quay-rhel8:v3.12.8 Clair: registry.redhat.io/quay/clair-rhel8:v3.12.8 PostgreSQL: registry.redhat.io/rhel8/postgresql-13:1-109 Redis: registry.redhat.io/rhel8/redis-6:1-110 3.3. Upgrade to 3.12.z from 3.10.z 3.3.1. Target images Quay: registry.redhat.io/quay/quay-rhel8:v3.12.8 Clair: registry.redhat.io/quay/clair-rhel8:v3.12.8 PostgreSQL: registry.redhat.io/rhel8/postgresql-13:1-109 Redis: registry.redhat.io/rhel8/redis-6:1-110 3.4. Upgrade to 3.11.z from 3.10.z 3.4.1. Target images Quay: registry.redhat.io/quay/quay-rhel8:v3.11.0 Clair: registry.redhat.io/quay/clair-rhel8:v3.11.0 PostgreSQL: registry.redhat.io/rhel8/postgresql-13:1-109 Redis: registry.redhat.io/rhel8/redis-6:1-110 3.5. Upgrade to 3.11.z from 3.9.z 3.5.1. Target images Quay: registry.redhat.io/quay/quay-rhel8:v3.11.0 Clair: registry.redhat.io/quay/clair-rhel8::v3.11.0 PostgreSQL: registry.redhat.io/rhel8/postgresql-13:1-109 Redis: registry.redhat.io/rhel8/redis-6:1-110

Commands:
8.233. webkitgtk 8.233.1. RHBA-2013:1613 - webkitgtk bug fix update Updated webkitgtk packages that fix one bug are now available for Red Hat Enterprise Linux 6. WebKitGTK+ is the port of the portable web rendering engine WebKit to the GTK+ platform. Bug Fix BZ# 966571 Previously, the just-in-time (JIT) compilation was not enabled for JavaScript in WebKitGTK+. As a consequence, some websites experienced problems with loading and performance. This update enables the JIT compilation for 32-bit Intel, Intel 64, and AMD64 architectures and the unwanted behavior no longer occurs. Users of webkitgtk are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.251. tar 7.251.1. RHBA-2012:1372 - tar bug fix update Updated tar packages that fix one bug are now available for Red Hat Enterprise Linux 6. The tar packages provide the GNU tar program. Gnu tar can allows to save multiple files in one archive and can restore the files from that archive. This update fixes the following bug: BZ# 841308 Prior to this update, tar failed to match and extract given file names from an archive when this archive was created with the options "--sparse" and "--posix". This update modifies the underlying code to match and extract the given name as expected. All users of tar are advised to upgrade to these updated packages, which fix this bug. 7.251.2. RHBA-2013:0489 - tar bug fix update Updated tar packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The tar packages provide the GNU tar utility, which allows the user to save multiple files in one archive and can restore the files from that archive. Bug Fixes BZ# 875727 When the "--strip-components" command-line parameter was used, the tar utility was unable to correctly match a file name that had to be extracted and the action failed. This bug has been fixed and tar now matches file names as expected in the described scenario. BZ#877769 When the "--listed-incremental" command-line parameter was used and a file was specified multiple times, tar terminated unexpectedly with a segmentation fault. The underlying source code has been modified and tar no longer crashes under these circumstances. All users of tar are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 3. Selecting an installed Red Hat build of OpenJDK version for a specific application Some applications require a specific Red Hat build of OpenJDK version to run. If multiple versions of Red Hat build of OpenJDK are installed on the system using the yum package manager or portable bundle, you can select a Red Hat build of OpenJDK version for each application where necessary by setting the value of the JAVA_HOME environment variable or using a wrapper script. Prerequisites Multiple versions of Red Hat build of OpenJDK installed on the machine. Ensure that the application you want to run is installed. Procedure Set the JAVA_HOME environment variable. For example, if Red Hat build of OpenJDK 17 was installed using yum : USD JAVA_HOME=/usr/lib/jvm/java-17-openjdk Note The symbolic link java-17-openjdk is controlled by the alternatives command. Do one of the following: Launch the application using the default, system-wide configuration. Launch the application specifying the JAVA_HOME variable:

Commands:
mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 11.0.9, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-11-openjdk-11.0.9.10-0.el8_0.x86_644/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-144.el8.x86_64", arch: "amd64", family: "unix"
JAVA_HOME=/usr/lib/jvm/java-17-openjdk-17.0.0.0.35-4.el8.x86_64/ mvn --version Apache Maven 3.5.4 (Red Hat 3.5.4-5) Maven home: /usr/share/maven Java version: 17, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-17-openjdk-17.0.0.0.35-4.el8.x86_64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "4.18.0-305.19.1.el8_4.x86_64", arch: "amd64", family: "unix"
Chapter 5. Frequently asked questions Is it possible to deploy applications to an OpenShift cluster from CodeReady Workspaces? Yes. The user must log in to the OpenShift cluster from their running workspace using oc login . For best performance, what is the recommended storage to use for Persistent Volumes used with CodeReady Workspaces? Use block storage. Is it possible to deploy more than one CodeReady Workspaces instance on the same cluster? It is not recommended. This feature is subject to removal in a future release. Is it possible to install CodeReady Workspaces offline (that is, disconnected from the internet)? Yes. See Installing CodeReady Workspaces in restricted environments . Is it possible to use non-default certificates with CodeReady Workspaces? Yes, you can use self-signed or public certificates. See Importing untrusted TLS certificates . Is it possible to run multiple workspaces simultaneously? Yes. See Configuring the number of workspaces that a user can run . What specific changes have been implemented for IBM Power Systems? The memory limit for some plug-ins has been increased, to give Pods sufficient RAM to run. Table 5.1. Example memory limits differences between IBM Power System and other architectures Plug-in IBM Power System Other architectures Che-Theia editor 2G 512M OpenShift connector 2.5G 1.5G

Commands:
3.14. Detaching a Virtual Disk This Ruby example detaches a disk from a virtual machine. # Find the virtual machine: vm = vms_service.list(search: 'name=myvm').first # Detach the first disk from the virtual machine: vm_service = vms_service.vm_service(vm.id) attachments_service = vm_service.disk_attachments_service attachment = attachments_service.list.first # Remove the attachment. The default behavior is that the disk is detached # from the virtual machine, but not deleted from the system. If you wish to # delete the disk, change the `detach_only` parameter to `false`. attachment.remove(detach_only: true) For more information, see http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/VmService:disk_attachments_service .

Commands:
Find the virtual machine: vm = vms_service.list(search: 'name=myvm').first Detach the first disk from the virtual machine: vm_service = vms_service.vm_service(vm.id) attachments_service = vm_service.disk_attachments_service attachment = attachments_service.list.first Remove the attachment. The default behavior is that the disk is detached from the virtual machine, but not deleted from the system. If you wish to delete the disk, change the `detach_only` parameter to `false`. attachment.remove(detach_only: true)
Chapter 3. Analyzing your projects with the MTA plugin You can analyze your projects with the MTA plugin by creating a run configuration and running an analysis. 3.1. Creating a run configuration You can create multiple run configurations to run against each project you import to IntelliJ IDEA. Procedure In the Projects view, click the project you want to analyze. On the left side of the screen, click the Migration Toolkit for Applications tab. If this is your first configuration, the run configuration panel is displayed on the right. If this is not your first configuration, right-click configuration in the list and select New configuration . The run configuration panel is displayed on the right. Complete the following configuration fields: cli : Enter the path to the cli executable. For example: USDHOME/mta-cli-7.1.1.GA-redhat/bin/mta-cli . Input : Click Add and enter the input file or directory. Target : Select one or more target migration paths. Note The location shown in the Output is set by the plugin. In the list of configurations, right-click the new configuration and select Run Analysis . The Console (MTA) terminal emulator opens, displaying information about the progress of the analysis. When the analysis is completed, you can click either Report or Results below the name of the configuration file you ran. Reports opens the MTA report, which describes any issues you need to address before you migrate or modernize your application. For more information, see Reviewing the reports in the CLI Guide . Results opens a directory displaying hints (issues) per application.

Commands:
7.126. libvirt-cim 7.126.1. RHBA-2013:0449 - libvirt-cim bug fix update Updated libvirt-cim packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The libvirt-cim package contains a Common Information Model (CIM) provider based on Common Manageability Programming Interface (CMPI). It supports most libvirt virtualization features and allows management of multiple libvirt-based platforms. Bug Fixes BZ# 805892 If the sblim-sfcb package was installed on the system, rebuilding the libvirt-cim package failed with an error due to an incomplete substitution in the Makefile. The substitution has been corrected and rebuilding libvirt-cim now works as expected. BZ#864096 When upgrading the libvirt-cim package to a newer version after libvirt-cim had registered its classes with a cim-server, the %preun code unregistered the classes leaving the system without libvirt-cim classes being registered. Now the libvirt-cim package only unregisters the libvirt-cim classes on uninstall. Users of libvirt-cim are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.3.4. Completing Transactions An unexpected situation, such as power loss or system crash, can prevent you from completing your yum transaction. When such event occurs in the middle of your transaction, you can try to resume it later with the following command as root : yum-complete-transaction The yum-complete-transaction tool searches for incomplete or aborted yum transactions on a system and attempts to complete them. By default, these transactions are listed in the /var/lib/yum/transaction-all and /var/lib/yum/transaction-done files. If there are more unfinished transactions, yum-complete-transaction attempts to complete the most recent one first. To clean transaction journal files without attempting to resume the aborted transactions, use the --cleanup-only option: yum-complete-transaction --cleanup-only

Commands:
2.5. Storage and File Systems device-mapper-multipath component Multipath's queue_without_daemon yes default option queues I/O even though all iSCSI links have been disconnected when the system is shut down, which causes LVM to become unresponsive when scanning all block devices. As a result, the system cannot be shut down. To work around this issue, add the following line into the defaults section of /etc/multipath.conf : initscripts component If the /etc/fstab file contains an NFS mount entry that has the file system check ( fsck ) enabled, the netfs service responsible for mounting and unmounting NFS file systems initializes the file system check. Because NFS is not a block-level file system, this operation fails, and subsequently also fails the system boot itself. To work around this problem, disable the file system check by setting the sixth vaule for NFS mount entries to 0 . iscsi-initiator-utils component, BZ# 739843 iSCSI discovery via a TOE (TCP Offload Engine) interface fails when the iscsiadm -m iface has never been executed. This is due to the iscsiadm -m discovery command not checking interface settings while the iscsiadm -m iface does. To work around this issue, run the iscsiadm -m iface command at least once after installing the iscsi-initiatio-utils package. Once the interface setting is updated, discoveries are performed with no errors. vdsm component Attempting to create/extend a storage domain on/with a device that exposes a block size different than 512 bytes such create/extend request to fail. To work around this issue, the storage must be configured to expose a block size of 512 bytes. kernel component, BZ# 606260 The NFSv4 server in Red Hat Enterprise Linux 6 currently allows clients to mount using UDP and advertises NFSv4 over UDP with rpcbind . However, this configuration is not supported by Red Hat and violates the RFC 3530 standard. lvm2 component The dracut utility currently only supports one FiberChannel over Ethernet (FCoE) connection to be used to boot from the root device. Consequently, booting from a root device that spans multiple FCoE devices (for example, using RAID, LVM or similar techniques) is not possible. lvm2 component The pvmove command cannot currently be used to move mirror devices. However, it is possible to move mirror devices by issuing a sequence of two commands. For mirror images, add a new image on the destination PV and then remove the mirror image on the source PV: Mirror logs can be handled in a similar fashion: or

Commands:
queue_without_daemon no
~]USD lvconvert -m +1 <vg/lv> <new PV> ~]USD lvconvert -m -1 <vg/lv> <old PV>
~]USD lvconvert --mirrorlog core <vg/lv> ~]USD lvconvert --mirrorlog disk <vg/lv> <new PV>
~]USD lvconvert --mirrorlog mirrored <vg/lv> <new PV> ~]USD lvconvert --mirrorlog disk <vg/lv> <old PV>