mtpti5iD/redhat-docs_dataset huggingface dataset:
15.9. Disabling and Re-enabling Replication By default, replication is enabled when you create a replication agreement. In certain situations, for example, when taking down a server for maintenance, administrators want to temporarily disable replication. Important If you disable the replication entry using the dsconf replication disable command, Directory Server automatically deletes the replication agreement as well. In this case, to re-enable replication, you must recreate the replication agreement. To temporarily disable a replication agreement: To re-enable an replication agreement:

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt disable --suffix="dc=example,dc=com" agreement_name
dsconf -D "cn=Directory Manager" ldap://server.example.com repl-agmt enable --suffix="dc=example,dc=com" agreement_name
8.5.3. Related Books The following books discuss various issues related to disaster recovery, and are good resources for Red Hat Enterprise Linux system administrators: The System Administrators Guide ; Red Hat, Inc -- Includes a chapter on system recovery, which could be useful in bare metal restorations. Unix Backup &Recovery by W. Curtis Preston; O'Reilly &Associates -- Although not written specifically for Linux systems, this book provides in-depth coverage into many backup-related issues, and even includes a chapter on disaster recovery.

Commands:
19.3. Unmounting a File System To detach a previously mounted file system, use either of the following variants of the umount command: Note that unless this is performed while logged in as root , the correct permissions must be available to unmount the file system. For more information, see Section 19.2.2, "Specifying the Mount Options" . See Example 19.9, "Unmounting a CD" for an example usage. Important When a file system is in use (for example, when a process is reading a file on this file system, or when it is used by the kernel), running the umount command fails with an error. To determine which processes are accessing the file system, use the fuser command in the following form: For example, to list the processes that are accessing a file system mounted to the /media/cdrom/ directory: Example 19.9. Unmounting a CD To unmount a CD that was previously mounted to the /media/cdrom/ directory, use the following command:

Commands:
umount directory USD umount device
fuser -m directory
fuser -m /media/cdrom /media/cdrom: 1793 2013 2022 2435 10532c 10672c
umount /media/cdrom
Chapter 16. Accessing odf-console with the ovs-multitenant plugin by manually enabling global pod networking In OpenShift Container Platform, when ovs-multitenant plugin is used for software-defined networking (SDN), pods from different projects cannot send packets to or receive packets from pods and services of a different project. By default, pods can not communicate between namespaces or projects because a project's pod networking is not global. To access odf-console, the OpenShift console pod in the openshift-console namespace needs to connect with the OpenShift Data Foundation odf-console in the openshift-storage namespace. This is possible only when you manually eanble global pod networking. Issue When`ovs-multitenant` plugin is used in the OpenShift Container Platform, the odf-console plugin fails with the following message: Resolution Make the pod networking for the OpenShift Data Foundation project global:

Commands:
GET request for "odf-console" plugin failed: Get "https://odf-console-service.openshift-storage.svc.cluster.local:9001/locales/en/plugin__odf-console.json": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
oc adm pod-network make-projects-global openshift-storage
Chapter 8. Clusters 8.1. Introduction to Clusters A cluster is a logical grouping of hosts that share the same storage domains and have the same type of CPU (either Intel or AMD). If the hosts have different generations of CPU models, they use only the features present in all models. Each cluster in the system must belong to a data center, and each host in the system must belong to a cluster. Virtual machines are dynamically allocated to any host in a cluster and can be migrated between them, according to policies defined on the cluster and settings on the virtual machines. The cluster is the highest level at which power and load-sharing policies can be defined. The number of hosts and number of virtual machines that belong to a cluster are displayed in the results list under Host Count and VM Count , respectively. Clusters run virtual machines or Red Hat Gluster Storage Servers. These two purposes are mutually exclusive: A single cluster cannot support virtualization and storage hosts together. Red Hat Virtualization creates a default cluster in the default data center during installation. Figure 8.1. Cluster

Commands:
Chapter 6. Using qdstat or qdmanage over SSL/TLS With the Interconnect 1.10.1 release, certificates are verified using the system Certificate Authority (CA) when using qdstat or qdmanage over SSL/TLS and the --ssl-trustfile is not specified. Typically, the system CA is not used to issue these certificates and the connection fails. If you use qdstat or qdmanage to connect to a router over SSL/TLS, specify the CA file to authenticate that router to avoid connection issues. For example: USD qdstat --ssl-trustfile <pem-database-file>

Commands:
qdstat --ssl-trustfile <pem-database-file>
4.5. Global Cluster Properties When you select a cluster to configure, a cluster-specific page is displayed. The page provides an interface for configuring cluster-wide properties. You can configure cluster-wide properties by clicking on Configure along the top of the cluster display. This yields a tabbed interface which provides the following tabs: General , Fence Daemon , Network , Redundant Ring , QDisk and Logging . To configure the parameters in those tabs, follow the steps in the following sections. If you do not need to configure parameters in a tab, skip the section for that tab. 4.5.1. Configuring General Properties Clicking on the General tab displays the General Properties page, which provides an interface for modifying the configuration version. The Cluster Name text box displays the cluster name; it does not accept a cluster name change. The only way to change the name of a cluster is to create a new cluster configuration with the new name. The Configuration Version value is set to 1 at the time of cluster creation and is automatically incremented each time you modify your cluster configuration. However, if you need to set it to another value, you can specify it at the Configuration Version text box. If you have changed the Configuration Version value, click Apply for this change to take effect.

Commands:
14.18. Managing Resources for Guest Virtual Machines virsh allows the grouping and allocation of resources on a per guest virtual machine basis. This is managed by the libvirt daemon, which creates cgroups and manages them on behalf of the guest virtual machine. The only thing that is left for the system administrator to do is to either query or set tunables against specified guest virtual machines. The following tunables may used: memory - The memory controller allows for setting limits on RAM and swap usage and querying cumulative usage of all processes in the group cpuset - The CPU set controller binds processes within a group to a set of CPUs and controls migration between CPUs. cpuacct - The CPU accounting controller provides information about CPU usage for a group of processes. cpu -The CPU scheduler controller controls the prioritization of processes in the group. This is similar to granting nice level privileges. devices - The devices controller grants access control lists on character and block devices. freezer - The freezer controller pauses and resumes execution of processes in the group. This is similar to SIGSTOP for the whole group. net_cls - The network class controller manages network utilization by associating processes with a tc network class. In creating a group hierarchy cgroup will leave mount point and directory setup entirely to the administrators' discretion and is more complex than just adding some mount points to /etc/fstab . It is necessary to setup the directory hierarchy and decide how processes get placed within it. This can be done with the following virsh commands: schedinfo - described in Section 14.19, "Setting Schedule Parameters" blkiotune - described in Section 14.20, "Display or Set Block I/O Parameters" domiftune - described in Section 14.5.9, "Setting Network Interface Bandwidth Parameters" memtune - described in Section 14.21, "Configuring Memory Tuning"

Commands:
8.46. dnsmasq 8.46.1. RHBA-2014:0757 - dnsmasq bug fix update Updated dnsmasq packages that fix one bug are now available for Red Hat Enterprise Linux 6. The dnsmasq packages contain Dnsmasq, a lightweight domain name system (DNS) forwarder and dynamic host configuration protocol (DHCP) server. Bug Fix BZ# 991473 Previously, the Dnsmasq service status verification in the init script was not sufficiently robust and only determined the presence of all the instances of Dnsmasq running on the system. As a consequence, the init script identified Dnsmasq as running even when no Dnsmasq system instance had been initiated. The init script has been fixed to explicitly verify the process with the process ID written in the PID file of the system instance. As a result, the status of the Dnsmasq system instance is now identified correctly even if there are running instances not started by the init script. Users of dnsmasq are advised to upgrade to these updated packages, which fix this bug.

Commands:
19.2. Problems After Installation 19.2.1. Remote Graphical Desktops and XDMCP If you have installed the X Window System and would like to log in to your Red Hat Enterprise Linux system using a graphical login manager, enable the X Display Manager Control Protocol (XDMCP). This protocol allows users to remotely log in to a desktop environment from any X-compatible client, such as a network-connected workstation or X11 terminal. The procedure below explains how to enable XDMCP. Procedure 19.3. Enabling XDMCP on IBM Z Open the /etc/gdm/custom.conf configuration file in a plain text editor such as vi or nano . In the custom.conf file, locate the section starting with [xdmcp] . In this section, add the following line: Save the file, and exit the text editor. Restart the X Window System . To do this, either reboot the whole system, or restart the GNOME Display Manager using the following command as root : Wait for the login prompt to appear again, and log in using your normal user name and password. The IBM Z server is now configured for XDMCP. You can connect to it from another workstation (client) by starting a remote X session using the X command on the client workstation. For example: Replace address with the host name of the remote X11 server. The command connects to the remote X11 server using XDMCP and displays the remote graphical login screen on display :1 of the X11 server system (usually accessible by pressing Ctrl - Alt - F8 ). You can also access remote desktop sessions using a nested X11 server, which opens the remote desktop as a window in your current X11 session. Xnest allows users to open a remote desktop nested within their local X11 session. For example, run Xnest using the following command, replacing address with the host name of the remote X11 server: For more information about XDMCP, see the X Window System documentation at http://www.x.org/releases/X11R7.6/doc/libXdmcp/xdmcp.html . 19.2.2. Is Your System Displaying Signal 11 Errors? A signal 11 error, commonly known as a segmentation fault , means that a program accessed a memory location that was not assigned to it. A signal 11 error can occur due to a bug in one of the software programs that is installed, or faulty hardware. If you receive a fatal signal 11 error during the installation, first make sure you are using the most recent installation images, and let Anaconda verify them to make sure they are not corrupted. Bad installation media (such as an improperly burned or scratched optical disk) are a common cause of signal 11 errors. Verifying the integrity of the installation media is recommended before every installation. For information about obtaining the most recent installation media, see Chapter 2, Downloading Red Hat Enterprise Linux . To perform a media check before the installation starts, append the rd.live.check boot option at the boot menu. See Section 23.2.2, "Verifying Boot Media" for details. Other possible causes are beyond this document's scope. Consult your hardware manufacturer's documentation for more information.

Commands:
Enable=true
systemctl restart gdm.service
X :1 -query address
Xnest :1 -query address
8.2.4.3. Network By itself, a network cannot act as backup media. But combined with mass storage technologies, it can serve quite well. For instance, by combining a high-speed network link to a remote data center containing large amounts of disk storage, suddenly the disadvantages about backing up to disks mentioned earlier are no longer disadvantages. By backing up over the network, the disk drives are already off-site, so there is no need for transporting fragile disk drives anywhere. With sufficient network bandwidth, the speed advantage you can get from backing up to disk drives is maintained. However, this approach still does nothing to address the matter of archival storage (though the same "spin off to tape after the backup" approach mentioned earlier can be used). In addition, the costs of a remote data center with a high-speed link to the main data center make this solution extremely expensive. But for the types of organizations that need the kind of features this solution can provide, it is a cost they gladly pay.

Commands:
3.6. Bonding Modes Red Hat Virtualization uses Mode 4 by default, but supports the following common bonding modes: Mode 0 (round-robin policy) Transmits packets through network interface cards in sequential order. Packets are transmitted in a loop that begins with the first available network interface card in the bond and end with the last available network interface card in the bond. All subsequent loops then start with the first available network interface card. Mode 0 offers fault tolerance and balances the load across all network interface cards in the bond. However, Mode 0 cannot be used in conjunction with bridges, and is therefore not compatible with virtual machine logical networks. Mode 1 (active-backup policy) Sets all network interface cards to a backup state while one network interface card remains active. In the event of failure in the active network interface card, one of the backup network interface cards replaces that network interface card as the only active network interface card in the bond. The MAC address of the bond in Mode 1 is visible on only one port to prevent any confusion that might otherwise be caused if the MAC address of the bond changed to reflect that of the active network interface card. Mode 1 provides fault tolerance and is supported in Red Hat Virtualization. Mode 2 (XOR policy) Selects the network interface card through which to transmit packets based on the result of an XOR operation on the source and destination MAC addresses modulo network interface card slave count. This calculation ensures that the same network interface card is selected for each destination MAC address used. Mode 2 provides fault tolerance and load balancing and is supported in Red Hat Virtualization. Mode 3 (broadcast policy) Transmits all packets to all network interface cards. Mode 3 provides fault tolerance and is supported in Red Hat Virtualization. Mode 4 (IEEE 802.3ad policy) Creates aggregation groups in which the interfaces share the same speed and duplex settings. Mode 4 uses all network interface cards in the active aggregation group in accordance with the IEEE 802.3ad specification and is supported in Red Hat Virtualization. Mode 5 (adaptive transmit load balancing policy) Ensures the distribution of outgoing traffic accounts for the load on each network interface card in the bond and that the current network interface card receives all incoming traffic. If the network interface card assigned to receive traffic fails, another network interface card is assigned to the role of receiving incoming traffic. Mode 5 cannot be used in conjunction with bridges, therefore it is not compatible with virtual machine logical networks. Mode 6 (adaptive load balancing policy) Combines Mode 5 (adaptive transmit load balancing policy) with receive load balancing for IPv4 traffic without any special switch requirements. ARP negotiation is used for balancing the receive load. Mode 6 cannot be used in conjunction with bridges, therefore it is not compatible with virtual machine logical networks.

Commands:
Chapter 4. Prerequisites The installation of Ansible Automation Platform 2.3 for this reference environment uses the following: Red Hat OpenShift Platform 4.12 Appendix C, Applying labels and taints to Red Hat OpenShift node An Amazon S3 bucket to handle the ReadWriteMany storage requirement for automation hub Warning The installation of AAP 2.3 requires at least version Red Hat OpenShift 4.9. For more details, visit the Red Hat Ansible Automation Platform Life Cycle page. Note There are many methods to deploy Red Hat OpenShift. The size of your Red Hat OpenShift cluster will depend on the specific requirements of your applications (not just Ansible Automation Platform). Factors to consider include the number of users accessing the cluster, the amount of data and resources that the applications require to run, and your scalability and redundancy requirements. For details on how to deploy Red Hat OpenShift, visit the Install Guide In addition to the install guide above, review the OpenShift 4 Resources Configuration: Methodology and Tools blog article to assist in determining the appropriate cluster size based on your needs. Note Automation hub requires ReadWriteMany file-based storage, Azure Blob storage, or Amazon S3-compliant storage for operation so that multiple pods can access shared content, such as collections. This reference environment takes advantage of creating an Amazon S3 bucket to fulfill the request of ReadWriteMany storage. Details Appendix D, Create an Amazon S3 bucket .

Commands:
Chapter 42. Desktop spice component, BZ# 1030024 Video playback on a Red Hat Enterprise Linux 7.1 guest with GNOME Shell is sometimes not detected as a video stream by spice-server . The video stream is therefore not compressed in such a case. gobject-introspection component, BZ# 1076414 The gobject-introspection library is not available in a 32-bit multilib package. Users who wish to compile 32-bit applications that rely on GObject introspection or libraries that use it, such as GTK+ or GLib , should use the mock package to set up a build environment for their applications. kernel component, BZ#1183631 Due to a bug, the X.Org X server running on a Lenovo T440s laptop crashes if the laptop is removed from a docking station while an external monitor is attached. All applications running in the GUI are terminated, which leads to potential loss of unsaved data. To work around this problem, detach the laptop from the docking station while the laptop's lid is closed, or unplug all monitors from the docking station first. firefox component, BZ#1162691 The icedtea-web Java plugin does not load in Firefox when running on Red Hat Enterprise Linux for POWER, little endian, architecture. Consequently, Java Web Start (javaws) does not work in this environment. Firefox supports NPAPI plugins for Intel P6, AMD64 and Intel 64 systems, PowerPC platform (32bit), and ARM architectures. All other architectures are not supported by Firefox at the moment and there is no plan to extend it.

Commands:
Appendix D. Command-Line Tools AMQ Broker includes a set of command-line interface (CLI) tools so you can manage your messaging journal. The table below lists the name for each tool and its description. Table D.1. Command-line tools Tool Description exp Exports the message data using a special and independent XML format. imp Imports the journal to a running broker using the output provided by exp . data Prints reports about journal records and compacts their data. encode Shows an internal format of the journal encoded to String. decode Imports the internal journal format from encode. For a full list of commands available for each tool, use the help parameter followed by the tool's name. In the example below, the CLI output lists all the commands available to the data tool after the user entered the command ./artemis help data . You can use the help at the tool for more information on how to execute each of the tool's commands. For example, the CLI lists more information about the data print command after the user enters the ./artemis help data print .

Commands:
./artemis help data NAME artemis data - data tools group (print|imp|exp|encode|decode|compact) (example ./artemis data print) SYNOPSIS artemis data artemis data compact [--broker <brokerConfig>] [--verbose] [--paging <paging>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data decode [--broker <brokerConfig>] [--suffix <suffix>] [--verbose] [--paging <paging>] [--prefix <prefix>] [--file-size <size>] [--directory <directory>] --input <input> [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data encode [--directory <directory>] [--broker <brokerConfig>] [--suffix <suffix>] [--verbose] [--paging <paging>] [--prefix <prefix>] [--file-size <size>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data exp [--broker <brokerConfig>] [--verbose] [--paging <paging>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] artemis data imp [--host <host>] [--verbose] [--port <port>] [--password <password>] [--transaction] --input <input> [--user <user>] artemis data print [--broker <brokerConfig>] [--verbose] [--paging <paging>] [--journal <journal>] [--large-messages <largeMessges>] [--bindings <binding>] COMMANDS With no arguments, Display help information print Print data records information (WARNING: don't use while a production server is running)
./artemis help data print NAME artemis data print - Print data records information (WARNING: don't use while a production server is running) SYNOPSIS artemis data print [--bindings <binding>] [--journal <journal>] [--paging <paging>] OPTIONS --bindings <binding> The folder used for bindings (default ../data/bindings) --journal <journal> The folder used for messages journal (default ../data/journal) --paging <paging> The folder used for paging (default ../data/paging)
Chapter 2. Installing the Red Hat JBoss Core Services 2.4.57 You can install the Apache HTTP Server 2.4.57 on Red Hat Enterprise Linux or Windows Server. For more information, see the following sections of the installation guide: Installing the JBCS Apache HTTP Server on RHEL from archive files Installing the JBCS Apache HTTP Server on RHEL from RPM packages Installing the JBCS Apache HTTP Server on Windows Server

Commands: