mtpti5iD/redhat-docs_dataset huggingface dataset:
7.195. setroubleshoot 7.195.1. RHBA-2015:1361 - setroubleshoot bug fix update Updated setroubleshoot packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The setroubleshoot packages contain a set of analysis plug-ins for use with the setroubleshoot utility. Each plug-in has the capacity to analyze SELinux Access Vector Cache (AVC) data, as well as system data, to provide user-friendly reports that describe how to interpret SELinux AVC denial messages. Bug Fixes BZ# 787139 On Red Hat Enterprise Linux 6, the "sealert -a" command previously only displayed a part of the expected output. This update adds the missing line of code, and "sealert -a" now prints the full extent of its output. BZ# 1098068 Prior to this update, the "sealert -V" command did not properly display the verbose debug message. With this update, the underlying code has been adjusted to ensure that the the verbose form of the debug message is printed, and the described problem no longer occurs. Users of setroubleshoot are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.163. pacemaker 8.163.1. RHBA-2014:1544 - pacemaker bug fix update Updated pacemaker packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The Pacemaker Resource Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Bug Fixes BZ# 1036631 Previously, co-location constraints for cloned groups were not fully respected. As a consequence, members of cloned groups were not correctly stopped along with dependencies. Now, members of cloned groups are stopped whenever dependencies are also stopped. BZ# 1037423 Prior to this update, no information concerning the status of healthy members of a cloned resource group were displayed to the user. A new option has been added to allow the status of cloned groups to be shown in the output of the "pcs status --full" command. BZ# 1046131 Previously, Pacemaker did not correctly cancel the recurring monitor operation of LSB scripts it managed. Consequently, monitor operations failed after resources successfully stopped. This bug has been fixed, and recurring monitor operations are now correctly cancelled before the LSB resource is stopped. BZ# 1069279 Under some conditions, the default stop or start ordering of resources enabled violation of co-location constraints. As a consequence, resources could be temporarily active on the same node despite a colocation constraint that instructed them otherwise. With this update, ordering of resources respects configured colocation constraints, and resources are never on the same node if configured not to be. BZ# 1078954 Previously, Pacemaker could not start more than 10 instances of a cloned resource. As a consequence, clusters containing more than 10 nodes did not function correctly. This update fixes this bug, and Pacemaker can now properly start an unlimited number of instances of a cloned resource. BZ# 1086885 Due to a timing issue, nodes that rebooted too fast became stuck in the pending state and did not rejoin the cluster. With this update, the timing issue has been resolved, nodes now join the cluster, and are reported as online. Users of pacemaker are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Appendix A. Revision History Revision History Revision 3.0-12 Wed Dec 20 2023 Lenka Spackova Fixed broken links and anchors. Revision 3.0-11 Fri Nov 12 2021 Lenka Spackova Updated Section 4.8, "Database Connectors" . Revision 3.0-10 Tue Dec 18 2018 Lenka Spackova Fixed syntax of a command in the PostgreSQL migration chapter. Revision 3.0-9 Mon Oct 30 2017 Lenka Spackova Added information regarding database connectors. Revision 3.0-8 Tue Oct 24 2017 Lenka Spackova Release of Red Hat Software Collections 3.0 Release Notes. Revision 3.0-7 Tue Oct 03 2017 Lenka Spackova Release of Red Hat Software Collections 3.0 Beta Release Notes.

Commands:
probe::nfs.aop.readpages Name probe::nfs.aop.readpages - NFS client reading multiple pages Synopsis nfs.aop.readpages Values nr_pages number of pages attempted to read in this execution ino inode number file filp argument size number of pages attempted to read in this execution rsize read size (in bytes) dev device identifier rpages read size (in pages) Description Fires when in readahead way, read several pages once

Commands:
23.3. Configuring a DHCP Client The first step for configuring a DHCP client is to make sure the kernel recognizes the network interface card. Most cards are recognized during the installation process and the system is configured to use the correct kernel module for the card. If a card is added after installation, Kudzu [6] should recognize it and prompt for the configuration of the corresponding kernel module for it. Be sure to check the Hardware Compatibility List available at http://hardware.redhat.com/hcl/ . If the network card is not configured by the installation program or Kudzu and you know which kernel module to load for it, refer to Chapter 37, Kernel Modules for details on loading kernel modules. To configure a DHCP client manually, modify the /etc/sysconfig/network file to enable networking and the configuration file for each network device in the /etc/sysconfig/network-scripts directory. In this directory, each device should have a configuration file named ifcfg-eth0 , where eth0 is the network device name. The /etc/sysconfig/network file should contain the following line: The NETWORKING variable must be set to yes if you want networking to start at boot time. The /etc/sysconfig/network-scripts/ifcfg-eth0 file should contain the following lines: A configuration file is needed for each device to be configured to use DHCP. Other options for the network script include: DHCP_HOSTNAME - Only use this option if the DHCP server requires the client to specify a hostname before receiving an IP address. (The DHCP server daemon in Red Hat Enterprise Linux does not support this feature.) PEERDNS= <answer> , where <answer> is one of the following: yes - Modify /etc/resolv.conf with information from the server. If using DHCP, then yes is the default. no - Do not modify /etc/resolv.conf . SRCADDR= <address> , where <address> is the specified source IP address for outgoing packets. USERCTL= <answer> , where <answer> is one of the following: yes - Non-root users are allowed to control this device. no - Non-root users are not allowed to control this device. If you prefer using a graphical interface, refer to Chapter 17, Network Configuration for details on using the Network Administration Tool to configure a network interface to use DHCP. Note For advanced configurations of client DHCP 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, refer to the dhclient and dhclient.conf man pages. [6] Kudzu is a hardware probing tool run at system boot time to determine what hardware has been added or removed from the system.

Commands:
NETWORKING=yes
DEVICE=eth0 BOOTPROTO=dhcp ONBOOT=yes
Chapter 49. Securing passwords with a keystore You can use a keystore to encrypt passwords that are used for communication between Business Central and KIE Server. You should encrypt both controller and KIE Server passwords. If Business Central and KIE Server are deployed to different application servers, then both application servers should use the keystore. Use Java Cryptography Extension KeyStore (JCEKS) for your keystore because it supports symmetric keys. Note If KIE Server is not configured with JCEKS, KIE Server passwords are stored in system properties in plain text form. Prerequisites KIE Server is installed in IBM WebSphere Application Server. A KIE Server user with the kie-server role has been created, as described in Section 46.1, "Creating the KIE Server group and role" . Java 8 or higher is installed. Procedure Create a JCEKS keystore. When prompted, enter the password for the KIE Server user that you created. Set the system properties listed in the following table: Table 49.1. System properties used to load a KIE Server JCEKS System property Placeholder Description kie.keystore.keyStoreURL <KEYSTORE_URL> URL for the JCEKS that you want to use, for example file:///home/kie/keystores/keystore.jceks kie.keystore.keyStorePwd <KEYSTORE_PWD> Password for the JCEKS kie.keystore.key.server.alias <KEY_SERVER_ALIAS> Alias of the key for REST services where the password is stored kie.keystore.key.server.pwd <KEY_SERVER_PWD> Password of the alias for REST services with the stored password kie.keystore.key.ctrl.alias <KEY_CONTROL_ALIAS> Alias of the key for default REST Process Automation Controller where the password is stored kie.keystore.key.ctrl.pwd <KEY_CONTROL_PWD> Password of the alias for default REST Process Automation Controller with the stored password Start KIE Server to verify the configuration.

Commands:
1.5.3. Installing Signed Packages Installation for most packages can be done safely (except kernel packages) by issuing the following command as root: rpm -Uvh <package> ... For example, to install all packages in a new directory, called updates/ , under the /tmp directory, run: For kernel packages, as root use the command in the following form: rpm -ivh <kernel-package> For example, to install kernel-2.6.32-220.el6.x86_64.rpm , type the following at a shell prompt: Once the machine has been safely rebooted using the new kernel, the old kernel may be removed using the following command: rpm -e <old-kernel-package> For instance, to remove kernel-2.6.32-206.el6.x86_64 , type: Alternatively, to install packages with Yum, run, as root, the following command: To install local packages with Yum, run, as root, the following command: Note It is not a requirement that the old kernel be removed. The default boot loader, GRUB, allows for multiple kernels to be installed, then chosen from a menu at boot time. Important Before installing any security errata, be sure to read any special instructions contained in the errata report and execute them accordingly. Refer to Section 1.5.4, "Applying the Changes" for general instructions about applying the changes made by an errata update.

Commands:
~]# rpm -Uvh /tmp/updates/*.rpm Preparing... ########################################### [100%] 1:alsa-lib ########################################### [ 33%] 2:alsa-utils ########################################### [ 67%] 3:aspell ########################################### [100%]
~]# rpm -ivh /tmp/updates/kernel-2.6.32-220.el6.x86_64.rpm Preparing... ########################################### [100%] 1:kernel ########################################### [100%]
~]# rpm -e kernel-2.6.32-206.el6.x86_64
~]# yum install kernel-2.6.32-220.el6.x86_64.rpm
~]# yum localinstall /root/updates/emacs-23.1-21.el6_2.3.x86_64.rpm
Chapter 51. Authentication and Interoperability Installing an IdM replica on RHEL 7.6 fails if the IdM master runs on RHEL 6 With a recent update of the pki-core package, certain ciphers are no longer enabled by default in the Identity Management (IdM) Certificate Authority (CA). As a consequence, setting up an IdM server with integrated CA on RHEL 7.6 as a replica of a master running on RHEL 6 fails with a CRITICAL Failed to configure CA instance error. To work around the problem, append the following entry to the end of the NSSCipherSuite parameter in the /etc/httpd/conf.d/nss.conf file: As a result, the IdM installation on RHEL 7.6 no longer fails. Note that installing a CA-less IdM replica on RHEL 7.6 works as expected even without this workaround. (BZ# 1667434 ) RADIUS proxy functionality is now also available in IdM running in FIPS mode In FIPS mode, OpenSSL disables the use of the MD5 digest algorithm by default. Consequently, because the RADIUS protocol requires MD5 to encrypt a secret between the RADIUS client and the RADIUS server, the unavailability of MD5 in FIPS mode causes the RHEL Identity Management (IdM) RADIUS proxy server to fail. If the RADIUS server is running on the same host as the IdM master, you can work around the problem and enable MD5 within the secure perimeter. To do that, create a file /etc/systemd/system/radiusd.service.d/ipa-otp.conf with the following content: To apply the change, reload the systemd configuration: and start the radiusd service: The configuration of the RADIUS proxy requires the use of a common secret between the client and the server to wrap credentials. Specify this secret in the configuration of the RADIUS proxy in RHEL IdM using the command line interface (CLI) or web UI. To do it in the CLI: (BZ# 1571754 ) Potential risk when using the default value for ldap_id_use_start_tls option When using ldap:// without TLS for identity lookups, it can pose a risk for an attack vector. Particularly a man-in-the-middle (MITM) attack which could allow an attacker to impersonate a user by altering, for example, the UID or GID of an object returned in an LDAP search. Currently, the SSSD configuration option to enforce TLS, ldap_id_use_start_tls , defaults to false . Ensure that your setup operates in a trusted environment and decide if it is safe to use unencrypted communication for id_provider = ldap . Note id_provider = ad and id_provider = ipa are not affected as they use encrypted connections protected by SASL and GSSAPI. If it is not safe to use unencrypted communication, enforce TLS by setting the ldap_id_use_start_tls option to true in the /etc/sssd/sssd.conf file. The default behavior is planned to be changed in a future release of RHEL. (JIRA:RHELPLAN-155168)

Commands:
+ecdhe_rsa_aes_128_sha,+ecdhe_rsa_aes_256_sha
/etc/systemd/system/radiusd.service.d/ipa-otp.conf [Service] Environment=OPENSSL_FIPS_NON_APPROVED_MD5_ALLOW=1
systemctl daemon-reload
systemctl start radiusd
ipa radiusproxy-add name_of_your_proxy_server --secret your_secret
Chapter 1. Building applications overview Using OpenShift Container Platform, you can create, edit, delete, and manage applications using the web console or command line interface (CLI). 1.1. Working on a project Using projects, you can organize and manage applications in isolation. You can manage the entire project lifecycle, including creating, viewing, and deleting a project in OpenShift Container Platform. After you create the project, you can grant or revoke access to a project and manage cluster roles for the users using the Developer perspective. You can also edit the project configuration resource while creating a project template that is used for automatic provisioning of new projects. Using the CLI, you can create a project as a different user by impersonating a request to the OpenShift Container Platform API. When you make a request to create a new project, the OpenShift Container Platform uses an endpoint to provision the project according to a customizable template. As a cluster administrator, you can choose to prevent an authenticated user group from self-provisioning new projects . 1.2. Working on an application 1.2.1. Creating an application To create applications, you must have created a project or have access to a project with the appropriate roles and permissions. You can create an application by using either the Developer perspective in the web console , installed Operators , or the OpenShift CLI ( oc ) . You can source the applications to be added to the project from Git, JAR files, devfiles, or the developer catalog. You can also use components that include source or binary code, images, and templates to create an application by using the OpenShift CLI ( oc ). With the OpenShift Container Platform web console, you can create an application from an Operator installed by a cluster administrator. 1.2.2. Maintaining an application After you create the application, you can use the web console to monitor your project or application metrics . You can also edit or delete the application using the web console. When the application is running, not all applications resources are used. As a cluster administrator, you can choose to idle these scalable resources to reduce resource consumption. 1.2.3. Deploying an application You can deploy your application using Deployment or DeploymentConfig objects and manage them from the web console. You can create deployment strategies that help reduce downtime during a change or an upgrade to the application. You can also use Helm , a software package manager that simplifies deployment of applications and services to OpenShift Container Platform clusters. 1.3. Using the Red Hat Marketplace The Red Hat Marketplace is an open cloud marketplace where you can discover and access certified software for container-based environments that run on public clouds and on-premises.

Commands:
5.2. Disabling Rebooting Using Ctrl+Alt+Del The action that happens in response to pressing Ctrl+Alt+Del at console is specified in the /etc/init/control-alt-delete.conf file. By default, the shutdown utility with the -r option is used to shutdown and reboot the system. To disable this action, create an overriding configuration file that specifies the exec true command, which does nothing. To do that, run the following command as root:

Commands:
~]# echo "exec true" >> /etc/init/control-alt-delete.override
2.2. What is Metadata? Metadata is data about data. A piece of metadata, called a meta object in the Teiid Designer, contains information about a specific information structure, irrespective of whatever individual data fields that may comprise that structure. Let us use the example of a very basic database, an address book. Within your address book you certainly have a field or column for the ZIP code (or postal code number). Assuming that the address book services addresses within the United States, you can surmise the following about the column or field for the ZIP code: Named ZIPCode Numeric A string Nine characters long Located in the StreetAddress table Comprised of two parts: The first five digits represent the five ZIP code numbers, the final four represent the ZIP Plus Four digits if available, or 0000 if not Formatted only in integer numeric characters. Errors will result if formatted as 631410.00 or 6314q0000 This definition represents metadata about the ZIP code data in the address book database. It abstracts information from the database itself and becomes useful to describe the content of your enterprise information systems and to determine how a column in one enterprise information source relates to another, and how those two columns could be used together for a new purpose You can think of this metadata in several contexts: What information does the metadata contain? (See Section 2.4, "Business and Technical Metadata" ) What data does the metadata represent? (See Section 2.11, "Source and View Metadata" ) How will my organization use and manage this metadata? (See Section 2.7, "Design-Time and Runtime Metadata" )

Commands:
12.8. Delegating Translators You can create a delegating translator by extending the org.teiid.translator.BaseDelegatingExecutionFactory class. Once your classes are packaged as a custom translator, you will be able to wire another translator instance into your delegating translator at runtime in order to intercept all of the calls to the delegate. This base class does not provide any functionality on its own, other than delegation. Table 12.2. Execution Properties Name Description Default delegateName Translator instance name to delegate to. As an example, consider if you are currently using "oracle" translator in your VDB and you need to intercept the calls going through this translator. You first write a custom delegating translator: Then you deploy this translator. Then modify your -vdb.xml or .vdb file: We have defined a "translator" called "oracle-interceptor", which is based on the custom translator "interceptor" from above, and supplied the translator it required to delegate to "oracle" as its delegateName. Then, we used this override translator "oracle-interceptor" in the VDB. Now any calls going into this VDB model's translator will be intercepted by your code to do whatever you need to do.

Commands:
@Translator(name="interceptor", description="interceptor") public class InterceptorExecutionFactory extends org.teiid.translator.BaseDelegatingExecutionFactory{ @Override public void getMetadata(MetadataFactory metadataFactory, C conn) throws TranslatorException { // do intercepting code here.. // If you need to call the original delegate, do not call if do not need to. // but if you did not call the delegate fulfill the method contract super.getMetadata(metadataFactory, conn); // do more intercepting code here.. } }
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <vdb name="myvdb" version="1"> <model name="mymodel"> <source name="source" translator-name="oracle-interceptor" connection-jndi-name="java:oracle-ds"/> </model> <!-- the below it is called translator overriding, where you can set different properties --> <translator name="oracle-interceptor" type="interceptor" /> <property name="delegateName" value="oracle" /> </translator> </vdb>
5.7.2. NFS and Sendmail Never put the mail spool directory, /var/spool/mail/ , on an NFS shared volume. Because NFSv2 and NFSv3 do not maintain control over user and group IDs, two or more users can have the same UID, and receive and read each other's mail. With NFSv4 using Kerberos, this is not the case, since the SECRPC_GSS kernel module does not utilize UID-based authentication.

Commands:
5.373. rhnlib 5.373.1. RHBA-2013:1212 - rhnlib bug fix update Updated rhnlib packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The rhnlib packages contain Python libraries developed specifically for interfacing with the Red Hat Network (RHN). Bug Fix BZ# 993086 The RHN Proxy did not work properly if separated from a parent by a slow enough network. Consequently, users who attempted to download larger repodata files and RPMs experienced timeouts. This update changes both RHN Proxy and Red Hat Enterprise Linux RHN Client to allow all communications to obey a configured timeout value for connections. Users of rhnlib are advised to upgrade to these updated packages, which fix this bug.

Commands:
33.11. Installing DNS Services Into an Existing Server It is possible to install DNS services into an IdM server that was originally installed without them. To do this, make sure the ipa-server-dns package is installed, and then use the ipa-dns-install utility. Configuring DNS services using ipa-dns-install follows the same principles as installing DNS with the ipa-server-install utility, as described in Section 2.3.3, "Installing a Server with Integrated DNS" . For more information about ipa-dns-install , see the ipa-dns-install (1) man page. 33.11.1. Setting up Additional Name Servers 33.11.1.1. Setting up Additional Name Servers IdM adds the newly-configured IdM DNS server to the list of DNS servers in the /etc/resolv.conf file. It is recommended to manually add other DNS servers as backup servers in case the IdM server becomes unavailable. For example: For more details about configuring /etc/resolv.conf , see the resolv.conf (5) man page.

Commands:
search example.com ; the IdM server nameserver 192.0.2.1 ; backup DNS servers nameserver 198.51.100.1 nameserver 198.51.100.2
Chapter 3. Red Hat High Availability Add-On Resources This chapter provides a summary of Red Hat High Availability resources and their operation. 3.1. Red Hat High Availability Add-On Resource Overview A cluster resource is an instance of program, data, or application to be managed by the cluster service. These resources are abstracted by agents that provide a standard interface for managing the resource in a cluster environment. This standardization is based on industry approved frameworks and classes, which makes managing the availability of various cluster resources transparent to the cluster service itself.

Commands: