mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 39. Clustering The pcs tool now manages bundle resources in Pacemaker As a Technology Preview starting with Red Hat Enterprise Linux 7.4, the pcs tool supports bundle resources. You can now use the pcs resource bundle create and the pcs resource bundle update commands to create and modify a bundle. You can add a resource to an existing bundle with the pcs resource create command. For information on the parameters you can set for a bundle resource, run the pcs resource bundle --help command. (BZ# 1433016 )

Commands:
Chapter 4. Configuring the remote node on the Nagios Core server Configure the Nagios Core server to be aware of the remote hosts. Prerequisites Root-level access to the remote node on the Nagios Core server. Internet access. Procedure Install the check_nrpe plug-in: Example Create a configuration for the remote host: Syntax Example Edit the configuration file and update the settings for the remote host: Syntax Example Syntax Replace LOCALHOST with the hostname of the remote host, and 127.0.0.1 with the IP address of the Ceph monitor host. Example Delete or comment out the Host Group definition: Example Change the file ownership to Nagios: Example Add a cfg_file= reference to the host01.cfg file in /usr/local/nagios/etc/nagios.cfg : Example Restart the Nagios server: Example Ensure that the make and install procedures worked and that there is connectivity between the Nagios Core server and the remote host containing NRPE: Syntax Replace HOSTNAME_OF_REMOTE_HOST with the IP address of the Ceph host to monitor. Example Verification The check should echo NRPE v4.0.3 if it is working correctly.

Commands:
cd ~ wget https://github.com/NagiosEnterprises/nrpe/releases/download/nrpe-4.0.3/nrpe-4.0.3.tar.gz tar xvfz nrpe-4.0.3.tar.gz cd nrpe-4.0.3 ./configure make check_nrpe make install-plugin
cd /usr/local/nagios/etc/objects cp localhost.cfg HOST_TO_ADD .cfg
cd /usr/local/nagios/etc/objects cp localhost.cfg host01.cfg
vi HOST_TO_ADD .cfg
vi host01.cfg
Define a host for the local machine define host { use linux-server ; Name of host template to use ; This host definition will inherit all variables that are defined ; in (or inherited by) the linux-server host template definition. host_name LOCALHOST alias LOCALHOST address 127.0.0.1 }
Define a host for the local machine define host { use linux-server ; Name of host template to use ; This host definition will inherit all variables that are defined ; in (or inherited by) the linux-server host template definition. host_name host01 alias host01 address 10.10.128.69 }
vi host01.cfg
#define hostgroup { # hostgroup_name linux-servers ; The name of the hostgroup alias Linux Servers ; Long name of the group members localhost ; Comma separated list of hosts that belong to this group #}
chown nagios:nagios host01.cfg
vi /usr/local/nagios/etc/nagios.cfg
cfg_file=/usr/local/nagios/etc/objects/host01.cfg
systemctl restart nagios
/usr/local/nagios/libexec/check_nrpe -H HOSTNAME_OF_REMOTE_HOST
/usr/local/nagios/libexec/check_nrpe -H host01
22.16.7. Adding a Broadcast Client Address To add a broadcast client address, that is to say, to configure a broadcast address to be monitored for broadcast NTP packets, make use of the broadcastclient command in the ntp.conf file. The broadcastclient command takes the following form: broadcastclient Enables the receiving of broadcast messages. Requires authentication by default. See Section 22.6, "Authentication Options for NTP" . This command configures a system to act as an NTP client. Systems can be both client and server at the same time.

Commands:
Chapter 26. Desktop Empathy now can validate certificate chains for Google Talk Previously, the Empathy instant messaging client was not able to validate the certificate chain for Google Talk by ignoring disabled legacy certificate authorities, such as Equifax Secure Certificate Authority, in the chain. As a consequence, Empathy prompted the user about an invalid certificate when connecting to Google Talk, even though there was no problem with the chain. This update fixes the bug and Empathy now ignores disabled legacy certificate authorities in the list returned by the server and attempts to construct alternate chains that might be valid. (BZ#1386616)

Commands:
24.2. Trouble During the Installation 24.2.1. The " No devices found to install Red Hat Enterprise Linux " Error Message If you receive an error message stating No devices found to install Red Hat Enterprise Linux , then there may be an issue with your DASD devices. If you encounter this error, add the DASD=< disks > parameter to your parameter file or CMS configuration file (where disks is the DASD range reserved for installation) and start the install again. Additionally, make sure you format the DASDs using the dasdfmt command within a Linux root shell, instead of formatting the DASDs using CMS. Anaconda automatically detects any DASD devices that are not yet formatted and asks you whether to format the devices.

Commands:
11.4. Methods 11.4.1. Creating a Network Resource Creation of a new network requires the name and datacenter elements. Example 11.3. Creating a network resource 11.4.2. Updating a Network Resource The name , description , ip , vlan , stp and display elements are updatable post-creation. Example 11.4. Updating a network resource 11.4.3. Removing a Network Resource Removal of a network requires a DELETE request. Example 11.5. Removing a network

Commands:
POST /ovirt-engine/api/networks HTTP/1.1 Accept: application/xml Content-type: application/xml <network> <name>network 1</name> <data_center id="00000000-0000-0000-0000-000000000000"/> </network>
PUT /ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000 HTTP/1.1 Accept: application/xml Content-type: application/xml <network> <description>Network 1</description> </network>
DELETE /ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000 HTTP/1.1 HTTP/1.1 204 No Content
B.92. system-config-firewall B.92.1. RHBA-2010:0942 - system-config-firewall bug fix update Updated system-config-firewall packages that fix a bug are now available for Red Hat Enterprise Linux 6. system-config-firewall is a graphical user interface for basic firewall setup. Bug Fix BZ# 636110 Prior to this update, certain dialog windows in the Tamil translation of the Firewall Configuration utility contained untranslated strings. With this update, the remaining strings have been translated into the Tamil language, so that dialog windows no longer contain English texts. Users of system-config-firewall are advised to upgrade to these updated packages, which resolve this issue.

Commands:
24.2.2. Logging Use the Logging tab to configure options for specific transfer and error logs. By default, the server writes the transfer log to the /var/log/httpd/access_log file and the error log to the /var/log/httpd/error_log file. The transfer log contains a list of all attempts to access the Web server. It records the IP address of the client that is attempting to connect, the date and time of the attempt, and the file on the Web server that it is trying to retrieve. Enter the name of the path and file in which to store this information. If the path and file name do not start with a slash (/), the path is relative to the server root directory as configured. This option corresponds to the TransferLog directive. Figure 24.4. Logging You can configure a custom log format by checking Use custom logging facilities and entering a custom log string in the Custom Log String field. This configures the LogFormat directive. Refer to http://httpd.apache.org/docs-2.0/mod/mod_log_config.html#formats for details on the format of this directive. The error log contains a list of any server errors that occur. Enter the name of the path and file in which to store this information. If the path and file name do not start with a slash (/), the path is relative to the server root directory as configured. This option corresponds to the ErrorLog directive. Use the Log Level menu to set the verbosity of the error messages in the error logs. It can be set (from least verbose to most verbose) to emerg, alert, crit, error, warn, notice, info or debug. This option corresponds to the LogLevel directive. The value chosen with the Reverse DNS Lookup menu defines the HostnameLookups directive. Choosing No Reverse Lookup sets the value to off. Choosing Reverse Lookup sets the value to on. Choosing Double Reverse Lookup sets the value to double. If you choose Reverse Lookup , your server automatically resolves the IP address for each connection which requests a document from your Web server. Resolving the IP address means that your server makes one or more connections to the DNS in order to find out the hostname that corresponds to a particular IP address. If you choose Double Reverse Lookup , your server performs a double-reverse DNS. In other words, after a reverse lookup is performed, a forward lookup is performed on the result. At least one of the IP addresses in the forward lookup must match the address from the first reverse lookup. Generally, you should leave this option set to No Reverse Lookup , because the DNS requests add a load to your server and may slow it down. If your server is busy, the effects of trying to perform these reverse lookups or double reverse lookups may be quite noticeable. Reverse lookups and double reverse lookups are also an issue for the Internet as a whole. Each individual connection made to look up each hostname adds up. Therefore, for your own Web server's benefit, as well as for the Internet's benefit, you should leave this option set to No Reverse Lookup .

Commands:
11.2.3. Creating a Swap File To add a swap file: Determine the size of the new swap file in megabytes and multiply by 1024 to determine the number of blocks. For example, the block size of a 64 MB swap file is 65536. At a shell prompt as root, type the following command with count being equal to the desired block size: Setup the swap file with the command: To enable the swap file immediately but not automatically at boot time: To enable it at boot time, edit /etc/fstab to include the following entry: The time the system boots, it enables the new swap file. After adding the new swap file and enabling it, verify it is enabled by viewing the output of the command cat /proc/swaps or free .

Commands:
dd if=/dev/zero of=/swapfile bs=1024 count=65536
mkswap /swapfile
swapon /swapfile
/swapfile swap swap defaults 0 0
17.2. Bridged Mode When using Bridged mode , all of the guest virtual machines appear within the same subnet as the host physical machine. All other physical machines on the same physical network are aware of the virtual machines, and can access the virtual machines. Bridging operates on Layer 2 of the OSI networking model. Figure 17.2. Virtual network switch in bridged mode It is possible to use multiple physical interfaces on the hypervisor by joining them together with a bond . The bond is then added to a bridge and then guest virtual machines are added onto the bridge as well. However, the bonding driver has several modes of operation, and only a few of these modes work with a bridge where virtual guest machines are in use. Warning When using bridged mode, the only bonding modes that should be used with a guest virtual machine are Mode 1, Mode 2, and Mode 4. Using modes 0, 3, 5, or 6 is likely to cause the connection to fail. Also note that Media-Independent Interface (MII) monitoring should be used to monitor bonding modes, as Address Resolution Protocol (ARP) monitoring does not work. For more information on bonding modes, see related Knowledgebase article , or the Red Hat Enterprise Linux 7 Networking Guide . For a detailed explanation of bridge_opts parameters, used to configure bridged networking mode, see the Red Hat Virtualization Administration Guide .

Commands:
Chapter 26. Artifact management You can manage artifacts from the Artifacts page in Business Central. The artifact repository is a local Maven repository and there is only one Maven repository for each installation. Business Central recommends using Maven repository solutions like Sonatype NexusTM , Apache ArchivaTM , or JFrog ArtifactoryTM . The Artifacts page lists all the artifacts in the Maven repository. You can upload artifacts to the Maven repository. Note You can only upload JAR, KJAR, and pom.xml files to the Artifacts repository. 26.1. Viewing an artifact You can view all the content of the local maven repository from the Artifacts page. Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Artifacts . Click Open to view the artifact details. Click Ok to go back to the Artifacts page. 26.2. Downloading an artifact You can download and save an artifact from Business Central repository to the local storage of a project. Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Artifacts . Click Download . Browse to the directory where you want to save the artifact. Click Save . 26.3. Uploading an artifact You can upload an artifact from the local storage to a project in Business Central. Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Artifacts . Click Upload . Click Choose File and browse to the directory from where you want to upload the artifact. Click Upload . Note If you are using a non-Maven artifact, first deploy the artifact to the Maven repository using the mvn deploy command and then refresh the artifact list in Business Central.

Commands:
Chapter 1. Preface In some of the example listings, what is meant to be displayed on one line does not fit inside the available page width. These lines have been broken up. A '\' at the end of a line means that a break has been introduced to fit in the page, with the following lines indented. So: Is really:

Commands:
Let's pretend to have an extremely long line that does not fit This one is short
Let's pretend to have an extremely long line that does not fit This one is short
1.3.2. Cluster Status Tool You can access the Cluster Status Tool ( Figure 1.7, " Cluster Status Tool " ) through the Cluster Management tab in Cluster Administration GUI. Figure 1.7. Cluster Status Tool The nodes and services displayed in the Cluster Status Tool are determined by the cluster configuration file ( /etc/cluster/cluster.conf ). You can use the Cluster Status Tool to enable, disable, restart, or relocate a high-availability service.

Commands:
Chapter 3. Important notes 3.1. AMQ C++ Unsettled interfaces The AMQ C++ messaging API includes classes and methods that are not yet proven and can change in future releases. Be aware that use of these interfaces might require changes to your application code in the future. These interfaces are marked Unsettled API in the API reference. They include the interfaces in the proton::codec and proton::io namespaces and the following interfaces in the proton namespace. listen_handler The on_sender_drain_start and on_sender_drain_finish methods on messaging_handler The draining and return_credit methods on sender The draining and drain methods on receiver API elements present in header files but not yet documented are considered unsettled and are subject to change. Deprecated interfaces Interfaces marked Deprecated in the API reference are scheduled for removal in a future release. This release deprecates the following interfaces in the proton namespace. void_function0 - Use the work class or C++11 lambdas instead. default_container - Use the container class instead. url and url_error - Use a third-party URL library instead. 3.2. Preferred clients In general, AMQ clients that support the AMQP 1.0 standard are preferred for new application development. However, the following exceptions apply: If your implementation requires distributed transactions, use the AMQ Core Protocol JMS client. If you require MQTT or STOMP in your domain (for IoT applications, for instance), use community-supported MQTT or STOMP clients. The considerations above do not necessarily apply if you are already using: The AMQ OpenWire JMS client (the JMS implementation previously provided in A-MQ 6) The AMQ Core Protocol JMS client (the JMS implementation previously provided with HornetQ) 3.3. Legacy clients Deprecation of the CMS and NMS APIs The ActiveMQ CMS and NMS messaging APIs are deprecated in AMQ 7. It is recommended that users of the CMS API migrate to AMQ C++, and users of the NMS API migrate to AMQ .NET. The CMS and NMS APIs might have reduced functionality in AMQ 7. Deprecation of the legacy AMQ C++ client The legacy AMQ C++ client (the C++ client previously provided in MRG Messaging) is deprecated in AMQ 7. It is recommended that users of this API migrate to AMQ C++. The Core API is unsupported The Artemis Core API client is not supported. This client is distinct from the AMQ Core Protocol JMS client, which is supported. 3.4. Upstream versions AMQ C++, AMQ Python, and AMQ Ruby are now based on Qpid Proton 0.32.0 . AMQ JavaScript is now based on Rhea 1.0.24 . AMQ .NET is now based on AMQP.Net Lite 2.4.0 . AMQ JMS is now based on Qpid JMS 0.53.0 . AMQ Core Protocol JMS is now based on ActiveMQ Artemis 2.11.0 . AMQ OpenWire JMS is now based on ActiveMQ 5.11.0 . AMQ JMS Pool is now based on Pooled JMS 1.1.1 . AMQ Resource Adapter is now based on AMQP 1.0 Resource Adapter 1.0.2 . AMQ Spring Boot Starter is now based on AMQP 1.0 JMS Spring Boot 2.3.3 . AMQ Netty OpenSSL is now based on netty-tcnative 2.0.31.Final .

Commands:
18.13.2. Creating TCP Tunnels A TCP client/server architecture provides a virtual network. In this configuration, one guest virtual machine provides the server end of the network while all other guest virtual machines are configured as clients. All network traffic is routed between the guest virtual machine clients via the guest virtual machine server. This mode is also available for unprivileged users. Note that this mode does not provide default DNS or DHCP support nor does it provide outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first four network types thus providing appropriate routing. To create a TCP tunnel place the following XML details into the <devices> element: ... <devices> <interface type='server'> <mac address='52:54:00:22:c9:42'> <source address='192.168.0.1' port='5558'/> </interface> ... <interface type='client'> <mac address='52:54:00:8b:c9:51'> <source address='192.168.0.1' port='5558'/> </interface> </devices> ... Figure 18.29. TCP tunnel domain XMl example

Commands:
<devices> <interface type='server'> <mac address='52:54:00:22:c9:42'> <source address='192.168.0.1' port='5558'/> </interface> <interface type='client'> <mac address='52:54:00:8b:c9:51'> <source address='192.168.0.1' port='5558'/> </interface> </devices>
8.64. hsqldb 8.64.1. RHBA-2013:1614 - hsqldb bug fix update Updated hsqldb packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The hsqldb packages provide a relational database management system written in Java. The Hyper Structured Query Language Database (HSQLDB) contains a JDBC driver to support a subset of ANSI-92 SQL. Bug Fixes BZ# 996152 Previously, the /etc/sysconfig/hsqldb file was not marked as "config(noreplace)". Consequently, reinstallation or update of the packages could overwrite changes to the configuration made by the user. With this update, the configuration file has been marked correctly, and modifications to the file are preserved during reinstallation or update. BZ# 962676 Prior to this update, the hsqldb database depended on java packages of version 1:1.6.0 or later, which are unavailable on some Red Hat Enterprise Linux 6 platforms. As a consequence, installing the hsqldb packages failed with an error message. With this update, java packages of version 0:1.5.0 or later are required, and the installation of hsqldb now proceeds correctly as expected. Users of hsqldb are advised to upgrade to these updated packages, which fix these bugs.

Commands:
11.3. Bridged Networking with libvirt Bridged networking (also known as physical device sharing) is used to dedicate a physical device to a virtual machine. Bridging is often used for more advanced setups and on servers with multiple network interfaces. To create a bridge ( br0 ) based on the eth0 interface, execute the following command on the host: Important NetworkManager does not support bridging. NetworkManager must be disabled to use networking with the network scripts (located in the /etc/sysconfig/network-scripts/ directory). If you do not want to disable NetworkManager entirely, add " NM_CONTROLLED=no " to the ifcfg-* network script being used for the bridge.

Commands:
virsh iface-bridge eth0 br0
chkconfig NetworkManager off chkconfig network on service NetworkManager stop service network start
Chapter 9. Red Hat build of Kogito on Red Hat OpenShift Container Platform You can deploy Red Hat build of Kogito microservices on Red Hat OpenShift Container Platform for cloud implementation. In this architecture, Red Hat build of Kogito microservices are deployed as OpenShift pods that you can scale up and down individually to provide as few or as many containers as required for a particular service. To help you deploy your Red Hat build of Kogito microservices on OpenShift, Red Hat Decision Manager provides Red Hat Process Automation Manager Kogito Operator . This operator guides you through the deployment process. The operator is based on the Operator SDK and automates many of the deployment steps for you. For example, when you provide the operator with a link to the Git repository that contains your application, the operator automatically configures the components required to build your project from source and deploys the resulting services. To install the Red Hat Process Automation Manager Kogito Operator in OpenShift web console, go to Operators OperatorHub in the left menu, search for and select RHPAM Kogito Operator , and follow the on-screen instructions to install the latest operator version.

Commands:
Chapter 4. Requirements To begin using simple content access, you must meet the following software requirements. For simple content access with Red Hat Subscription Management: Simple content access enabled within Red Hat Subscription Management. For simple content access with Red Hat Satellite: Satellite 6.14 or later (versions that are under full or maintenance support). Earlier versions of Satellite can be used with simple content access, but migration to a supported version of Satellite is recommended. Note For Satellite version support information, see the Red Hat Satellite Product Life Cycle life cycle and update policy document. Simple content access enabled, where required. Satellite version 6.16 supports only simple content access. Manual enablement of simple content access is not required for versions 6.16 and later. Satellite versions 6.15 and 6.14 (and 6.13, reaching end of life (EOL) in November 2024), simple content access enabled for each Satellite organization. Any simple content access setting on the manifest is ignored; the setting on the Satellite organization takes precedence. Satellite versions 6.12 and earlier (EOL versions that are not supported), simple content access enabled for each allocation and manifest. In addition, enabled manifests must be refreshed for simple content access to take effect.

Commands:
Chapter 1. About Red Hat OpenShift Pipelines Red Hat OpenShift Pipelines is a cloud-native, continuous integration and continuous delivery (CI/CD) solution based on Kubernetes resources. It uses Tekton building blocks to automate deployments across multiple platforms by abstracting away the underlying implementation details. Tekton introduces a number of standard custom resource definitions (CRDs) for defining CI/CD pipelines that are portable across Kubernetes distributions. Note Because Red Hat OpenShift Pipelines releases on a different cadence from OpenShift Container Platform, the Red Hat OpenShift Pipelines documentation is now available as a separate documentation set at Red Hat OpenShift Pipelines .

Commands: