mtpti5iD/redhat-docs_dataset huggingface dataset:
21.3. JMX Statistic Levels JMX statistics can be enabled at two levels: At the cache level, where management information is generated by individual cache instances. At the CacheManager level, where the CacheManager is the entity that governs all cache instances created from it. As a result, the management information is generated for all these cache instances instead of individual caches. Important In Red Hat JBoss Data Grid, statistics are enabled by default in Remote Client-Server mode and disabled by default for Library mode. While statistics are useful in assessing the status of JBoss Data Grid, they adversely affect performance and must be disabled if they are not required. Report a bug

Commands:
12.4. Accessing Delegated Services For both services and hosts, if a client has delegated authority, it can obtain a keytab for that principal on the local machine. For services, this has the format service/hostname@REALM . For hosts, the service is host . With kinit , use the -k option to load a keytab and the -t option to specify the keytab. For example, to access a host: To access a service:

Commands:
kinit -kt /etc/krb5.keytab host/ipa.example.com@EXAMPLE.COM
kinit -kt /etc/httpd/conf/krb5.keytab http/ipa.example.com@EXAMPLE.COM
6.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. The following types are used with BIND. Different types allow you to configure flexible access: named_zone_t Used for master zone files. Other services cannot modify files of this type. named can only modify files of this type if the named_write_master_zones Boolean is enabled. named_cache_t By default, named can write to files labeled with this type, without additional Booleans being set. Files copied or created in the /var/named/slaves/ , /var/named/dynamic/ and /var/named/data/ directories are automatically labeled with the named_cache_t type. named_var_run_t Files copied or created in the /var/run/bind/ , /var/run/named/ , and /var/run/unbound/ directories are automatically labeled with the named_var_run_t type. named_conf_t BIND-related configuration files, usually stored in the /etc/ directory, are automatically labeled with the named_conf_t type. named_exec_t BIND-related executable files, usually stored in the /usr/sbin/ directory, are automatically labeled with the named_exec_t type. named_log_t BIND-related log files, usually stored in the /var/log/ directory, are automatically labeled with the named_log_t type. named_initrc_exec_t Executable BIND-related files in the /etc/rc.d/init.d/ directory are automatically labeled with the named_initrc_exec_t type.

Commands:
2.2. Setting a Password for the Piranha Configuration Tool Before using the Piranha Configuration Tool for the first time on the primary LVS router, you must restrict access to it by creating a password. To do this, login as root and issue the following command: /usr/sbin/piranha-passwd After entering this command, create the administrative password when prompted. Warning For a password to be more secure, it should not contain proper nouns, commonly used acronyms, or words in a dictionary from any language. Do not leave the password unencrypted anywhere on the system. If the password is changed during an active Piranha Configuration Tool session, the administrator is prompted to provide the new password.

Commands:
Chapter 7. Downgrading Red Hat Quay Red Hat Quay only supports rolling back, or downgrading, to z-stream versions, for example, 3.12.3 3.12.2. Rolling back to y-stream versions (3 3.12) is not supported. This is because Red Hat Quay updates might contain database schema upgrades that are applied when upgrading to a new version of Red Hat Quay. Database schema upgrades are not considered backwards compatible. Important Downgrading to z-streams is neither recommended nor supported by either Operator based deployments or virtual machine based deployments. Downgrading should only be done in extreme circumstances. The decision to rollback your Red Hat Quay deployment must be made in conjunction with the Red Hat Quay support and development teams. For more information, contact Red Hat Quay support.

Commands:
11.6. Disabling and Re-enabling Service Entries Active services can be accessed by other services, hosts, and users within the domain. There can be situations when it is necessary to remove a host or a service from activity. However, deleting a service or a host removes the entry and all the associated configuration, and it removes it permanently. 11.6.1. Disabling Service Entries Disabling a service prevents domain users from access it without permanently removing it from the domain. This can be done by using the service-disable command. For a service, specify the principal for the service. For example: Important Disabling a host entry not only disables that host. It disables every configured service on that host as well. 11.6.2. Re-enabling and Services Disabling a service essentially kills its current, active keytabs. Removing the keytabs effectively removes the service from the IdM domain without otherwise touching its configuration entry. To re-enable a service, simply use the ipa-getkeytab command. The -s option sets which IdM server to request the keytab, -p gives the principal name, and -k gives the file to which to save the keytab. For example, requesting a new HTTP keytab: If the ipa-getkeytab command is run on an active IdM client or server, then it can be run without any LDAP credentials ( -D and -w ). The IdM user uses Kerberos credentials to authenticate to the domain. To run the command directly on a disabled host, then supply LDAP credentials to authenticate to the IdM server. The credentials should correspond to the host or service which is being re-enabled.

Commands:
[jsmith@ipaserver ~]USD kinit admin ipa service-disable http/server.example.com
ipa-getkeytab -s ipaserver.example.com -p HTTP/server.example.com -k /etc/httpd/conf/krb5.keytab -e aes256-cts
Chapter 12. Storage Domains 12.1. Storage Domain Elements The storagedomains collection provides information about the storage domains in a Red Hat Virtualization environment. An API user accesses this information through the rel="storagedomains" link obtained from the entry point URI. The following table shows specific elements contained in a storage domain resource representation. Table 12.1. Storage domain elements Element Type Description Properties link rel="permissions" relationship A link to the sub-collection for storage domain permissions. link rel="files" relationship A link to the files sub-collection for this storage domains. link rel="vms" relationship A link to the vms sub-collection for a storage domain with type set to export . link rel="templates" relationship A link to the templates sub-collection for a storage domain with type set to export . type enumerated The storage domain type. A list of enumerated values are available in capabilities . external_status complex/enumerated The storage domain health status as reported by external systems and plug-ins. The state element contains an enumerated value of ok , info , warning , error , or failure . master Boolean: true or false true if this is the master storage domain of a data center. host complex A reference to the host on which this storage domain should be initialized. The only restriction on this host is that it should have access to the physical storage specified. storage complex Describes the underlying storage of the storage domain. available integer Space available in bytes. used integer Space used in bytes. committed integer Space committed in bytes. storage_format enumerated Describes the storage format version for the storage domain. A list of enumerated values are available in capabilities . wipe_after_delete Boolean: true or false Sets the wipe after delete option by default on the storage domain. This option can be edited after the domain is created, but doing so will not change the wipe after delete property of disks that already exist. warning_low_space_indicator integer A percentage value that sets the warning low space indicator option. If the free space available on the storage domain is below this percentage, warning messages are displayed to the user and logged. critical_space_action_blocker integer A value in GB that sets the critical space action blocker option. If the free space available on the storage domain is below this value, error messages are displayed to the user and logged, and any new action that consumes space, even temporarily, will be blocked. Important The API as documented in this chapter is experimental and subject to change. It is not covered by the backwards compatibility statement.

Commands:
Chapter 17. Revision History Version Date Change Author 0.2-7 Dec 20 2023 Removed an outdated link. Lenka Spackova 0.2-6 Jul 03 2023 The rhscl/mariadb-103-rhel7 container image is EOL. Lenka Spackova 0.2-5 May 23 2023 Update with the release of Red Hat Developer Toolset 12.1. Lenka Spackova 0.2-4 Nov 22 2022 Update with the release of Red Hat Developer Toolset 12.0. Lenka Spackova 0.2-3 Nov 15 2021 Release of Using Red Hat Software Collections 3.8 Container Images. Lenka Spackova 0.2-2 Oct 11 2021 Release of Using Red Hat Software Collections 3.8 Beta Container Images. Lenka Spackova 0.2-1 Jun 03 2021 Release of Using Red Hat Software Collections 3.7 Container Images. Lenka Spackova 0.2-0 May 03 2021 Release of Using Red Hat Software Collections 3.7 Beta Container Images. Lenka Spackova 0.1-9 Apr 06 2021 Improved supported architectures. Lenka Spackova 0.1-8 Jan 13 2021 Improved introductory chapters and extended information about building application images. Lenka Spackova 0.1-7 Dec 01 2020 Release of Using Red Hat Software Collections 3.6 Container Images. Lenka Spackova 0.1-6 Oct 29 2020 Release of Using Red Hat Software Collections 3.6 Beta Container Images. Lenka Spackova 0.1-5 May 26 2020 Release of Using Red Hat Software Collections 3.5 Container Images. Lenka Spackova 0.1-4 Apr 21 2020 Release of Using Red Hat Software Collections 3.5 Beta Container Images. Lenka Spackova 0.1-3 Dec 10 2019 Release of Using Red Hat Software Collections 3.4 Container Images. Lenka Spackova 0.1-2 Nov 07 2019 Release of Using Red Hat Software Collections 3.4 Beta Container Images. Lenka Spackova 0.1-1 Jun 11 2019 Release of Using Red Hat Software Collections 3.3 Container Images. Lenka Spackova 0.1-0 Apr 16 2019 Release of Using Red Hat Software Collections 3.3 Beta Container Images. Lenka Spackova 0.0-9 Nov 13 2018 Release of Using Red Hat Software Collections 3.2 Container Images. Lenka Spackova 0.0-8 Oct 23 2018 Release of Using Red Hat Software Collections 3.2 Beta Container Images. Lenka Spackova 0.0-8 Aug 29 2018 Added a known issue related to SystemTap in devtoolset-6-perftools. Lenka Spackova 0.0-7 May 10 2018 Extended MongoDB image documentation. Lenka Spackova 0.0-6 May 03 2018 Release of Using Red Hat Software Collections 3.1 Container Images. Lenka Spackova 0.0-5 Apr 04 2018 Release of Using Red Hat Software Collections 3.1 Beta Container Images. Lenka Spackova 0.0-3 Nov 29 2017 Added the Extending Existing Container Images section. Lenka Spackova 0.0-2 Oct 24 2017 Release of Using Red Hat Software Collections 3.0 Container Images. Lenka Spackova 0.0-1 Oct 03 2017 Release of Using Red Hat Software Collections 3.0 Beta Container Images. Lenka Spackova

Commands:
Chapter 6. Removing OSDs using the OpenShift Data Foundation CLI tool 6.1. Removing object storage devices using the OpenShift Data Foundation CLI tool You can use the OpenShift Data Foundation command line interface (CLI) tool to automate the process of object storage device (OSD) removal. This helps to avoid the possible data loss while removing OSDs. Prerequisites Download the OpenShift Data Foundation command line interface (CLI) tool. With the Data Foundation CLI tool, you can effectively manage and troubleshoot your Data Foundation environment from a terminal. You can find a compatible version and download the CLI tool from the customer portal . Procedure Identify the OSD that needs to be removed. The OSD that needs removal is in CrashLoopBackOff or Error state. Example output: Run the following command to remove OSD 0 : [Optional] If removal of the OSD affects placement group (PG) status, enter yes-force-destroy-osd . Verify that the last line of the command output contains cephosd: completed removal of OSD 0 . Verify the corresponding deployment is removed:

Commands:
oc get -n openshift-storage pods -l app=rook-ceph-osd -o wide
rook-ceph-osd-0-6d77d6c7c6-m8xj6 0/1 CrashLoopBackOff 0 24h 10.129.0.16 compute-2 <none> <none>
odf purge-osd 0
oc get deployment rook-ceph-osd-0
7.5. Verifying Network Configuration Bonding for Redundancy Network redundancy is a process when devices are used for backup purposes to prevent or recover from a failure of a specific system. The following procedure describes how to verify the network configuration for bonding in redundancy: Procedure Ping the destination IP from the bond interface. For example: View which interface is in active mode: enp1s0 is the active port interface. Set the active port interface down: Check if the backup interface is up: enp2s0 is now the active port interface. Check if you can still ping the destination IP from the bond interface:

Commands:
~]# ping -I bond0 DSTADDR
~]# cat /sys/class/net/bond0/bonding/active_slave enp1s0
~]# ip link set enp1s0 down
~]# cat /sys/class/net/bond0/bonding/active_slave enp2s0
~]# ping -I bond0 DSTADDR
3.2. Unmounting a Hierarchy If you mounted a hierarchy by editing the /etc/cgconfig.conf configuration file, you can unmount it simply by removing the configuration directive from the mount section of this configuration file. Then restart the service to apply the new configuration. Similarly, you can unmount a hierarchy by executing the following command as root : Replace controller_name with the name of the hierarchy that contains the resource controller you wish to detach. Warning Make sure that you use umount to remove only hierarchies that you mounted yourself manually. Detaching a hierarchy that contains a default controller (listed in Available Controllers in Red Hat Enterprise Linux 7 ) will most probably lead to complications requiring a system reboot.

Commands:
~]# umount /sys/fs/cgroup/ controller_name
B.11. cups B.11.1. RHSA-2010:0866 - Important: cups security update Updated cups 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 important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. The Common UNIX Printing System (CUPS) provides a portable printing layer for UNIX operating systems. CVE-2010-2941 An invalid free flaw was found in the way the CUPS server parsed Internet Printing Protocol (IPP) packets. A malicious user able to send IPP requests to the CUPS server could use this flaw to crash the CUPS server. Red Hat would like to thank Emmanuel Bouillon of NATO C3 Agency for reporting this issue. Users of cups are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the cupsd daemon will be restarted automatically.

Commands:
15.2. Language Selection Use the arrow keys on your keyboard to select a language to use during the installation process (refer to Figure 15.3, "Language Selection" ). With your selected language highlighted, press the Tab key to move to the OK button and press the Enter key to confirm your choice. The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen. To add support for additional languages, customize the installation at the package selection stage. For more information, refer to Section 16.19.2, " Customizing the Software Selection " . Figure 15.3. Language Selection Once you select the appropriate language, click to continue.

Commands:
Chapter 7. Accessing Support Using the Red Hat Support Tool The Red Hat Support Tool , in the redhat-support-tool package, can function as both an interactive shell and as a single-execution program. It can be run over SSH or from any terminal. It enables, for example, searching the Red Hat Knowledgebase from the command line, copying solutions directly on the command line, opening and updating support cases, and sending files to Red Hat for analysis. 7.1. Installing the Red Hat Support Tool The Red Hat Support Tool is installed by default on Red Hat Enterprise Linux. If required, to ensure that it is, enter the following command as root :

Commands:
~]# yum install redhat-support-tool
Appendix B. List of tickets by component Bugzilla and JIRA IDs are listed in this document for reference. Bugzilla bugs that are publicly accessible include a link to the ticket. Component Tickets 389-ds-base BZ#1801327 , BZ#1700987 , BZ#1796558 , BZ#1769418 , BZ#1807537 , BZ#1837105 , BZ#1824930 , BZ#1827284 ansible BZ#1767177 , BZ#1439896, BZ#1660838 apr BZ#1739287 bind BZ#1744081 , BZ#1758317 , BZ#1853191, BZ#1851836 cloud-init BZ#1772505 , BZ#1685580 cloud BZ#1846667, BZ#1348508 corosync BZ#1413573 criu BZ#1400230 cups BZ#1672212 custodia BZ#1403214 desktop BZ#1481411 dnf BZ#1461652 fence-agents BZ#1476401 filesystems BZ#1274459, BZ#1111712, BZ#1206277, BZ#1477977 firewalld BZ#1796055 , BZ#1754117 freerdp BZ#1834286 gnome-shell BZ#1481395 hardware-enablement BZ#1062759, BZ#1384452, BZ#1519746, BZ#1454918, BZ#1454916 identity-management BZ#1819745 , BZ#1405325 ipa BZ#1115294 , BZ#1298286 , BZ#1518939 iptables BZ#1851944 iscsi-initiator-utils BZ#1439055 kernel-rt BZ#1790643 kernel BZ#1801759 , BZ#1781726, BZ#1514705, BZ#1855010 , BZ#1807077, BZ#1770232, BZ#1829777, BZ#1836292, BZ#1168430, BZ#1706522, BZ#1813394, BZ#1844522, BZ#1838903, BZ#1862840, BZ#1871027, BZ#1874101, BZ#1933998, BZ#1559615, BZ#1230959, BZ#1460849, BZ#1464377, BZ#1457533, BZ#1503123, BZ#1589397, BZ#1726642 kexec-tools BZ#1773478 krb5 BZ#1733289 , BZ#1782492 libguestfs BZ#1387213 libreswan BZ#1375750 libvirt BZ#1475770 mariadb BZ#1834835 networking BZ#1062656, BZ#916384, BZ#916382, BZ#755087, BZ#1259547, BZ#1393375 nss BZ#1431210 , BZ#1425514 , BZ#1432142 openscap BZ#1478285 , BZ#1640522 , BZ#1829782 openssh BZ#1828598 oscap-anaconda-addon BZ#1648162 ovmf BZ#653382 pacemaker BZ#1792492 pcp BZ#1775373 pcs BZ#1433016 perl BZ#1751381 , BZ#1806523 pki-core BZ#1768718, BZ#1487418 resource-agents BZ#1513957 scap-security-guide BZ#1821633 , BZ#1791583 , BZ#1665233 , BZ#1958789 , BZ#1955180 , BZ#1691877 , BZ#1494606 , BZ#1609014 , BZ#1776780 , BZ#1890111 , BZ#1942281 , BZ#1838622 , BZ#1721439 , BZ#1778661 , BZ#1891435 , BZ#1976123 security BZ#1421794, BZ#1832194 selinux-policy BZ#1770123 , BZ#1780332 , BZ#1775573 services BZ#1790655, BZ#1844443 sssd BZ#1796352 , BZ#1068725 storage BZ#1649493, BZ#1942865, BZ#1109348, BZ#1119909, BZ#1414957 systemd BZ#1284974 tang BZ#1703445 tools BZ#1569484 tuned BZ#1702724 , BZ#1776149 unbound BZ#2121623 usbguard BZ#1480100 vdo BZ#1706154 virtualization BZ#1854917, BZ#1103193, BZ#1299662 , BZ#1661654 yum-utils BZ#2042313 yum BZ#1708628, BZ#1778784

Commands:
14.7. Using an Access Banner In Certificate System, Administrators can configure a banner with customizable text. The banner will be displayed in the following situations: Application When the banner is displayed PKI Console Before the console is displayed. After the session has expired. [a] Web interface When you connect to the web interface. After the session expired. [a] pki command-line utility Before the actual operation proceeds. [a] For details about changing the session timeout, see Section 14.4.2, "Session Timeout" . You can use the banner to display important information to the users before they can use Certificate System. The user must agree to the displayed text to continue. Example 14.4. When the Access Banner is Displayed The following example shows when the access banner is displayed if you are using the pki utility: 14.7.1. Enabling an Access Banner To enable the access banner, create the /etc/pki/ instance_name /banner.txt file and enter the text to displayed. Important The text in the /etc/pki/ instance_name /banner.txt file must use the UTF-8 format. To validate, see Section 14.7.4, "Validating the Banner" . 14.7.2. Disabling an Access Banner To disable the access banner, either delete or rename the /etc/pki/ instance_name /banner.txt file. For example: 14.7.3. Displaying the Banner To display the currently configured banner: 14.7.4. Validating the Banner To validate that the banner does not contain invalid characters:

Commands:
pki cert-show 0x1 WARNING! Access to this service is restricted to those individuals with specific permissions. If you are not an authorized user, disconnect now. Any attempts to gain unauthorized access will be prosecuted to the fullest extent of the law. Do you want to proceed (y/N)? y ----------------- Certificate "0x1" ----------------- Serial Number: 0x1 Issuer: CN=CA Signing Certificate,OU= instance_name ,O=EXAMPLE Subject: CN=CA Signing Certificate,OU= instance_name ,O=EXAMPLE Status: VALID Not Before: Mon Feb 20 18:21:03 CET 2017 Not After: Fri Feb 20 18:21:03 CET 2037
mv /etc/pki/ instance_name /banner.txt /etc/pki/ instance_name /banner.txt.UNUSED
pki-server banner-show -i instance_name
pki-server banner-validate -i instance_name --------------- Banner is valid ---------------
2.14. pqos The pqos utility, which is available from the intel-cmt-cat package, enables you to both monitor and control CPU cache and memory bandwidth on recent Intel processors. You can use it for workload isolation and improving performance determinism in multitenant deployments. It exposes the following processor capabilities from the Resource Director Technology (RDT) feature set: Monitoring Last Level Cache (LLC) usage and contention monitoring using the Cache Monitoring Technology (CMT) Per-thread memory bandwidth monitoring using the Memory Bandwidth Monitoring (MBM) technology Allocation Controlling the amount of LLC space that is available for specific threads and processes using the Cache Allocation Technology (CAT) Controlling code and data placement in the LLC using the Code and Data Prioritization (CDP) technology Use the following command to list the RDT capabilities supported on your system and to display the current RDT configuration: Additional Resources For more information about using pqos , see the pqos (8) man page. For detailed information on the CMT, MBM, CAT, and CDP processor features, see the official Intel documentation: Intel(R) Resource Director Technology (Intel(R) RDT) .

Commands:
pqos --show --verbose