mtpti5iD/redhat-docs_dataset huggingface dataset:
B.81. resource-agents B.81.1. RHBA-2010:0835 - resource-agents bug fix update Updated resource-agents packages that provide a fix for a bug are now available for Red Hat Enterprise Linux 6. The resource-agents packages contain the cluster resource agents for use by rgmanager and pacemaker. These agents allow users to build highly available services. Bug Fix BZ# 640190 The config-utils library did not work correctly with certain references, causing problems with several agents. All users of the resource-agents package are advised to upgrade to these updated packages, which address this issue and add this enhancement.

Commands:
Chapter 38. Storage No support for thin provisioning on top of RAID in a cluster While RAID logical volumes and thinly provisioned logical volumes can be used in a cluster when activated exclusively, there is currently no support for thin provisioning on top of RAID in a cluster. This is the case even if the combination is activated exclusively. Currently this combination is only supported in LVM's single machine non-clustered mode. When using thin-provisioning, it is possible to lose buffered writes to the thin-pool if it reaches capacity If a thin-pool is filled to capacity, it may be possible to lose some writes even if the pool is being grown at that time. This is because a resize operation (even an automated one) will attempt to flush outstanding I/O to the storage device prior to the resize being performed. Since there is no room in the thin-pool, the I/O operations must be errored first to allow the grow to succeed. Once the thin pool has grown, the logical volumes associated with the thin-pool will return to normal operation. As a workaround to this problem, set 'thin_pool_autoextend_threshold' and 'thin_pool_autoextend_percent' appropriately for your needs in the lvm.conf file. Do not set the threshold so high or the percent so low that your thin-pool will reach full capacity so quickly that it does not allow enough time for it to be auto-extended (or manually extended if you prefer). If you are not using over-provisioning (creating logical volumes in excess of the size of the backing thin-pool), then be prepared to remove snapshots as necessary if the thin-pool begins to near capacity.

Commands:
Chapter 16. Enabling kdump For your RHEL 9 systems, you can configure enabling or disabling the kdump functionality on a specific kernel or on all installed kernels. However, you must routinely test the kdump functionality and validate its working status. 16.1. Enabling kdump for all installed kernels The kdump service starts by enabling kdump.service after the kexec tool is installed. You can enable and start the kdump service for all kernels installed on the machine. Prerequisites You have administrator privileges. Procedure Add the crashkernel= command-line parameter to all installed kernels: xxM is the required memory in megabytes. Enable the kdump service: Verification Check that the kdump service is running: 16.2. Enabling kdump for a specific installed kernel You can enable the kdump service for a specific kernel on the machine. Prerequisites You have administrator privileges. Procedure List the kernels installed on the machine. Add a specific kdump kernel to the system's Grand Unified Bootloader (GRUB) configuration. For example: xxM is the required memory reserve in megabytes. Enable the kdump service. Verification Check that the kdump service is running. 16.3. Disabling the kdump service You can stop the kdump.service and disable the service from starting on your RHEL 9 systems. Prerequisites Fulfilled requirements for kdump configurations and targets. For details, see Supported kdump configurations and targets . All configurations for installing kdump are set up according to your needs. For details, see Installing kdump . Procedure To stop the kdump service in the current session: To disable the kdump service: Warning It is recommended to set kptr_restrict=1 as default. When kptr_restrict is set to (1) as default, the kdumpctl service loads the crash kernel regardless of whether the Kernel Address Space Layout ( KASLR ) is enabled. If kptr_restrict is not set to 1 and KASLR is enabled, the contents of /proc/kore file are generated as all zeros. The kdumpctl service fails to access the /proc/kcore file and load the crash kernel. The kexec-kdump-howto.txt file displays a warning message, which recommends you to set kptr_restrict=1 . Verify for the following in the sysctl.conf file to ensure that kdumpctl service loads the crash kernel: Kernel kptr_restrict=1 in the sysctl.conf file. Additional resources Managing systemd

Commands:
grubby --update-kernel=ALL --args="crashkernel=xxM"
systemctl enable --now kdump.service
systemctl status kdump.service ○ kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled) Active: active (live)
ls -a /boot/vmlinuz- * /boot/vmlinuz-0-rescue-2930657cd0dc43c2b75db480e5e5b4a9 /boot/vmlinuz-4.18.0-330.el8.x86_64 /boot/vmlinuz-4.18.0-330.rt7.111.el8.x86_64
grubby --update-kernel= vmlinuz-4.18.0-330.el8.x86_64 --args="crashkernel= xxM "
systemctl enable --now kdump.service
systemctl status kdump.service ○ kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled) Active: active (live)
systemctl stop kdump.service
systemctl disable kdump.service
Chapter 3. Getting started This chapter guides you through the steps to set up your environment and run a simple messaging program. 3.1. Prerequisites You must complete the installation procedure for your environment. You must have an AMQP 1.0 message broker listening for connections on interface localhost and port 5672 . It must have anonymous access enabled. For more information, see Starting the broker . You must have a queue named examples . For more information, see Creating a queue . 3.2. Running Hello World on Red Hat Enterprise Linux The Hello World example creates a connection to the broker, sends a message containing a greeting to the examples queue, and receives it back. On success, it prints the received message to the console. Change to the examples directory and run the helloworld.js example. USD cd <install-dir> /node_modules/rhea/examples USD node helloworld.js Hello World! 3.3. Running Hello World on Microsoft Windows The Hello World example creates a connection to the broker, sends a message containing a greeting to the examples queue, and receives it back. On success, it prints the received message to the console. Change to the examples directory and run the helloworld.js example. > cd <install-dir> /node_modules/rhea/examples > node helloworld.js Hello World!

Commands:
cd <install-dir> /node_modules/rhea/examples node helloworld.js Hello World!
> cd <install-dir> /node_modules/rhea/examples > node helloworld.js Hello World!
6.14. Miscellaneous Cluster Configuration This section describes using the ccs command to configure the following: Section 6.14.1, "Cluster Configuration Version" Section 6.14.2, "Multicast Configuration" Section 6.14.3, "Configuring a Two-Node Cluster" Section 6.14.4, "Logging" Section 6.14.5, "Configuring Redundant Ring Protocol" You can also use the ccs command to set advanced cluster configuration parameters, including totem options, dlm options, rm options and cman options. For information on setting these parameters see the ccs (8) man page and the annotated cluster configuration file schema at /usr/share/doc/cman-X.Y.ZZ/cluster_conf.html . To view a list of the miscellaneous cluster attributes that have been configured for a cluster, execute the following command: 6.14.1. Cluster Configuration Version A cluster configuration file includes a cluster configuration version value. The configuration version value is set to 1 by default when you create a cluster configuration file and it is automatically incremented each time you modify your cluster configuration. However, if you need to set it to another value, you can specify it with the following command: You can get the current configuration version value on an existing cluster configuration file with the following command: To increment the current configuration version value by 1 in the cluster configuration file on every node in the cluster, execute the following command:

Commands:
ccs -h host --lsmisc
ccs -h host --setversion n
ccs -h host --getversion
ccs -h host --incversion
Appendix A. Using your subscription AMQ is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. A.1. Accessing your account Procedure Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. A.2. Activating a subscription Procedure Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. A.3. Downloading release files To access .zip, .tar.gz, and other release files, use the customer portal to find the relevant files for download. If you are using RPM packages or the Red Hat Maven repository, this step is not required. Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ product. The Software Downloads page opens. Click the Download link for your component. A.4. Registering your system for packages To install RPM packages for this product on Red Hat Enterprise Linux, your system must be registered. If you are using downloaded release files, this step is not required. Procedure Go to access.redhat.com . Navigate to Registration Assistant . Select your OS version and continue to the page. Use the listed command in your system terminal to complete the registration. For more information about registering your system, see one of the following resources: Red Hat Enterprise Linux 7 - Registering the system and managing subscriptions Red Hat Enterprise Linux 8 - Registering the system and managing subscriptions Revised on 2023-05-17 11:27:00 UTC

Commands:
Chapter 111. Demoting or promoting hidden replicas After a replica has been installed, you can configure whether the replica is hidden or visible. For details about hidden replicas, see The hidden replica mode . Prerequisites Ensure that the replica is not the DNSSEC key master. If it is, move the service to another replica before making this replica hidden. Ensure that the replica is not a CA renewal server. If it is, move the service to another replica before making this replica hidden. For details, see Changing and resetting IdM CA renewal server . Procedure To hide a replica: To make a replica visible again: To view a list of all the hidden replicas in your topology: If all of your replicas are enabled, the command output does not mention hidden replicas.

Commands:
ipa server-state replica.idm.example.com --state=hidden
ipa server-state replica.idm.example.com --state=enabled
ipa config-show
Common object reference OpenShift Container Platform 4.14 Reference guide common API objects Red Hat OpenShift Documentation Team

Commands:
<quantity> ::= <signedNumber><suffix>
(Note that <suffix> may be empty, from the "" case in <decimalSI>.)
(International System of units; See: http://physics.nist.gov/cuu/Units/binary.html)
(Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.)
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.Object `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
type MyAPIObject struct { runtime.TypeMeta `json:",inline"` MyPlugin runtime.RawExtension `json:"myPlugin"` }
type PluginA struct { AOption string `json:"aOption"` }
{ "kind":"MyAPIObject", "apiVersion":"v1", "myPlugin": { "kind":"PluginA", "aOption":"foo", }, }
Chapter 15. Integration Options Red Hat Single Sign-On (RH-SSO) is a single sign-on solution that you can use to secure your browser applications with your REST web services and Git access. When you integrate Red Hat Process Automation Manager with RH-SSO, you create an SSO and identity management (IDM) environment for Red Hat Process Automation Manager. The session management feature of RH-SSO enables you to use a single authentication for different Red Hat Process Automation Manager environments on the internet. The following chapters describe how you can integrate RH-SSO with Red Hat Process Automation Manager: Chapter 18, Authenticating Business Central through RH-SSO To authenticate Red Hat Process Automation Manager through an RH-SSO server, you must secure both the Red Hat Process Automation Manager web client (Business Central) and remote services through RH-SSO.This integration enables you to connect to Red Hat Process Automation Manager through RH-SSO using either Business Central or a remote service consumer. Chapter 19, Authenticating KIE Server through RH-SSO To authenticate KIE Server through an RH-SSO server, you must secure the remote services provided by KIE Server. Doing this enables any remote Red Hat Process Automation Manager service consumer (user or a service) to authenticate through RH-SSO. Note that KIE Server does not have a web interface. Chapter 20, Authenticating third-party clients through RH-SSO If Business Central or KIE Server are using RH-SSO, third-party clients must authenticate themselves using RH-SSO. After authentication, they can consume the remote service endpoints provided by Business Central and KIE Server, such as the REST API or remote file system services. To facilitate LDAP integration with Red Hat Process Automation Manager, consider using RH-SSO with LDAP. For information, see the "LDAP and Active Directory" section of the Red Hat Single Sign-On Server Administration Guide .

Commands:
A.7. Visual Tracing (using PCP-GUI and pmchart) Through the use of of the PCP-GUI package, you can use the pmchart graphical utility to plot performance metric values into graphs. The pmchart utility allows multiple charts to be displayed simultaneously, with metrics being sourced from one or more live hosts with alternative options to use metric data from PCP log archives as a source of historical data. When you open pmchart , the PCP charts GUI displays. On the bottom of the display is the pmtime VCR-like controls. The start/pause button allows you to control the interval in which the metric data is polled and in the event that you are using historical data, the date and time for the metrics. From the File -> New Chart option in the toolbar, you can select a metric from both the local machine and remote machines by specifying their host name or address and then selecting performance metrics from the remote hosts. Advanced configuration options include the ability to manually set the axis values for the chart and to manually choose the color of the plots. There are multiple options to take images or record the views created in pmchart . You can save an image of the current view through the File -> Export option in the toolbar. Recording is made available by the Record -> Start option in the toolbar and these recordings can be stopped at a later time using Record -> Stop . After the recording has been terminated, the recorded metrics are archived to be viewed at a later date. You can customize the pmchart interface to display the data from performance metrics in multiple ways, including line plot, bar graphs and utilization graphs. In pmchart , the main configuration file known as the "view" allows the metadata associated with one or more charts to be saved. This metadata describes all of the chart's aspects including the metrics used and the chart columns. You can create a custom "view" configuration which can be saved using File -> Save View and then loaded again at a later time. For more information about view configuration files and their syntax, see the pmchart (1) man page. The following example pmchart view configuration describes a stacking chart graph showing the total number of glocks for the mounted GFS2 file system loop1 using the gfs2.glocks metric. We also have a plot graph underneath which plots the average latency for the glock grant, demote and queue requests for the same file system instance "loop1".

Commands:
kmchart version 1 chart title "Total number of Glocks /loop1" style stacking antialiasing off plot legend "Shared" metric gfs2.glocks.shared instance "loop1" plot legend "Unlocked" metric gfs2.glocks.unlocked instance "loop1" plot legend "Deferred" metric gfs2.glocks.deferred instance "loop1" plot legend "Exclusive"metric gfs2.glocks.exclusive instance "loop1" chart title "Average Glock Latency (usecs) /loop1" style plot antialiasing off plot legend "Demote" metric gfs2.latency.demote.all instance "loop1" plot legend "Grant" metric gfs2.latency.grant.all instance "loop1" plot legend "Queue" metric gfs2.latency.queue.all instance "loop1"
6.3. Configuring Host Names Using hostnamectl The hostnamectl tool is provided for administering the three separate classes of host names in use on a given system. 6.3.1. View All the Host Names To view all the current host names, enter the following command: The status option is implied by default if no option is given. 6.3.2. Set All the Host Names To set all the host names on a system, enter the following command as root : This will alter the pretty, static, and transient host names alike. The static and transient host names will be simplified forms of the pretty host name. Spaces will be replaced with " - " and special characters will be removed. 6.3.3. Set a Particular Host Name To set a particular host name, enter the following command as root with the relevant option: Where option is one or more of: --pretty , --static , and --transient . If the --static or --transient options are used together with the --pretty option, the static and transient host names will be simplified forms of the pretty host name. Spaces will be replaced with " - " and special characters will be removed. If the --pretty option is not given, no simplification takes place. When setting a pretty host name, remember to use the appropriate quotation marks if the host name contains spaces or a single quotation mark. For example: 6.3.4. Clear a Particular Host Name To clear a particular host name and allow it to revert to the default, enter the following command as root with the relevant option: Where "" is a quoted empty string and where option is one or more of: --pretty , --static , and --transient . 6.3.5. Changing Host Names Remotely To execute a hostnamectl command on a remote system, use the -H, --host option as follows: Where hostname is the remote host you want to configure. The username is optional. The hostnamectl tool will use SSH to connect to the remote system.

Commands:
~]USD hostnamectl status
~]# hostnamectl set-hostname name
~]# hostnamectl set-hostname name [ option ... ]
~]# hostnamectl set-hostname "Stephen's notebook" --pretty
~]# hostnamectl set-hostname "" [ option ... ]
~]# hostnamectl set-hostname -H [ username ]@ hostname
5.211. nmap 5.211.1. RHBA-2012:0817 - nmap bug fix and enhancement update Updated nmap packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The nmap packages provide a network exploration utility and a security scanner. The nmap package has been upgraded to version 5.51, which provides a number of bug fixes and enhancements over the version and improves performance. (BZ# 512042 ) Bug Fix BZ# 813734 Prior to this update, the nping man page listed "--md" for the "More Fragments" option. This update corrects this misprint and now correctly lists "--mf" for this option. All users of nmap are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
4.4. Apache HTTP Server Below is a list of changes for the Apache HTTP Server that are noteworthy when migrating to Red Hat Enterprise Linux 6: The mod_file_cache , mod_mem_cache , and mod_imagemap modules are no longer supported. The Charset=UTF-8 option has been added to the default IndexOptions directive. If directory listings with a non UTF-8 character set are required (such as those produced by mod_autoindex ), this option must be changed. The distcache distributed session cache is no longer supported in mod_ssl . The default location of the process ID (pid) file has moved from /var/run to /var/run/httpd . The mod_python package is no longer included as upstream development has ceased. Red Hat Enterprise Linux 6 provides mod_wsgi as an alternative, with support for Python scripting using the WSGI interface.

Commands:
Chapter 8. Identity Management security settings Learn more about security-related features of Identity Management. 8.1. How Identity Management applies default security settings By default, Identity Management (IdM) uses the system-wide crypto policy. The benefit of this policy is that you do not need to harden individual IdM components manually. Important Red Hat recommends that you use the system-wide crypto policy. Changing individual security settings can break components of IdM. Additional resources See the crypto-policies(7) man page on your system 8.2. Anonymous LDAP binds in Identity Management By default, anonymous binds to the Identity Management (IdM) LDAP server are enabled. Anonymous binds can expose certain configuration settings or directory values. However, some utilities, such as realmd , or older RHEL clients require anonymous binds enabled to discover domain settings when enrolling a client. Additional resources Disabling anonymous binds 8.3. Disabling anonymous binds You can disable anonymous binds on the Identity Management (IdM) 389 Directory Server instance by using LDAP tools to reset the nsslapd-allow-anonymous-access attribute. These are the valid values for the nsslapd-allow-anonymous-access attribute: on : allows all anonymous binds (default) rootdse : allows anonymous binds only for root DSE information off : disallows any anonymous binds Red Hat does not recommend completely disallowing anonymous binds by setting the attribute to off , because this also blocks external clients from checking the server configuration. LDAP and web clients are not necessarily domain clients, so they connect anonymously to read the root DSE file to get connection information. By changing the value of the nsslapd-allow-anonymous-access attribute to rootdse , you allow access to the root DSE and server configuration without any access to the directory data. Warning Certain clients rely on anonymous binds to discover IdM settings. Additionally, the compat tree can break for legacy clients that are not using authentication. Perform this procedure only if your clients do not require anonymous binds. Prerequisites You can authenticate as the Directory Manager to write to the LDAP server. You can authenticate as the root user to restart IdM services. Procedure Change the nsslapd-allow-anonymous-access attribute to rootdse . Restart the 389 Directory Server instance to load the new setting. Verification Display the value of the nsslapd-allow-anonymous-access attribute. Additional resources nsslapd-allow-anonymous-access in Directory Server 11 documentation Anonymous LDAP binds in Identity Management

Commands:
ldapmodify -x -D "cn=Directory Manager" -W -h server.example.com -p 389 Enter LDAP Password: dn: cn=config changetype: modify replace: nsslapd-allow-anonymous-access nsslapd-allow-anonymous-access: rootdse modifying entry "cn=config"
systemctl restart dirsrv.target
ldapsearch -x -D "cn=Directory Manager" -b cn=config -W -h server.example.com -p 389 nsslapd-allow-anonymous-access | grep nsslapd-allow-anonymous-access Enter LDAP Password: requesting: nsslapd-allow-anonymous-access nsslapd-allow-anonymous-access: rootdse