mtpti5iD/redhat-docs_dataset huggingface dataset:
39.2. iSCSI Settings With dm-multipath If dm-multipath is implemented, it is advisable to set iSCSI timers to immediately defer commands to the multipath layer. To configure this, nest the following line under device { in /etc/multipath.conf : This ensures that I/O errors are retried and queued if all paths are failed in the dm-multipath layer. You may need to adjust iSCSI timers further to better monitor your SAN for problems. Available iSCSI timers you can configure are NOP-Out Interval/Timeouts and replacement_timeout , which are discussed in the following sections. 39.2.1. NOP-Out Interval/Timeout To help monitor problems the SAN, the iSCSI layer sends a NOP-Out request to each target. If a NOP-Out request times out, the iSCSI layer responds by failing any running commands and instructing the SCSI layer to requeue those commands when possible. When dm-multipath is being used, the SCSI layer will fail those running commands and defer them to the multipath layer. The multipath layer then retries those commands on another path. If dm-multipath is not being used, those commands are retried five times before failing altogether. Intervals between NOP-Out requests are 10 seconds by default. To adjust this, open /etc/iscsi/iscsid.conf and edit the following line: Once set, the iSCSI layer will send a NOP-Out request to each target every [interval value] seconds. By default, NOP-Out requests time out in 10 seconds [10] . To adjust this, open /etc/iscsi/iscsid.conf and edit the following line: This sets the iSCSI layer to timeout a NOP-Out request after [timeout value] seconds. SCSI Error Handler If the SCSI Error Handler is running, running commands on a path will not be failed immediately when a NOP-Out request times out on that path. Instead, those commands will be failed after replacement_timeout seconds. For more information about replacement_timeout , refer to Section 39.2.2, " replacement_timeout " . To verify if the SCSI Error Handler is running, run: [10] Prior to Red Hat Enterprise Linux 5.4, the default NOP-Out requests time out was 15 seconds.

Commands:
features "1 queue_if_no_path"
node.conn[0].timeo.noop_out_interval = [interval value]
node.conn[0].timeo.noop_out_timeout = [timeout value]
iscsiadm -m session -P 3
7.215. ricci 7.215.1. RHBA-2013:0453 - ricci bug fix and enhancement update Updated ricci packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The ricci packages contain a daemon and a client for remote configuring and managing of clusters. Bug Fixes BZ# 811702 Prior to this update, if the ricci daemon was not running on all nodes, executing the "ccs --stopall" command caused an attribute error to occur. With this update, the code has been fixed and the error no longer occurs in the aforementioned scenario. BZ#815752 Previously, a segmentation fault occurred in both the ricci daemon and ccs_sync utility when processing a larger cluster.conf file. This was caused by an insufficient thread stack size in ricci. The ccs_sync utility terminated unexpectedly due to incorrect behavior of the PR_Write function. With this update, a patch has been introduced to fix both causes. As a result, the segmentation fault no longer occurs. BZ# 877381 Previously, a segmentation fault occurred in the ricci daemon when processing cluster.conf files with very large values. This was caused by allocating large amounts of memory not available on the stack. With this update, a patch has been introduced to allocate memory on the heap and provide an error if not enough memory is available. As a result, the segmentation fault no longer occurs. BZ# 818335 Previously, the "ccs_sync" command did not return a non-zero exit code if an error occurred or the ricci daemon was not running, even when running the command with the "-w" option to exit with a failure status if any warnings were issued. The underlying source code has been modified so that "ccs_sync" with the "-w" option now returns "1" on failure. BZ# 839039 With this update, a minor typographical error has been fixed in the ccs error message related to being unable to start a node, possibly due to lack of quorum. BZ#841288 Previously, the "ccs --lsmisc" command did not properly display the alternate multicast address. The bug has been fixed, and the alternate multicast address is now reported correctly when --lsmisc is used. BZ# 867019 Previously, the ccs program failed to generate certificates when running on a read-only NFS. This bug has been fixed and ccs now generates certificates regardless of the type of the current working directory. BZ# 866894 Previously, the ccs program incorrectly handled the cluster.conf file when adding a resource into the file. Consequently, resulting cluster.conf was invalid. This bug has been fixed and ccs now works correctly in the described case. BZ#842939 Previously, the ricci daemon would not properly handle yum output when it was split over multiple lines. Consequently, in certain circumstances the conga management system was unable to list or install packages. This bug has been fixed and ricci now works correctly in the described case. Enhancement BZ# 878108 The cluster schema has been updated to match the current Red Hat Enterprise Linux 6.4 cluster packages. All users of ricci are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 4. Cleaning Integration Test Suite (tempest) resources Before you validate your deployments by using OpenStack Integration Test Suite (tempest), run the cleanup command with the --init-saved-state flag. This command scans your environment to discover resources, for example networks, volumes, images, flavors, projects, and users. The discovered resources are saved in a file called saved_state.json . When the tempest cleanup command is executed all resources not recorded in the saved_state.json file are deleted. Prerequisites An OpenStack environment that contains the Integration Test Suite packages. For more information, see Installing the Integration Test Suite with director . An Integration Test Suite configuration that corresponds to your OpenStack environment. For more information, see Creating a workspace . One or more completed Integration Test Suite validation tests. 4.1. Performing a dry run Perform a dry run before you execute the cleanup. A dry run lists the files that Integration Test Suite would delete by a cleanup, without actually deleting any files. The dry_run.json file contains the list of files that a cleanup deletes. Procedure Complete the dry run: Review the dry_run.json file to ensure that the cleanup does not delete any files that you require for your environment. 4.2. Performing a tempest clean up Before you run any tempest tests, you must initialize the saved state. This creates the file saved_state.json , which prevents the cleanup from deleting objects that must be kept. Warning If you do not run the cleanup command with the --init-saved-state flag, RHOSP objects are deleted. If you create objects after running the cleanup command with --init-saved-state , those objects can be deleted by subsequent tempest commands. Procedure Initialize the saved state to create the saved_state.json file: Perform the cleanup: The tempest cleanup command deletes tempest resources but does not delete projects or the tempest administrator account. Note You can modify the saved_state.json file to include or exclude objects that you want to retain or remove.

Commands:
tempest cleanup --dry-run
tempest cleanup --init-saved-state
tempest cleanup
8.214. servicelog 8.214.1. RHBA-2014:1443 - servicelog bug fix and enhancement update Updated servicelog packages that fix several bugs and add various enhancements are now available. The servicelog packages provide a relational database to help manage errors on IBM eServer System p machines. Firmware and device driver errors are logged and managed using this database, which provides advanced error management capabilities. Note The servicelog packages have been updated to upstream version 1.1.12, which includes several minor bug fixes and adds support for handling platform dependencies like the PowerVM guest or BE guest. (BZ# 739119 , BZ# 1088404 ) All users of servicelog are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 10. Dashboard (horizon) Parameters Parameter Description HorizonAllowedHosts A list of IP/Hostname for the server OpenStack Dashboard (horizon) is running on. Used for header checks. The default value is * . HorizonCustomizationModule OpenStack Dashboard (horizon) has a global overrides mechanism available to perform customizations. HorizonPasswordValidator Regex for password validation. HorizonPasswordValidatorHelp Help text for password validation. HorizonSecret Secret key for the webserver. HorizonSecureCookies Set CSRF_COOKIE_SECURE / SESSION_COOKIE_SECURE in OpenStack Dashboard (horizon). The default value is False . HorizonVhostExtraParams Extra parameters for OpenStack Dashboard (horizon) vhost configuration. The default value is {'add_listen': True, 'priority': 10, 'access_log_format': '%a %l %u %t \\"%r\\" %>s %b \\"%%{}{Referer}i\\" \\"%%{}{User-Agent}i\\"', 'options': ['FollowSymLinks', 'MultiViews']} . MemcachedIPv6 Enable IPv6 features in Memcached. The default value is False . TimeZone The timezone to be set on the overcloud. The default value is UTC . WebSSOChoices Specifies the list of SSO authentication choices to present. Each item is a list of an SSO choice identifier and a display message. The default value is [['OIDC', 'OpenID Connect']] . WebSSOEnable Enable support for Web Single Sign-On. The default value is False . WebSSOIDPMapping Specifies a mapping from SSO authentication choice to identity provider and protocol. The identity provider and protocol names must match the resources defined in keystone. The default value is {'OIDC': ['myidp', 'openid']} . WebSSOInitialChoice The initial authentication choice to select by default. The default value is OIDC .

Commands:
Upgrading connected Red Hat Satellite to 6.15 Red Hat Satellite 6.15 Upgrade 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
subscription-manager repos --enable satellite-maintenance-6.15-for-rhel-8-x86_64-rpms
dnf module enable satellite-maintenance:el8
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
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
4.208. openssh 4.208.1. RHBA-2011:1551 - openssh bug fix and enhancement update Updated openssh packages that fix multiple bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. OpenSSH is OpenBSD's Secure Shell (SSH) protocol implementation. These packages include the core files necessary for the OpenSSH client and server. Bug Fixes BZ# 685060 Prior to this update, SELinux could prevent users from uploading new files to their home directories in a chrooted Secure File Transfer Protocol (SFTP) environment. This bug has been fixed and users are now able to upload and download files in chrooted environment using SFTP. BZ# 705397 , BZ# 728459 Prior to this update, multiple manual pages contained formatting errors. As a consequence, error messages or warnings could be displayed when viewing these manual pages. The formatting has been corrected and the error messages and warnings are no longer displayed. BZ# 708056 Previously, when the SSH_USE_STRONG_RNG environment variable was set to 1, openssh read 48 bytes from the /dev/random number generator to generate a seed. This seed was too long and caused long delays on ssh or sshd startup and when connections were received. Now, the SSH_USE_STRONG_RNG variable contains the number of bytes that should be pulled from /dev/random (with a minimum default value of six) and the delays no longer occur. BZ# 714554 Previously, when restarting the dovecot service, ssh could become unresponsive. With this update, the source code is modified and the dovecot service now restarts properly and without hanging. BZ# 729021 Prior to this update, the debuginfo file was missing in the debuginfo package. With this update, the debuginfo file is included in the package and users can now view all debug information. BZ# 731939 Previously, the lastlog command did not show the last login of a user with a big user ID on 32-bit architectures. With this update, the source code is modified so that the last login information is now always recorded. Enhancement BZ# 695781 With this update, multiple manual pages now describe Internet Protocol version 6 (IPv6) usage. All users of openssh are advised to upgrade to these updated packages, which fix these bugs and add this enhancement. 4.208.2. RHEA-2012:0065 - openssh enhancement update Updated openssh packages that add one enhancement are now available for Red Hat Enterprise Linux 6. OpenSSH is OpenBSD's Secure Shell (SSH) protocol implementation. These packages include the core files necessary for the OpenSSH client and server. Enhancement BZ# 782367 Previously, OpenSSH could use the Advanced Encryption Standard New Instructions (AES-NI) instruction set only with the AES Cipher-block chaining (CBC) cipher. This update adds support for Counter (CTR) mode encryption in OpenSSH so the AES-NI instruction set can now be used efficiently also with the AES CTR cipher. All users of openssh are advised to upgrade to these updated packages, which add this enhancement.

Commands:
8.133. openscap 8.133.1. RHBA-2013:1590 - openscap bug fix and enhancement update Updated openscap packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The openscap packages provide OpenSCAP, which is a set of open source libraries for the integration of the Security Content Automation Protocol (SCAP). SCAP is a line of standards that provide a standard language for the expression of Computer Network Defense (CND) related information. Note The openscap packages have been upgraded to upstream version 0.9.12, which provides a number of bug fixes and enhancements over the version. This update adds support for the National Institute of Standards and Technology's (NIST) SCAP 1.2 standard, so that all content, such as the following, is correctly supported: the Red Hat Enterprise Linux 5 Security Technical Implementation Guide (STIG), The United States Government Configuration Baseline (USGCB), and Red Hat Security Advisory content. (BZ# 956763 ) Bug Fix BZ# 999903 Previously, the oscap utility did not properly handle the process of object evaluation while querying the RPM database (RPMDB). RPMDB iterators created upon the query were not correctly removed if the process was aborted, which led to RPMDB corruption. With this update, the created RPMDB iterators are now removed correctly and process abortion no longer causes RPMDB corruption. Users of openscap are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
11.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: allow_rsync_anon_write Having this Boolean enabled allows rsync in the rsync_t domain to manage files, links and directories that have a type of public_content_rw_t . Often these are public files used for public file transfer services. Files and directories must be labeled public_content_rw_t . rsync_client Having this Boolean enabled allows rsync to initiate connections to ports defined as rsync_port_t , as well as allowing rsync to manage files, links and directories that have a type of rsync_data_t . Note that the rsync daemon must be in the rsync_t domain in order for SELinux to enact its control over rsync . The configuration example in this chapter demonstrates rsync running in the rsync_t domain. rsync_export_all_ro Having this Boolean enabled allows rsync in the rsync_t domain to export NFS and CIFS volumes with read-only access to clients. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
Appendix E. Importing an Existing Ceph Cluster to Ansible You can configure Ansible to use a cluster deployed without Ansible. For example, if you upgraded Red Hat Ceph Storage 1.3 clusters to version 2 manually, configure them to use Ansible by following this procedure: After manually upgrading from version 1.3 to version 2, install and configure Ansible on the administration node. Ensure that the Ansible administration node has passwordless ssh access to all Ceph nodes in the cluster. See Section 3.9, "Enabling password-less SSH for Ansible" for more details. As root , create a symbolic link to the Ansible group_vars directory in the /etc/ansible/ directory: As root , create an all.yml file from the all.yml.sample file and open it for editing: Set the generate_fsid setting to false in group_vars/all.yml . Get the current cluster fsid by executing ceph fsid . Set the retrieved fsid in group_vars/all.yml . Modify the Ansible inventory in /etc/ansible/hosts to include Ceph hosts. Add monitors under a [mons] section, OSDs under an [osds] section and gateways under an [rgws] section to identify their roles to Ansible. Make sure ceph_conf_overrides is updated with the original ceph.conf options used for [global] , [osd] , [mon] , and [client] sections in the all.yml file. Options like osd journal , public_network and cluster_network should not be added in ceph_conf_overrides because they are already part of all.yml . Only the options that are not part of all.yml and are in the original ceph.conf should be added to ceph_conf_overrides . From the /usr/share/ceph-ansible/ directory run the playbook.

Commands:
ln -s /usr/share/ceph-ansible/group_vars /etc/ansible/group_vars
cd /etc/ansible/group_vars cp all.yml.sample all.yml vim all.yml
cd /usr/share/ceph-ansible/ ansible-playbook infrastructure-playbooks/take-over-existing-cluster.yml -u <username> -i hosts
2.20. RHEA-2011:0572 - new package: nuxwdog New nuxwdog packages are now available for Red Hat Enterprise Linux 6. The nuxwdog packages provide a watchdog daemon that is used to start, stop, and monitor system processes, as well as to prompt users for passwords when required. Additionally, interfaces to the client code for various programming languages are included to allow clients to interact with the nuxwdog daemon. This enhancement update adds the nuxwdog packages to Red Hat Enterprise Linux 6. (BZ# 643546 ) All users who require nuxwdog should install these new packages.

Commands:
Chapter 7. References 7.1. Red Hat Configuring and managing high availability clusters on RHEL 9 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 3108316 - Red Hat Enterprise Linux 9.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:
11.2. Modeling your functions Teiid Designer provides an object wizard to assist you in modeling your User Defined Functions. Right-click the existing Relational View Model and click New Child - Procedure and then click on the radio button for "User Defined Function". In the wizard, you can see an option to specify the function's jar location on your file system, as well as the Java class and the Java method. If you create a function using alternative methods, you must select the procedure and edit the different properties for the procedure in the Properties view. Figure 11.1. VDB UDF Jar Files A User Defined Function represents a defined method in a java class. In order for the Teiid runtime to register the function and allow its use in the transformations, you must specify the following as properties: Function Category - unique name for a grouping of user defined functions. This category is displayed in the Expression Builder wizard so you can locate and select your function. Java Class - fully qualified name of the java class containing your function method. Java Method - the name of the function method in your java class. UDF Jar Path - the relative path in your project for the jar containing your UDF which will be in a lib folder in your project. If you are defining your jar for the first time and there is no jars in your lib folder, the property editor will allow you to select a jar from your file system. If one or more jars already exist in a lib folder, the editor will allow you to choose between selecting from your workspace or your file system.

Commands:
1.5. JBoss Operations Network 1.5.1. Installing JBoss Agent Plug-in Packs JBoss Operations Network has additional agent plug-ins to manage other JBoss products. Although these are JBoss ON resource plug-ins, they are included in separate packages and require a separate subscription to download them. Download the plug-in JAR files from the Customer Support Portal. Navigate to https://access.redhat.com/jbossnetwork/ . Select JBoss ON for PRODUCT . Select Download . Extract the plug-in JAR files into the JON_HOME /plugins directory. Have the JBoss ON server update its plug-ins. This can be done through the JBoss ON GUI or by restarting the server. To load the plug-ins through the GUI: Open the Administration tab. In the Configuration area on the left, select the Agent Plug-ins link. At the bottom of the list of loaded agent plug-ins, click the SCAN FOR UPDATES button. Have the agents reload their plug-ins to load the new plug-ins. This can be done from the agent's command prompt using the plugins command: Note This can also be done in the JBoss ON GUI by scheduling an update plugins operation for an agent or a group or agents. Alternatively, restart the agents.

Commands:
> plugins update