mtpti5iD/redhat-docs_dataset huggingface dataset:
14.7.3. Displaying the Amount of Free Memory in a NUMA Cell The virsh freecell displays the available amount of memory on the machine within a specified NUMA cell. This command can provide one of three different displays of available memory on the machine depending on the options specified. If no options are used, the total free memory on the machine is displayed. Using the --all option, it displays the free memory in each cell and the total free memory on the machine. By using a numeric argument or with --cellno option along with a cell number it will display the free memory for the specified cell.

Commands:
Chapter 2. Backing up important files Backing up important configuration files, inventory files, and modified playbooks makes it easy to restore or redeploy your cluster. Red Hat recommends backing up your configuration after initial deployment, and after confirming the success of any major changes in your cluster. You can also take backups after a node has failed if necessary. Prerequisites Example playbooks and inventory files are stored in the /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment directory. If you have manually created or modified inventory and playbook files and you are not storing them in this directory, ensure that you know the path to their location. Procedure Log in to a hyperconverged host as the root user. Change into the hc-ansible-deployment directory and back up the default archive_config_inventory.yml file. Edit the archive_config_inventory.yml file with details of the cluster you want to back up. hosts The backend FQDN of each host in the cluster that you want to back up. backup_dir The directory in which to store backup files. nbde_setup If you use Network-Bound Disk Encryption, set this to true . Otherwise, set to false . upgrade Set to false . For example: Run the archive_config.yml playbook using your updated inventory file with the backupfiles tag. This creates an archive in the /root directory specific to each host FQDN in the hosts section of the inventory, for example, /root/rhvh-node-host1-backend.example.com-backup.tar.gz . Transfer the backup archives to a different machine.

Commands:
cd /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment cp archive_config_inventory.yml archive_config_inventory.yml.bk
all: hosts: host1-backend.example.com : host2-backend.example.com : host3-backend.example.com : vars: backup_dir: /rhhi-backup nbde_setup: true upgrade: false
ansible-playbook -i archive_config_inventory.yml archive_config.yml --tags=backupfiles
scp /root/rhvh-node-host1-backend.example.com-backup.tar.gz backup-host.example.com:/backups/
35.4. Binding/Unbinding an iface to a Portal Whenever iscsiadm is used to scan for interconnects, it will first check the iface.transport settings of each iface configuration in /var/lib/iscsi/ifaces . The iscsiadm utility will then bind discovered portals to any iface whose iface.transport is tcp . This behavior was implemented for compatibility reasons. To override this, use the -I iface_name to specify which portal to bind to an iface , as in: By default, the iscsiadm utility will not automatically bind any portals to iface configurations that use offloading. This is because such iface configurations will not have iface.transport set to tcp . As such, the iface configurations of Chelsio, Broadcom, and ServerEngines ports need to be manually bound to discovered portals. It is also possible to prevent a portal from binding to any existing iface . To do so, use default as the iface_name , as in: To remove the binding between a target and iface , use: To delete all bindings for a specific iface , use: To delete bindings for a specific portal (e.g. for Equalogic targets), use: Note If there are no iface configurations defined in /var/lib/iscsi/iface and the -I option is not used, iscsiadm will allow the network subsystem to decide which device a specific portal should use. [7] Refer to Chapter 36, Scanning iSCSI Targets with Multiple LUNs or Portals for information on proper_target_name .

Commands:
iscsiadm -m discovery -t st -p target_IP:port -I iface_name -P 1
iscsiadm -m discovery -t st -p IP:port -I default -P 1
iscsiadm -m node -targetname proper_target_name -I iface0 --op=delete [7]
iscsiadm -m node -I iface_name --op=delete
iscsiadm -m node -p IP:port -I iface_name --op=delete
Chapter 2. Set Up and Configure Infinispan Query 2.1. Set Up Infinispan Query 2.1.1. Infinispan Query Dependencies in Library Mode To use the JBoss Data Grid Infinispan Query via Maven, add the following dependencies: Non-Maven users must install all infinispan-embedded-query.jar , infinispan-embedded.jar , jboss-transaction-api_1.1_spec-1.0.1.Final-redhat-2.jar files from the JBoss Data Grid distribution. Warning The Infinispan query API directly exposes the Hibernate Search and the Lucene APIs and cannot be embedded within the infinispan-embedded-query.jar file. Do not include other versions of Hibernate Search and Lucene in the same deployment as infinispan-embedded-query . This action will cause classpath conflicts and result in unexpected behavior. Report a bug

Commands:
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-embedded-query</artifactId> <version>USD{infinispan.version}</version> </dependency> <dependency> <groupId>javax.transaction</groupId> <artifactId>transaction-api</artifactId> <version>1.1</version> </dependency>
7.160. pinentry 7.160.1. RHBA-2015:0755 - pinentry bug fix update Updated pinentry packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The pinentry packages contain a collection of simple personal identification number (PIN) or password entry dialogs, which utilize the Assuan protocol as described by the Project Aegypten. The pinentry packages also contain the command line version of the PIN entry dialog. Bug Fixes BZ# 662770 Due to an auto-detection problem, the pinentry wrapper in some cases attempted to launch the pinentry-gtk program even if it was not installed. The pinentry wrapper has been updated, and the problem no longer occurs. BZ# 704495 Due to lack of UTF-8 support, the output description text got scrambled when the "pinentry getpin" command was used. The same problem could occur when using the GNU Privacy Guard utility that called the "pinentry getpin" command on a key containing non-ASCII characters in its name. To fix this bug, proper UTF-8 translation has been performed, and the pinentry-curses binary file has been compiled against the ncursesw library, which contains wide character support. As a result, the output text is now correct. Users of pinentry are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.66. hypervkvpd 8.66.1. RHBA-2013:1539 - hypervkvpd bug fix update Updated hypervkvpd packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The hypervkvpd packages contain hypervkvpd, the guest Hyper-V Key-Value Pair (KVP) daemon. Using VMbus, hypervkvpd passes basic information to the host. The information includes guest IP address, fully qualified domain name, operating system name, and operating system release number. An IP injection functionality enables the user to change the IP address of a guest from the host via the hypervkvpd daemon. Bug Fixes BZ# 920032 Previously, the hypervkvpd service registered to two netlink multicast groups, one of which was used by the cgred service. When hypervkvpd received a netlink message, it was interpreted blindly as its own. As a consequence, hypervkvpd terminated unexpectedly with a segmentation fault. After this update, hypervkvpd now registers only to its own netlink multicast group and verifies the type of the incoming netlink message. Using hypervkvpd when the cgred service is running no longer leads to a segmentation fault. BZ# 962565 Prior to this update, the hypervkvpd init script did not check if Hyper-V driver modules were loaded into the kernel. If hypervkvpd was installed, it started automatically on system boot, even if the system was not running as a guest machine on a Hyper-V hypervisor. Verification has been added to the hypervkvpd init script to determine whether Hyper-V driver modules are loaded into the kernel. As a result, if the modules are not loaded into the kernel, hypervkvpd now does not start, but displays a message that proper driver modules are not loaded. BZ# 977861 Previously, hypervkvpd was not built with sufficiently secure compiler options, which could, consequently, make the compiled code vulnerable. The hypervkvpd daemon has been built with full read-only relocation (RELRO) and position-independent executable (PIE) flags. As a result, the compiled code is more secure and better guarded against possible buffer overflows. BZ# 983851 When using the Get-VMNetworkAdapter command to query a virtual machine network adapter, each subnet string has to be separated by a semicolon. Due to a bug in the IPv6 subnet enumeration code, the IPv6 addresses were not listed. A patch has been applied, and the IPv6 subnet enumeration now works as expected. Users of hypervkvpd are advised to upgrade to these updated packages, which fix these bugs. After updating the hypervkvpd packages, rebooting all guest machines is recommended, otherwise the Microsoft Windows server with Hyper-V might not be able to get information from these guest machines.

Commands:
Upgrading disconnected Red Hat Satellite to 6.15 Red Hat Satellite 6.15 Upgrade Disconnected Satellite Server and Capsule Red Hat Satellite Documentation Team satellite-doc-list@redhat.com

Commands:
satellite-maintain service stop
satellite-maintain service start
satellite-installer --foreman-proxy-dns-managed=false --foreman-proxy-dhcp-managed=false
rm /etc/yum.repos.d/*
cp /media/sat6/Satellite/media.repo /etc/yum.repos.d/satellite.repo
vi /etc/yum.repos.d/satellite.repo
[Satellite-6.15]
baseurl=file:///media/sat6/Satellite
cp /media/sat6/Maintenance/media.repo /etc/yum.repos.d/satellite-maintenance.repo
vi /etc/yum.repos.d/satellite-maintenance.repo
[Satellite-Maintenance]
baseurl=file:///media/sat6/Maintenance/
dnf module enable satellite-maintenance:el8
satellite-maintain upgrade list-versions
satellite-maintain upgrade check --target-version 6.15 --whitelist="repositories-validate,repositories-setup"
satellite-maintain upgrade run --target-version 6.15 --whitelist="repositories-validate,repositories-setup"
dnf needs-restarting --reboothint
reboot
satellite-maintain service restart
foreman-rake foreman_openscap:bulk_upload:default
yum clean metadata
satellite-maintain self-upgrade
grep foreman_url /etc/foreman-proxy/settings.yml
satellite-maintain upgrade list-versions
satellite-maintain upgrade check --target-version 6.15
satellite-maintain upgrade run --target-version 6.15
dnf needs-restarting --reboothint
reboot
satellite-installer --foreman-db-host newpostgres.example.com --katello-candlepin-db-host newpostgres.example.com --foreman-proxy-content-pulpcore-postgresql-host newpostgres.example.com
Chapter 7. References 7.1. Red Hat Configuring and managing high availability clusters Support Policies for RHEL High Availability Clusters Support Policies for RHEL High Availability Clusters - Fencing/STONITH Support Policies for RHEL High Availability Clusters - Management of SAP S/4HANA Support Policies for RHEL High Availability Clusters - Management of SAP NetWeaver in a Cluster Red Hat HA Solutions for SAP HANA, S/4HANA and NetWeaver based SAP Applications How to enable the SAP HA Interface for SAP ABAP application server instances managed by the RHEL HA Add-On? How to manage standalone SAP Web Dispatcher instances using the RHEL HA Add-On The Systemd-Based SAP Startup Framework 7.2. SAP SAP Note 1552925 - Linux: High Availability Cluster Solutions SAP Note 1693245 - SAP HA Script Connector Library SAP Note 1908655 - Support details for Red Hat Enterprise Linux HA Add-On SAP Note 2630416 - Support for Standalone Enqueue Server 2 SAP Note 2641322 - Installation of ENSA2 and update from ENSA1 to ENSA2 when using the Red Hat HA solutions for SAP SAP Note 2772999 - Red Hat Enterprise Linux 8.x: Installation and Configuration Standalone Enqueue Server | SAP Help Portal Setting up Enqueue Replication Server Fail over | SAP Blogs High Availability with the Standalone Enqueue Server Evolution of ENSA2 and ERS2... | SAP Blogs

Commands:
Planning your environment OpenShift Dedicated 4 An overview of planning for Dedicated 4 Red Hat OpenShift Documentation Team

Commands:
ocm login --token <token> 1
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ec2:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "autoscaling:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "s3:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "iam:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "elasticloadbalancing:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "cloudwatch:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "events:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "logs:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "support:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "kms:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "sts:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "tag:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "route53:*" ], "Resource": [ "*" ] }, { "Effect": "Allow", "Action": [ "servicequotas:ListServices", "servicequotas:GetRequestedServiceQuotaChange", "servicequotas:GetServiceQuota", "servicequotas:RequestServiceQuotaIncrease", "servicequotas:ListServiceQuotas" ], "Resource": [ "*" ] } ] }
{ "Version": "2012-10-17", "Statement": [ { "Action": "*", "Resource": "*", "Effect": "Allow" } ] }
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ec2:AttachVpnGateway", "ec2:DescribeVpnConnections", "ec2:AcceptVpcPeeringConnection", "ec2:DeleteVpcPeeringConnection", "ec2:DescribeVpcPeeringConnections", "ec2:CreateVpnConnectionRoute", "ec2:RejectVpcPeeringConnection", "ec2:DetachVpnGateway", "ec2:DeleteVpnConnectionRoute", "ec2:DeleteVpnGateway", "ec2:DescribeVpcs", "ec2:CreateVpnGateway", "ec2:ModifyVpcPeeringConnectionOptions", "ec2:DeleteVpnConnection", "ec2:CreateVpcPeeringConnection", "ec2:DescribeVpnGateways", "ec2:CreateVpnConnection", "ec2:DescribeRouteTables", "ec2:CreateTags", "ec2:CreateRoute", "directconnect:*" ], "Resource": "*" } ] }
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "aws-portal:ViewAccount", "aws-portal:ViewBilling" ], "Resource": "*" } ] }
Chapter 1. Introduction Before using this guide to configure JBoss EAP, it is assumed that the latest version of JBoss EAP has been downloaded and installed. For installation instructions, see the JBoss EAP Installation Guide . Important Since the installation location of JBoss EAP will vary between host machines, this guide refers to the installation location as EAP_HOME . The actual location of the JBoss EAP installation should be used instead of EAP_HOME when performing administrative tasks.

Commands:
Chapter 94. MavenArtifact schema reference Used in: Plugin The type property is a discriminator that distinguishes use of the MavenArtifact type from JarArtifact , TgzArtifact , ZipArtifact , OtherArtifact . It must have the value maven for the type MavenArtifact . Property Property type Description repository string Maven repository to download the artifact from. Applicable to the maven artifact type only. group string Maven group id. Applicable to the maven artifact type only. artifact string Maven artifact id. Applicable to the maven artifact type only. version string Maven version number. Applicable to the maven artifact type only. insecure boolean By default, connections using TLS are verified to check they are secure. The server certificate used must be valid, trusted, and contain the server name. By setting this option to true , all TLS verification is disabled and the artifacts will be downloaded, even when the server is considered insecure. type string Must be maven .

Commands:
8.242. tomcatjss 8.242.1. RHBA-2014:1550 - tomcatjss bug fix update An updated tomcatjss package that fixes one bug is now available for Red Hat Enterprise Linux 6. The tomcatjss package provides a Java Secure Socket Extension (JSSE) implementation using Java Security Services (JSS) for Tomcat 6. Bug Fix BZ# 1084224 Previously, the tomcatjss package missed the strictCiphers implementation. Consequently, the user could not disable weaker ciphers and enable the stronger ciphers. With this update, strictCiphers has been implemented to tomcatjss. Users of tomcatjss are advised to upgrade to this updated package, which fixes this bug.

Commands:
2.2. Command Line Configuration In case your system does not have the Date/Time Properties tool installed, or the X Window Server is not running, you will have to change the system date and time on the command line. Note that in order to perform actions described in this section, you have to be logged in as a superuser: 2.2.1. Date and Time Setup The date command allows the superuser to set the system date and time manually: Change the current date. Type the command in the following form at a shell prompt, replacing the YYYY with a four-digit year, MM with a two-digit month, and DD with a two-digit day of the month: For example, to set the date to 2 June 2010, type: Change the current time. Use the following command, where HH stands for an hour, MM is a minute, and SS is a second, all typed in a two-digit form: If your system clock is set to use UTC (Coordinated Universal Time), add the following option: For instance, to set the system clock to 11:26 PM using the UTC , type: You can check your current settings by typing date without any additional argument: Example 2.1. Displaying the current date and time

Commands:
~]USD su - Password:
~]# date +%D -s YYYY-MM-DD
~]# date +%D -s 2010-06-02
~]# date +%T -s HH:MM:SS
~]# date +%T -s HH:MM:SS -u
~]# date +%T -s 23:26:00 -u
~]USD date Wed Jun 2 11:58:48 CEST 2010
Chapter 9. Reinstalling GRUB You can reinstall the GRUB boot loader to fix certain problems, usually caused by an incorrect installation of GRUB, missing files, or a broken system. You can resolve these issues by restoring the missing files and updating the boot information. Reasons to reinstall GRUB: Upgrading the GRUB boot loader packages. Adding the boot information to another drive. The user requires the GRUB boot loader to control installed operating systems. However, some operating systems are installed with their own boot loaders and reinstalling GRUB returns control to the desired operating system. Note GRUB restores files only if they are not corrupted. 9.1. Reinstalling GRUB on BIOS-based machines You can reinstall the GRUB boot loader on your BIOS-based system. Always reinstall GRUB after updating the GRUB packages. Important This overwrites the existing GRUB to install the new GRUB. Ensure that the system does not cause data corruption or boot crash during the installation. Procedure Reinstall GRUB on the device where it is installed. For example, if sda is your device: Reboot your system for the changes to take effect: Additional resources grub-install(1) man page on your system 9.2. Reinstalling GRUB on UEFI-based machines You can reinstall the GRUB boot loader on your UEFI-based system. Important Ensure that the system does not cause data corruption or boot crash during the installation. Procedure Reinstall the grub2-efi and shim boot loader files: Reboot your system for the changes to take effect: 9.3. Reinstalling GRUB on IBM Power machines You can reinstall the GRUB boot loader on the Power PC Reference Platform (PReP) boot partition of your IBM Power system. Always reinstall GRUB after updating the GRUB packages. Important This overwrites the existing GRUB to install the new GRUB. Ensure that the system does not cause data corruption or boot crash during the installation. Procedure Determine the disk partition that stores GRUB: Reinstall GRUB on the disk partition: Replace partition with the identified GRUB partition, such as /dev/sda1 . Reboot your system for the changes to take effect: Additional resources grub-install(1) man page on your system 9.4. Resetting GRUB Resetting GRUB completely removes all GRUB configuration files and system settings, and reinstalls the boot loader. You can reset all the configuration settings to their default values, and therefore fix failures caused by corrupted files and invalid configuration. Important The following procedure will remove all the customization made by the user. Procedure Remove the configuration files: Reinstall packages. On BIOS-based machines: On UEFI-based machines: Rebuild the grub.cfg file for the changes to take effect. On BIOS-based machines: On UEFI-based machines: Follow Reinstalling GRUB procedure to restore GRUB on the /boot/ partition.

Commands:
grub2-install /dev/sda
reboot
yum reinstall grub2-efi shim
reboot
bootlist -m normal -o sda1
grub2-install partition
reboot
rm /etc/grub.d/ * rm /etc/sysconfig/grub
yum reinstall grub2-tools
yum reinstall grub2-efi shim grub2-tools
grub2-mkconfig -o /boot/grub2/grub.cfg
grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
C.6. Accessing Graphical Applications Remotely It is possible to access graphical applications on a remote server using these methods: You can start a separate application directly from your SSH session in your local X server. For that, you need to enable X11 forwarding. See Section 14.5.1, "X11 Forwarding" for details. You can run the whole X session over network using VNC. This method can be useful, especially when you are using a workstation without X server, for example, a non-Linux system. See Chapter 15, TigerVNC for details.

Commands:
Part V. Red Hat Build of OptaPlanner quick start guides Red Hat Build of OptaPlanner provides the following quick start guides to demonstrate how OptaPlanner can integrate with different techologies: Red Hat Build of OptaPlanner on the Red Hat build of Quarkus platform: a school timetable quick start guide Red Hat Build of OptaPlanner on the Red Hat build of Quarkus platform: a vaccination appointment scheduler quick start guide Red Hat Build of OptaPlanner on the Red Hat build of Quarkus platform: an employee scheduler quick start guide Red Hat Build of OptaPlanner on Spring Boot: a school timetable quick start guide Red Hat Build of OptaPlanner with Java solvers: a school timetable quick start guide

Commands:
5.32. coolkey 5.32.1. RHBA-2012:0948 - coolkey bug fix update Updated coolkey packages that resolve two issues are now available for Red Hat Enterprise Linux 6. Coolkey is a smart card support library for the CoolKey, CAC, and PIV smart cards. Bug Fixes BZ# 700907 Prior to this update, Coolkey did not recognize Spice virtualized CAC cards unless the card contained at least 3 certificates. This update fixes this issue so that cards with one or two certificates are recognized by Coolkey as expected. Note that this issue may also have affected some non-virtualized CAC cards. BZ# 713132 Under certain error conditions, Coolkey could leak memory data because a variable buffer was not being freed properly. With this update, the aforementioned buffer is properly freed, and memory leaks no longer occur. All users of coolkey are advised to upgrade to these updated packages, which resolve these issues.

Commands: