mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix B. Troubleshooting DNF modules If DNF modules fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows. List the enabled modules: B.1. Ruby If Ruby module fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows: List the enabled modules: If the Ruby 2.5 module has already been enabled, perform a module reset: B.2. PostgreSQL If PostgreSQL module fails to enable, it can mean an incorrect module is enabled. In that case, you have to resolve dependencies manually as follows: List the enabled modules: If the PostgreSQL 10 module has already been enabled, perform a module reset: If a database was previously created using PostgreSQL 10, perform an upgrade: Enable the DNF modules: Install the PostgreSQL upgrade package: Perform the upgrade:

Commands:
dnf module list --enabled
dnf module list --enabled
dnf module reset ruby
dnf module list --enabled
dnf module reset postgresql
dnf module enable satellite-capsule:el8
dnf install postgresql-upgrade
postgresql-setup --upgrade
Chapter 15. Set Up Lock Striping 15.1. About Lock Striping Lock Striping allocates locks from a shared collection of (fixed size) locks in the cache. Lock allocation is based on the hash code for each entry's key. Lock Striping provides a highly scalable locking mechanism with fixed overhead. However, this comes at a cost of potentially unrelated entries being blocked by the same lock. Lock Striping is disabled by default in Red Hat JBoss Data Grid. If lock striping remains disabled, a new lock is created for each entry. This alternative approach can provide greater concurrent throughput, but also results in additional memory usage, garbage collection churn, and other disadvantages. Report a bug

Commands:
API overview OpenShift Container Platform 4.14 Overview content for the OpenShift Container Platform API Red Hat OpenShift Documentation Team

Commands:
oc debug node/<node>
chroot /host
systemctl cat kubelet
/etc/systemd/system/kubelet.service.d/20-logging.conf [Service] Environment="KUBELET_LOG_LEVEL=2"
echo -e "[Service]\nEnvironment=\"KUBELET_LOG_LEVEL=8\"" > /etc/systemd/system/kubelet.service.d/30-logging.conf
systemctl daemon-reload
systemctl restart kubelet
rm -f /etc/systemd/system/kubelet.service.d/30-logging.conf
systemctl daemon-reload
systemctl restart kubelet
apiVersion: machineconfiguration.openshift.io/v1 kind: MachineConfig metadata: labels: machineconfiguration.openshift.io/role: master name: 99-master-kubelet-loglevel spec: config: ignition: version: 3.2.0 systemd: units: - name: kubelet.service enabled: true dropins: - name: 30-logging.conf contents: | [Service] Environment="KUBELET_LOG_LEVEL=2"
oc adm node-logs --role master -u kubelet
oc adm node-logs --role worker -u kubelet
journalctl -b -f -u kubelet.service
sudo tail -f /var/log/containers/*
- for n in USD(oc get node --no-headers | awk '{print USD1}'); do oc adm node-logs USDn | gzip > USDn.log.gz; done
Chapter 58. BrokerCapacityOverride schema reference Used in: BrokerCapacity Property Property type Description brokers integer array List of Kafka brokers (broker identifiers). cpu string Broker capacity for CPU resource in cores or millicores. For example, 1, 1.500, 1500m. For more information on valid CPU resource units see https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-cpu . inboundNetwork string Broker capacity for inbound network throughput in bytes per second. Use an integer value with standard OpenShift byte units (K, M, G) or their bibyte (power of two) equivalents (Ki, Mi, Gi) per second. For example, 10000KiB/s. outboundNetwork string Broker capacity for outbound network throughput in bytes per second. Use an integer value with standard OpenShift byte units (K, M, G) or their bibyte (power of two) equivalents (Ki, Mi, Gi) per second. For example, 10000KiB/s.

Commands:
Chapter 2. The pcsd Web UI This chapter provides an overview of configuring a Red Hat High Availability cluster with the pcsd Web UI. 2.1. pcsd Web UI Setup To set up your system to use the pcsd Web UI to configure a cluster, use the following procedure. Install the Pacemaker configuration tools, as described in Section 1.2, "Installing Pacemaker configuration tools" . On each node that will be part of the cluster, use the passwd command to set the password for user hacluster , using the same password on each node. Start and enable the pcsd daemon on each node: On one node of the cluster, authenticate the nodes that will constitute the cluster with the following command. After executing this command, you will be prompted for a Username and a Password . Specify hacluster as the Username . On any system, open a browser to the following URL, specifying one of the nodes you have authorized (note that this uses the https protocol). This brings up the pcsd Web UI login screen. Log in as user hacluster . This brings up the Manage Clusters page as shown in Figure 2.1, "Manage Clusters page" . Figure 2.1. Manage Clusters page

Commands:
systemctl start pcsd.service systemctl enable pcsd.service
pcs cluster auth node1 node2 ... nodeN
https:// nodename :2224
Planning, Installation, and Deployment Guide Red Hat Certificate System 10 This manual covers all aspects of installing, configuring, and managing Certificate System subsystems. Florian Delehaye Red Hat Customer Content Services fdelehay@redhat.com Marc Muehlfeld Red Hat Customer Content Services Petr Bokoc Red Hat Customer Content Services Filip Hanzelka Red Hat Customer Content Services Tomas Capek Red Hat Customer Content Services Aneta Petrova Red Hat Customer Content Services Ella Deon Ballard Red Hat Customer Content Services

Commands:
3.13. Optimizations in User Space Reducing the amount of work performed by system hardware is fundamental to saving power. Therefore, although the changes described in Chapter 3, Core Infrastructure and Mechanics permit the system to operate in various states of reduced power consumption, applications in user space that request unnecessary work from system hardware prevent the hardware from entering those states. During the development of Red Hat Enterprise Linux 6, audits were undertaken in the following areas to reduce unnecessary demands on hardware: Reduced wakeups Red Hat Enterprise Linux 6 uses a tickless kernel (refer to Section 3.6, "Tickless Kernel" ), which allows the CPUs to remain in deeper idle states longer. However, the timer tick is not the only source of excessive CPU wakeups, and function calls from applications can also prevent the CPU from entering or remaining in idle states. Unnecessary function calls were reduced in over 50 applications. Reduced storage and network I/O Input or output (I/O) to storage devices and network interfaces forces devices to consume power. In storage and network devices that feature reduced power states when idle (for example, ALPM or ASPM), this traffic can prevent the device from entering or remaining in an idle state, and can prevent hard drives from spinning down when not in use. Excessive and unnecessary demands on storage have been minimized in several applications. In particular, those demands that prevented hard drives from spinning down. Initscript audit Services that start automatically whether required or not have great potential to waste system resources. Services instead should default to "off" or "on demand" wherever possible. For example, the BlueZ service that enables Bluetooth support previously ran automatically when the system started, whether Bluetooth hardware was present or not. The BlueZ initscript now checks that Bluetooth hardware is present on the system before starting the service.

Commands:
C.3. Rule Instances This section discusses the rule instances that have been set. C.3.1. LdapCaCertRule The LdapCaCertRule can be used to publish CA certificates to an LDAP directory. Table C.11. LdapCaCert Rule Configuration Parameters Parameter Value Description type cacert Specifies the type of certificate that will be published. predicate Specifies a predicate for the publisher. enable yes Enables the rule. mapper LdapCaCertMap Specifies the mapper used with the rule. See Section C.2.1.1, "LdapCaCertMap" for details on the mapper. publisher LdapCaCertPublisher Specifies the publisher used with the rule. See Section C.1.2, "LdapCaCertPublisher" for details on the publisher. C.3.2. LdapXCertRule The LdapXCertRule is used to publish cross-pair certificates to an LDAP directory. Table C.12. LdapXCert Rule Configuration Parameters Parameter Value Description type xcert Specifies the type of certificate that will be published. predicate Specifies a predicate for the publisher. enable yes Enables the rule. mapper LdapCaCertMap Specifies the mapper used with the rule. See Section C.2.1.1, "LdapCaCertMap" for details on the mapper. publisher LdapCrossCertPairPublisher Specifies the publisher used with the rule. See Section C.1.6, "LdapCertificatePairPublisher" for details on this publisher. C.3.3. LdapUserCertRule The LdapUserCertRule is used to publish user certificates to an LDAP directory. Table C.13. LdapUserCert Rule Configuration Parameters Parameter Value Description type certs Specifies the type of certificate that will be published. predicate Specifies a predicate for the publisher. enable yes Enables the rule. mapper LdapUserCertMap Specifies the mapper used with the rule. See Section C.2.3, "LdapSimpleMap" for details on the mapper. publisher LdapUserCertPublisher Specifies the publisher used with the rule. See Section C.1.3, "LdapUserCertPublisher" for details on the publisher. C.3.4. LdapCRLRule The LdapCRLRule is used to publish CRLs to an LDAP directory. Table C.14. LdapCRL Rule Configuration Parameters Parameter Value Description type crl Specifies the type of certificate that will be published. predicate Specifies a predicate for the publisher. enable yes Enables the rule. mapper LdapCrlMap Specifies the mapper used with the rule. See Section C.2.1.2, "LdapCrlMap" for details on the mapper. publisher LdapCrlPublisher Specifies the publisher used with the rule. See Section C.1.4, "LdapCrlPublisher" for details on the publisher.

Commands:
Chapter 4. Use Cases This chapter describes two types of use case to illustrate the analysis and configuration methods described elsewhere in this guide. The first example considers typical servers and the second is a typical laptop. 4.1. Example - Server A typical standard server nowadays comes with the majority of the necessary hardware features supported in Red Hat Enterprise Linux 7. The first thing to take into consideration is the kinds of workloads for which the server will mainly be used. Based on this information you can decide which components can be optimized for power savings. Regardless of the type of server, graphics performance is generally not required. Therefore, GPU power savings can be left turned on. Webserver A webserver needs network and disk I/O. Depending on the external connection speed 100 Mbit/s might be enough. If the machine serves mostly static pages, CPU performance might not be very important. Power-management choices might therefore include: no disk or network plugins for tuned . ALPM turned on. ondemand governor turned on. network card limited to 100 Mbit/s. Compute server A compute server mainly needs CPU. Power management choices might include: depending on the jobs and where data storage happens, disk or network plugins for tuned ; or for batch-mode systems, fully active tuned . depending on utilization, perhaps the performance governor. Mailserver A mailserver needs mostly disk I/O and CPU. Power management choices might include: ondemand governor turned on, because the last few percent of CPU performance are not important. no disk or network plugins for tuned . network speed should not be limited, because mail is often internal and can therefore benefit from a 1 Gbit/s or 10 Gbit/s link. Fileserver Fileserver requirements are similar to those of a mailserver, but depending on the protocol used, might require more CPU performance. Typically, Samba-based servers require more CPU than NFS, and NFS typically requires more than iSCSI. Even so, you should be able to use the ondemand governor. Directory server A directory server typically has lower requirements for disk I/O, especially if equipped with enough RAM. Network latency is important although network I/O less so. You might consider latency network tuning with a lower link speed, but you should test this carefully for your particular network.

Commands:
Introduction Welcome to the Global File System Configuration and Administration document. This book provides information about installing, configuring, and maintaining Red Hat GFS (Red Hat Global File System). Red Hat GFS depends on the cluster infrastructure of Red Hat Cluster Suite. For information about Red Hat Cluster Suite refer to Red Hat Cluster Suite Overview and Configuring and Managing a Red Hat Cluster . HTML and PDF versions of all the official Red Hat Enterprise Linux manuals and release notes are available online at http://www.redhat.com/docs/ . 1. Audience This book is intended primarily for Linux system administrators who are familiar with the following activities: Linux system administration procedures, including kernel configuration Installation and configuration of shared storage networks, such as Fibre Channel SANs

Commands:
probe::netfilter.bridge.local_out Name probe::netfilter.bridge.local_out - Called on a bridging packet coming from a local process Synopsis netfilter.bridge.local_out Values indev Address of net_device representing input device, 0 if unknown br_msg Message age in 1/256 secs nf_drop Constant used to signify a 'drop' verdict llcproto_stp Constant used to signify Bridge Spanning Tree Protocol packet pf Protocol family -- always " bridge " br_fd Forward delay in 1/256 secs nf_queue Constant used to signify a 'queue' verdict brhdr Address of bridge header br_mac Bridge MAC address br_flags BPDU flags outdev_name Name of network device packet will be routed to (if known) nf_accept Constant used to signify an 'accept' verdict br_rid Identity of root bridge nf_stop Constant used to signify a 'stop' verdict br_type BPDU type br_max Max age in 1/256 secs protocol Packet protocol br_htime Hello time in 1/256 secs br_bid Identity of bridge br_rmac Root bridge MAC address br_prid Protocol identifier llcpdu Address of LLC Protocol Data Unit length The length of the packet buffer contents, in bytes nf_stolen Constant used to signify a 'stolen' verdict br_cost Total cost from transmitting bridge to root br_vid Protocol version identifier indev_name Name of network device packet was received on (if known) br_poid Port identifier outdev Address of net_device representing output device, 0 if unknown nf_repeat Constant used to signify a 'repeat' verdict

Commands:
14.6.2. Stopping a Running Domain to Restart It Later virsh managedsave domain --bypass-cache --running | --paused | --verbose saves and destroys (stops) a running domain so that it can be restarted from the same state at a later time. When used with a virsh start command it is automatically started from this save point. If it is used with the --bypass-cache option the save will avoid the filesystem cache. Note that this option may slow down the save process speed. --verbose displays the progress of the dump process Under normal conditions, the managed save will decide between using the running or paused state as determined by the state the domain is in when the save is done. However, this can be overridden by using the --running option to indicate that it must be left in a running state or by using --paused option which indicates it is to be left in a paused state. To remove the managed save state, use the virsh managedsave-remove command which will force the domain to do a full boot the time it is started. Note that the entire managed save process can be monitored using the domjobinfo command and can also be canceled using the domjobabort command.

Commands:
Appendix A. Technical users provided and required by Satellite During the installation of Satellite, system accounts are created. They are used to manage files and process ownership of the components integrated into Satellite. Some of these accounts have fixed UIDs and GIDs, while others take the available UID and GID on the system instead. To control the UIDs and GIDs assigned to accounts, you can define accounts before installing Satellite. Because some of the accounts have hard-coded UIDs and GIDs, it is not possible to do this with all accounts created during Satellite installation. The following table lists all the accounts created by Satellite during installation. You can predefine accounts that have Yes in the Flexible UID and GID column with custom UID and GID before installing Satellite. Do not change the home and shell directories of system accounts because they are requirements for Satellite to work correctly. Because of potential conflicts with local users that Satellite creates, you cannot use external identity providers for the system users of the Satellite base operating system. Table A.1. Technical users provided and required by Satellite User name UID Group name GID Flexible UID and GID Home Shell foreman N/A foreman N/A yes /usr/share/foreman /sbin/nologin foreman-proxy N/A foreman-proxy N/A yes /usr/share/foreman-proxy /sbin/nologin apache 48 apache 48 no /usr/share/httpd /sbin/nologin postgres 26 postgres 26 no /var/lib/pgsql /bin/bash pulp N/A pulp N/A no N/A /sbin/nologin puppet 52 puppet 52 no /opt/puppetlabs/server/data/puppetserver /sbin/nologin saslauth N/A saslauth 76 no /run/saslauthd /sbin/nologin tomcat 53 tomcat 53 no /usr/share/tomcat /bin/nologin unbound N/A unbound N/A yes /etc/unbound /sbin/nologin

Commands:
12.2.3. Btrfs The btrfsck tool is used to check and repair btrfs filesystems. This tool is still in early development and may not detect or repair all types of filesystem corruption. By default, btrfsck does not make changes to the filesystem; that is, it runs check-only mode by default. If repairs are desired the --repair option must be specified. The following three basic phases are performed by btrfsck while running: Extent checks. Filesystem root checks. Root reference count checks. The btrfs-image(8) utility can be used to create a metadata image prior to repair for diagnostic or testing purposes.

Commands:
A.2.3. The dmsetup status Command The dmsetup status device command provides status information for each target in a specified device. If you do not specify a device name, the output is information about all of the currently configured Device Mapper devices. You can list the status only of devices that have at least one target of a specified type with the dmsetup status --target target_type command. The following example shows the command to list the status of the targets in all currently configured mapped devices.

Commands:
dmsetup status testgfsvg-testgfslv3: 0 312352768 linear testgfsvg-testgfslv2: 0 312352768 linear testgfsvg-testgfslv1: 0 312352768 linear testgfsvg-testgfslv1: 312352768 50331648 linear VolGroup00-LogVol01: 0 4063232 linear VolGroup00-LogVol00: 0 151912448 linear
Chapter 12. Ensuring correct data displays in HawtIO If the display of the queues and connections in HawtIO is missing queues, missing connections, or displaying inconsistent icons, adjust the Jolokia collection size parameter that specifies the maximum number of elements in an array that Jolokia marshals in a response. Procedure : In the upper right corner of HawtIO, click the user icon and then click Preferences . Increase the value of the Maximum collection size option (the default is 50,000). Click Close .

Commands:
Chapter 104. MavenArtifact schema reference Used in: Plugin The type property is a discriminator that distinguishes use of the MavenArtifact type from JarArtifact , TgzArtifact , ZipArtifact , OtherArtifact . It must have the value maven for the type MavenArtifact . Property Property type Description type string Must be maven . repository string Maven repository to download the artifact from. Applicable to the maven artifact type only. group string Maven group id. Applicable to the maven artifact type only. artifact string Maven artifact id. Applicable to the maven artifact type only. version string Maven version number. Applicable to the maven artifact type only. insecure boolean By default, connections using TLS are verified to check they are secure. The server certificate used must be valid, trusted, and contain the server name. By setting this option to true , all TLS verification is disabled and the artifacts will be downloaded, even when the server is considered insecure.

Commands:
19.7. Managing Snapshots Using virt-manager , it is possible to create, run, and delete guest snapshots . A snapshot is a saved image of the guest's hard disk, memory, and device state at a single point in time. After a snapshot is created, the guest can be returned to the snapshot's configuration at any time. Important Red Hat recommends the use of external snapshots, as they are more flexible and reliable when handled by other virtualization tools. However, it is currently not possible to create external snapshots in virt-manager . To create external snapshots, use the virsh snapshot-create-as command with the --diskspec vda,snapshot=external option. For more information, see Section A.13, "Workaround for Creating External Snapshots with libvirt" . To manage snapshots in virt-manager, open the snapshot management interface by clicking on the guest console. To create a new snapshot, click under the snapshot list. In the snapshot creation interface, input the name of the snapshot and, optionally, a description, and click Finish . To revert the guest to a snapshot's configuration, select the snapshot and click To remove the selected snapshot, click Warning Creating and loading snapshots while the virtual machine is running (also referred to as live snapshots ) is only supported with qcow2 disk images. For more in-depth snapshot management, use the virsh snapshot-create command. See Section 20.39, "Managing Snapshots" for details about managing snapshots with virsh .

Commands:
Chapter 1. Support policy for Cryostat Red Hat supports a major version of Cryostat for a minimum of 6 months. Red Hat bases this figure on the time that the product gets released on the Red Hat Customer Portal. You can install and deploy Cryostat on Red Hat OpenShift Container Platform 4.8 or a later version that runs on an x86_64 architecture. Additional resources For more information about the Cryostat life cycle policy, see Red Hat build of Cryostat on the Red Hat OpenShift Container Platform Life Cycle Policy web page.

Commands:
4.14. PostgreSQL 4.14.1. Upgrading Databases If you are upgrading from an existing Red Hat Enterprise Linux 5 installation in which PostgreSQL 8.4 ( postgresql84-* packages) was in use, the Red Hat Enterprise Linux 6 PostgreSQL packages will operate as a drop-in replacement. However, if you are upgrading from a Red Hat Enterprise Linux 5 installation in which PostgreSQL 8.1 ( postgresql-* packages) or earlier was in use, and you have existing database content that needs to be preserved, you will need to follow the dump and reload procedure here due to changes in the data format: http://www.postgresql.org/docs/8.4/interactive/install-upgrading.html . Ensure that you perform the dump step before upgrading to Red Hat Enterprise Linux 6.

Commands:
3.4. Setting the Number of Locks Using the Web Console To set the number of locks using the Web Console: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. Open the Database menu, and select Global Database Configuration . Click Show Advanced Settings . Update the value in the Database Locks field. Click Save Configuration . Click the Actions button, and select Restart Instance .

Commands: