mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 16. Configuring kdump in the web console You can set up and test the kdump configuration by using the RHEL 8 web console. The web console can enable the kdump service at boot time. With the web console, you can configure the reserved memory for kdump and to select the vmcore saving location in an uncompressed or compressed format. 16.1. Configuring kdump memory usage and target location in web console You can configure the memory reserve for the kdump kernel and also specify the target location to capture the vmcore dump file with the RHEL web console interface. Prerequisites The web console must be installed and accessible. For details, see Installing the web console . Procedure In the web console, open the Kernel dump tab and start the kdump service by setting the Kernel crash dump switch to on. Configure the kdump memory usage in the terminal, for example: Restart the system to apply the changes. In the Kernel dump tab, click Edit at the end of the Crash dump location field. Specify the target directory for saving the vmcore dump file: For a local filesystem, select Local Filesystem from the drop-down menu. For a remote system by using the SSH protocol, select Remote over SSH from the drop-down menu and specify the following fields: In the Server field, enter the remote server address. In the SSH key field, enter the SSH key location. In the Directory field, enter the target directory. For a remote system by using the NFS protocol, select Remote over NFS from the drop-down menu and specify the following fields: In the Server field, enter the remote server address. In the Export field, enter the location of the shared folder of an NFS server. In the Directory field, enter the target directory. Note You can reduce the size of the vmcore file by selecting the Compression checkbox. Optional: Display the automation script by clicking View automation script . A window with the generated script opens. You can browse a shell script and an Ansible playbook generation options tab. Optional: Copy the script by clicking Copy to clipboard . You can use this script to apply the same configuration on multiple machines. Verification Click Test configuration . Click Crash system under Test kdump settings . Warning When you start the system crash, the kernel operation stops and results in a system crash with data loss. Additional resources Supported kdump targets

Commands:
sudo grubby --update-kernel ALL --args crashkernel=512M
40.2.3. Separating Kernel and User-space Profiles By default, kernel mode and user mode information is gathered for each event. To configure OProfile not to count events in kernel mode for a specific counter, execute the following command: Execute the following command to start profiling kernel mode for the counter again: To configure OProfile not to count events in user mode for a specific counter, execute the following command: Execute the following command to start profiling user mode for the counter again: When the OProfile daemon writes the profile data to sample files, it can separate the kernel and library profile data into separate sample files. To configure how the daemon writes to sample files, execute the following command as root: <choice> can be one of the following: none - do not separate the profiles (default) library - generate per-application profiles for libraries kernel - generate per-application profiles for the kernel and kernel modules all - generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules If --separate=library is used, the sample file name includes the name of the executable as well as the name of the library.

Commands:
opcontrol --event= <event-name> : <sample-rate> : <unit-mask> :0
opcontrol --event= <event-name> : <sample-rate> : <unit-mask> :1
opcontrol --event= <event-name> : <sample-rate> : <unit-mask> : <kernel> :0
opcontrol --event= <event-name> : <sample-rate> : <unit-mask> : <kernel> :1
opcontrol --separate= <choice>
7.166. ppp 7.166.1. RHBA-2015:0685 - ppp bug fix and enhancement update Updated ppp packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The ppp packages contain the Point-to-Point Protocol (PPP) daemon and documentation for PPP support. The PPP protocol provides a method for transmitting datagrams over serial point-to-point links. PPP is usually used to dial in to an Internet Service Provider (ISP) or other organization over a modem and phone line. Bug Fixes BZ# 906912 Previously, when the radius client configuration file contained an option not recognized by the PPP radius plug-in, an error was reported. To fix this bug, the parser for the configuration file has been amended to skip unrecognized options. Now, unknown options are skipped without reporting errors. BZ# 922769 Prior to this update, the ppp package incorrectly required the logrotate package. Consequently, the logrotate package could not be easily uninstalled. To fix this bug, the hard dependency on the logrotate package has been removed, and it is now possible to easily uninstall the logrotate package. BZ# 1197792 Previously, the Point-to-Point Protocol daemon (PPPD) terminated unexpectedly when the pppol2tp plug-in was used, and the PPPD command line contained a dump option. To fix this bug, the initialization of the variable containing textual representation of the file descriptor passed to the pppol2tp plug-in has been corrected. Now, the variable initializes properly, and PPPD no longer crashes in this scenario. Enhancement BZ# 815128 The ppp package now includes two new plug-ins (pppol2tp.so and openl2tp.so) that allow the use of kernel mode l2tp in dependent packages. As a result, it is now possible to leverage in-kernel pppo-l2tp protocol implementation by xl2tpd and openl2tpd. Users of ppp are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 3. Distribution selection Red Hat provides several distributions of Red Hat build of OpenJDK. This module helps you select the distribution that is right for your needs. All distributions of OpenJDK contain the JDK Flight Recorder (JFR) feature. This feature produces diagnostics and profiling data that can be consumed by other applications, such as JDK Mission Control (JMC). Red Hat build of OpenJDK RPMs for RHEL 8 RPM distributions of Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 for RHEL 8. Red Hat build of OpenJDK 8 JRE portable archive for RHEL Portable Red Hat build of OpenJDK 8 JRE archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 8 portable archive for RHEL Portable Red Hat build of OpenJDK 8 archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 11 JRE portable archive for RHEL Portable Red Hat build of OpenJDK 11 JRE archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 11 portable archive for RHEL Portable Red Hat build of OpenJDK 11 archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 17 JRE portable archive for RHEL Portable Red Hat build of OpenJDK 17 JRE archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 17 portable archive for RHEL Portable Red Hat build of OpenJDK 17 archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 21 JRE portable archive for RHEL Portable Red Hat build of OpenJDK 21 JRE archive distribution for RHEL 8 and 9 hosts. Red Hat build of OpenJDK 21 portable archive for RHEL Portable Red Hat build of OpenJDK 21 archive distribution for RHEL 8 and 9 hosts. Red Hat build of OpenJDK archive for Windows Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 distributions for all supported Windows hosts. Recommended for cases where multiple Red Hat build of OpenJDK versions may be installed on a host. This distribution includes the following: Java Web Start Mission Control Red Hat build of OpenJDK installers for Windows Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 MSI installers for all supported Windows hosts. Optionally installs Java Web Start and sets environment variables. Suitable for system wide installs of a single Red Hat build of OpenJDK version. Additional resources For more information about the JDK Flight Recorder (JFR), see Introduction to JDK Flight Recorder . For more information about the JDK Flight Recorder (JFR), see Introduction to JDK Mission Control . JDK Mission Control is available for RHEL with Red Hat Software Collections 3.2 . Where is JDK Mission Control (JMC) in JDK 21? Revised on 2024-05-09 14:48:08 UTC

Commands:
B.62.2. RHSA-2010:0979 - Moderate: openssl security update Updated openssl packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols, as well as a full-strength, general purpose cryptography library. CVE-2010-4180 A ciphersuite downgrade flaw was found in the OpenSSL SSL/TLS server code. A remote attacker could possibly use this flaw to change the ciphersuite associated with a cached session stored on the server, if the server enabled the SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG option, possibly forcing the client to use a weaker ciphersuite after resuming the session. Note Note that with this update, setting the SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG option has no effect and this bug workaround can no longer be enabled. All OpenSSL users should upgrade to these updated packages, which contain a backported patch to resolve this issue. For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.

Commands:
12.24. Object Translator 12.24.1. Object Translator The Object translator is a bridge for reading Java objects from external sources, such as Map Cache, and delivering them to the engine for processing. To assist in providing that bridge, the OBJECTTABLE function must be used to transform the Java object into rows and columns. These are the types of object translators: map-cache - supports a local cache that is of type Map and using Key searching. This translator is implemented by the org.teiid.translator.object.ObjectExecutionFactory class. Note See the Red Hat JBoss Data Grid resource adapter for this translator. It can be configured to look up the cache container through JNDI or created sources (such as ConfigurationFileName or RemoteServerList). 12.24.2. Object Translator: Execution Properties The following execution properties are relevant to translating from JBoss Data Grid. Table 12.20. Execution Properties Name Description Required Default SupportsLuceneSearching Setting to true assumes your objects are annotated and Hibernate/Lucene will be used to search the cache N false 12.24.3. Object Translator: Supported Capabilities The following are the connector capabilities when Key Searching is used: SELECT command CompareCriteria - only EQ InCriteria The following are the connector capabilities when Hibernate/Lucene Searching is enabled: SELECT command CompareCriteria - EQ, NE, LT, GT, etc. InCriteria OrCriteria And/Or Criteria Like Criteria INSERT, UPDATE, DELETE 12.24.4. Object Translator: Usage Retrieve objects from a cache and transform into rows and columns. The primary object returned by the cache should have a name in source of 'this'. All other columns will have their name in source (which defaults to the column name) interpreted as the path to the column value from the primary object. All columns that are not the primary key nor covered by a lucene index should be marked as SEARCHABLE 'Unsearchable'.

Commands:
C.6. Glock tracepoints The tracepoints are also designed to be able to confirm the correctness of the cache control by combining them with the blktrace output and with knowledge of the on-disk layout. It is then possible to check that any given I/O has been issued and completed under the correct lock, and that no races are present. The gfs2_glock_state_change tracepoint is the most important one to understand. It tracks every state change of the glock from initial creation right through to the final demotion which ends with gfs2_glock_put and the final NL to unlocked transition. The l (locked) glock flag is always set before a state change occurs and will not be cleared until after it has finished. There are never any granted holders (the H glock holder flag) during a state change. If there are any queued holders, they will always be in the W (waiting) state. When the state change is complete then the holders may be granted which is the final operation before the l glock flag is cleared. The gfs2_demote_rq tracepoint keeps track of demote requests, both local and remote. Assuming that there is enough memory on the node, the local demote requests will rarely be seen, and most often they will be created by umount or by occasional memory reclaim. The number of remote demote requests is a measure of the contention between nodes for a particular inode or resource group. When a holder is granted a lock, gfs2_promote is called, this occurs as the final stages of a state change or when a lock is requested which can be granted immediately due to the glock state already caching a lock of a suitable mode. If the holder is the first one to be granted for this glock, then the f (first) flag is set on that holder. This is currently used only by resource groups.

Commands:
Chapter 6. Installing a three-node cluster on vSphere In OpenShift Container Platform version 4.18, you can install a three-node cluster on VMware vSphere. A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster using either installer-provisioned or user-provisioned infrastructure. 6.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... If you are deploying a cluster with user-provisioned infrastructure: Configure your application ingress load balancer to route HTTP and HTTPS traffic to the control plane nodes. In a three-node cluster, the Ingress Controller pods run on the control plane nodes. For more information, see the "Load balancing requirements for user-provisioned infrastructure". After you create the Kubernetes manifest files, make sure that the spec.mastersSchedulable parameter is set to true in cluster-scheduler-02-config.yml file. You can locate this file in <installation_directory>/manifests . For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on vSphere with user-provisioned infrastructure". Do not create additional worker nodes. Example cluster-scheduler-02-config.yml file for a three-node cluster apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {} 6.2. steps Installing a cluster on vSphere with customizations Installing a cluster on vSphere with user-provisioned infrastructure

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {}
3.8. Choose a Boot Method You can use several methods to boot Red Hat Enterprise Linux. Installing from a DVD requires that you have purchased a Red Hat Enterprise Linux product, you have a Red Hat Enterprise Linux 6.9 DVD, and you have a DVD drive on a system that supports booting from it. Refer to Chapter 2, Making Media for instructions to make an installation DVD. Your BIOS may need to be changed to allow booting from your DVD/CD-ROM drive. For more information about changing your BIOS, refer to Section 7.1.1, "Booting the Installation Program on x86, AMD64, and Intel 64 Systems" . Other than booting from an installation DVD, you can also boot the Red Hat Enterprise Linux installation program from minimal boot media in the form of a bootable CD or USB flash drive. After you boot the system with a piece of minimal boot media, you complete the installation from a different installation source, such as a local hard drive or a location on a network. Refer to Section 2.2, "Making Minimal Boot Media" for instructions on making boot CDs and USB flash drives. Finally, you can boot the installer over the network from a preboot execution environment (PXE) server. Refer to Chapter 30, Setting Up an Installation Server . Again, after you boot the system, you complete the installation from a different installation source, such as a local hard drive or a location on a network.

Commands:
Chapter 1. Introduction JBoss EAP 7 can be used with the Microsoft Azure platform, as long as you use it within the specific supported configurations for running JBoss EAP in Azure. If you are configuring a clustered JBoss EAP environment, you must apply the specific configurations necessary to use JBoss EAP clustering features in Azure. This guide details the supported configurations of using JBoss EAP in Microsoft Azure, as well as the specific JBoss EAP configuration required to enable JBoss EAP clustering in Azure. All other JBoss EAP features not mentioned in this guide operate normally in Azure as with any other JBoss EAP installation. See the other JBoss EAP documentation for non-Azure-specific configuration instructions. 1.1. Subscription models for JBoss EAP on Azure You can choose between two subscription models for deploying JBoss EAP on Azure: bring your own subscription (BYOS) and pay-as-you-go (PAYG). The following are the differences between the two offerings: BYOS If you already have an existing Red Hat subscription, you can use it for deploying JBoss EAP on Azure with the BYOS model. For more information, see About Red Hat Cloud Access . PAYG If you do not have an existing Red Hat subscription, you can choose to pay based on the number of computing resources you used by using the PAYG model. 1.2. About Red Hat Cloud Access If you have an existing Red Hat subscription, Red Hat Cloud Access provides support for JBoss EAP on Red Hat certified cloud infrastructure providers, such as Amazon EC2 and Microsoft Azure. Red Hat Cloud Access allows you to cost-effectively move your subscriptions between traditional servers and public cloud-based resources. You can find more information about Red Hat Cloud Access on the Customer Portal .

Commands:
Chapter 13. Configuring Applications for Single Sign-On Some common applications, such as browsers and email clients, can be configured to use Kerberos tickets, SSL certifications, or tokens as a means of authenticating users. The precise procedures to configure any application depend on that application itself. The examples in this chapter (Mozilla Thunderbird and Mozilla Firefox) are intended to give you an idea of how to configure a user application to use Kerberos or other credentials. 13.1. Configuring Firefox to Use Kerberos for Single Sign-On Firefox can use Kerberos for single sign-on (SSO) to intranet sites and other protected websites. For Firefox to use Kerberos, it first has to be configured to send Kerberos credentials to the appropriate KDC. Even after Firefox is configured to pass Kerberos credentials, it still requires a valid Kerberos ticket to use. To generate a Kerberos ticket, use the kinit command and supply the user password for the user on the KDC. To configure Firefox to use Kerberos for SSO: In the address bar of Firefox, type about:config to display the list of current configuration options. In the Filter field, type negotiate to restrict the list of options. Double-click the network.negotiate-auth.trusted-uris entry. Enter the name of the domain against which to authenticate, including the preceding period (.). If you want to add multiple domains, enter them in a comma-separated list. Figure 13.1. Manual Firefox Configuration Important It is not recommended to configure delegation using the network.negotiate-auth.delegation-uris entry in the Firefox configuration options because this enables every Kerberos-aware server to act as the user. Note For more information, see Configuring the Browser for Kerberos Authentication in the Linux Domain Identity, Authentication, and Policy Guide ..

Commands:
[jsmith@host ~] USD kinit Password for jsmith@EXAMPLE.COM:
1.2. Installing Querying for Red Hat JBoss Data Grid In Red Hat JBoss Data Grid, the JAR files required to perform queries are packaged within the JBoss Data Grid Library and Remote Client-Server mode downloads. For details about downloading and installing JBoss Data Grid, see the Getting Started Guide 's Download and Install JBoss Data Grid chapter. 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: