mtpti5iD/redhat-docs_dataset huggingface dataset:
4.312. system-config-kickstart 4.312.1. RHBA-2011:1683 - system-config-kickstart bug fix update An updated system-config-kickstart package that fixes a bug is now available for Red Hat Enterprise Linux 6. The system-config-kickstart package contains Kickstart Configurator, a graphical tool for creating kickstart files. Bug Fix BZ# 676338 The system-config-kickstart utility terminated with a traceback if it was executed outside of a graphical environment. This problem has been fixed: the utility starts correctly in a graphical environment or displays an error message if the X Window System is not running. All users of system-config-kickstart are advised to upgrade to this updated package, which resolves this bug.

Commands:
5.318. syslinux 5.318.1. RHBA-2012:0894 - syslinux bug fix update Updated syslinux packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The syslinux utility is responsible for booting the operating system kernel. Bug Fixes BZ# 729013 Prior to this update, the binaries were compiled without debugging information. As a consequence, the debuginfo files for some binaries were missing. With this update, the binaries include all required debug information. BZ# 806464 Prior to this update, the isohybrid utility failed with a seek error when attempting to write ISO images to a USB device. As a consequence, the ISO images were on some systems not bootable. This update modifies the underlying code so that isohybrid now successfully writes the images to USB devices. Users of syslinux are advised to upgrade to these updated packages, which which fix these bugs.

Commands:
10.2.2.3. Directory Indexing The deprecated FancyIndexing directive has now been removed. The same functionality is available through the FancyIndexing option within the IndexOptions directive. The VersionSort option to the IndexOptions directive causes files containing version numbers to be sorted in a more natural way. For example, httpd-2.0.6.tar appears before httpd-2.0.36.tar in a directory index page. The defaults for the ReadmeName and HeaderName directives have changed from README and HEADER to README.html and HEADER.html . For more on this topic, refer to the following documentation on the Apache Software Foundation's website: http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#indexoptions http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#readmename http://httpd.apache.org/docs-2.0/mod/mod_autoindex.html#headername

Commands:
Chapter 11. Relocating an application between managed clusters A relocation operation is very similar to failover. Relocate is application based and uses the DRPlacementControl to trigger the relocation. The main difference for relocation is that a resync is issued to make sure any new application data saved on the Secondary managed cluster is immediately, not waiting for the mirroring schedule interval, replicated to the Primary managed cluster. Procedure On the Hub cluster navigate to Installed Operators and then click Openshift DR Hub Operator . Click DRPlacementControl tab. Click DRPC busybox-drpc and then the YAML view. Modify action to Relocate DRPlacementControl modify action to Relocate Click Save . Verify if the application busybox is now running in the Primary managed cluster, failover cluster ocp4perf2 specified in the YAML file. Example output: Verify if busybox is running in the Secondary managed cluster. The busybox application should no longer be running on this managed cluster. Example output: Important Be aware of known Regional-DR issues as documented in Known Issues section of Release Notes. If you need assistance with developer preview features, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on availability and work schedules.

Commands:
oc get pods,pvc -n busybox-sample
NAME READY STATUS RESTARTS AGE pod/busybox 1/1 Running 0 60s NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE persistentvolumeclaim/busybox-pvc Bound pvc-79f2a74d-6e2c-48fb-9ed9-666b74cfa1bb 5Gi RWO ocs-storagecluster-ceph-rbd 61s
oc get pods,pvc -n busybox-sample
No resources found in busybox-sample namespace.
Chapter 2. Clustering corosync now tests for correct network interface configuration in RRP mode RRP does not work when the IP address/port number pairs are the same or the IP versions are mixed. Corosync now checks whether the network interfaces have a different IP address/port number pair and whether they use the same IP version. Support for fence_ilo_ssh fencing agent The fence_ilo_ssh fencing agent is a fence agent that connects to an iLO device. It logs into the device via ssh and reboots a specified outlet. For information on the parameters for the fence_ilo_ssh fencing agent, see the fence_ilo_ssh(8) man page. Support for fence_mpath fencing agent The fence_mpath fencing agent is an I/O fencing agent that uses SCSI-3 persistent reservations to control access to multipath devices. For information on the operation of this fencing agent and for descriptions of its parameters, see the fence_mpath(8) man page. Corosync UDPU now automatically sends messages to the appropriate ring members only Previously, when using UDPU, all messages were sent to all configured members, as opposed to only the active members. This is appropriate for merge detection messages, but for everything else it creates unnecessary traffic to missing members and may trigger excessive arp requests on the network. Corosync has been modified to send most UDPU messages to active members only, with the exception of messages required for proper detection of merge or new member (1-2 pkts/sec). Support for new SAPHanaTopology and SAPHana resource agents in Pacemaker The resource-agents-sap-hana package provides two Pacemaker resource agents, SAPHanaTopology and SAPHana. These resource agents allow you to configure a Pacemaker cluster to manage a SAP HANA Scale-Up System Replication environment on Red Hat Enterprise Linux. Support for fence_emerson fencing agent The fence_emerson fencing agent is a fence agent for Emerson over SNMP. It is an I/O fencing agent that can be used with MPX and MPH2 managed rack PDU. For information on the parameters for the fence_emerson fencing agent, see the fence_emerson(8) man page.

Commands:
Chapter 33. Case management Case management is an extension of Business Process Management (BPM) that enables you to manage adaptable business processes. BPM is a management practice used to automate tasks that are repeatable and have a common pattern, with a focus on optimization by perfecting a process. Business processes are usually modeled with clearly defined paths leading to a business goal. This requires a lot of predictability, usually based on mass-production principles. However, many real-world applications cannot be described completely from start to finish (including all possible paths, deviations, and exceptions). Using a process-oriented approach in certain cases can lead to complex solutions that are hard to maintain. Case management provides problem resolution for non-repeatable, unpredictable processes as opposed to the efficiency-oriented approach of BPM for routine, predictable tasks. It manages one-off situations when the process cannot be predicted in advance. A case definition usually consists of loosely coupled process fragments that can be connected directly or indirectly to lead to certain milestones and ultimately a business goal, while the process is managed dynamically in response to changes that occur during run time. In Red Hat Process Automation Manager, case management includes the following core process engine features: Case file instance A per case runtime strategy Case comments Milestones Stages Ad hoc fragments Dynamic tasks and processes Case identifier (correlation key) Case lifecycle (close, reopen, cancel, destroy) A case definition is always an ad hoc process definition and does not require an explicit start node. The case definition is the main entry point for the business use case. A process definition is introduced as a supporting construct of the case and can be invoked either as defined in the case definition or dynamically to bring in additional processing when required. A case definition defines the following new objects: Activities (required) Case file (required) Milestones Roles Stages

Commands:
Part III. Migrating an existing environment from synchronization to trust in the context of integrating a Linux domain with an Active Directory domain In RHEL 7, synchronization and trust were two possible approaches to indirect integration of RHEL systems to Active Directory (AD). In RHEL 8, synchronization is deprecated. If you have configured synchronisation between RHEL Identity Management (IdM) and AD in RHEL 7, Red Hat recommends migrating to the approach based on an IdM-AD trust instead. This chapter describes how to migrate an existing synchronization-based setup to AD trust. The following migrating options are available in IdM: Migrating from synchronization to trust automatically, by using ipa-winsync-migrate Migrating from synchronization to trust manually, by using ID views

Commands:
Chapter 13. Metrics A metrics endpoint, /api/v2/metrics/ is available in the API that produces instantaneous metrics about automation controller, which can be consumed by system monitoring software such as the open source project Prometheus. The types of data shown at the metrics/ endpoint are Content-type: text/plain and application/json . This endpoint contains useful information, such as counts of how many active user sessions there are, or how many jobs are actively running on each automation controller node. You can configure Prometheus to scrape these metrics from automation controller by hitting the automation controller metrics endpoint and storing this data in a time-series database. Clients can later use Prometheus in conjunction with other software such as Grafana or Metricbeat to visualize that data and set up alerts. 13.1. Setting up Prometheus To set up and use Prometheus, you must install Prometheus on a virtual machine or container. For more information, see the First steps with Prometheus documentation. Procedure In the Prometheus configuration file (typically prometheus.yml ), specify a <token_value> , a valid username and password for an automation controller user that you have created, and a <controller_host> . Note Alternatively, you can provide an OAuth2 token (which can be generated at /api/v2/users/N/personal_tokens/ ). By default, the configuration assumes a user with username= admin and password= password . Using an OAuth2 Token, created at the /api/v2/tokens endpoint to authenticate Prometheus with automation controller, the following example provides a valid scrape configuration if the URL for your automation controller's metrics endpoint is https://controller_host:443/metrics . scrape_configs - job_name: 'controller' tls_config: insecure_skip_verify: True metrics_path: /api/v2/metrics scrape_interval: 5s scheme: https bearer_token: <token_value> # basic_auth: # username: admin # password: password static_configs: - targets: - <controller_host> For help configuring other aspects of Prometheus, such as alerts and service discovery configurations, see the Prometheus configuration documentation. If Prometheus is already running, you must restart it to apply the configuration changes by making a POST to the reload endpoint, or by killing the Prometheus process or service. Use a browser to navigate to your graph in the Prometheus UI at http://<your_prometheus>:9090/graph and test out some queries. For example, you can query the current number of active automation controller user sessions by executing: awx_sessions_total{type="user"} . Refer to the metrics endpoint in the automation controller API for your instance ( api/v2/metrics ) for more ways to query.

Commands:
scrape_configs - job_name: 'controller' tls_config: insecure_skip_verify: True metrics_path: /api/v2/metrics scrape_interval: 5s scheme: https bearer_token: <token_value> # basic_auth: # username: admin # password: password static_configs: - targets: - <controller_host>
Chapter 9. Viewing diagnostics Use the Diagnostics tab to view diagnostic information about the JVM via the JVM DiagnosticCommand and HotspotDiangostic interfaces. Note The functionality is similar to the Diagnostic Commands view in Java Mission Control (jmc) or the command line tool jcmd. The plugin will provide corresponding jcmd commands in some scenarios. Procedure To retrieve the number of instances of loaded classes and the amount of bytes they take up, click Class Histogram . If the operation is repeated, the tab shows the difference since last run. To view the JVM diagnostic flag setting, click the JVM flags . For a running JVM, you can also modify the flag settings. Additional resources The supported JVM depends on the platform, for more information go to one of the following sources: http://www.oracle.com/technetwork/java/vmoptions-jsp-140102.html http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html

Commands:
A.6. SELinux Login Problems SELinux maps only work for remote users, not for users with a local account. When a remote user logs in, authenticating against the IdM server, then the PAM SElinux modules create a file for that user in /etc/selinux/ policy_name /logins/ login . If that file does not exist, then it means that SSSD is not properly configured to use the IdM server as one of its identity providers. This is required for SELinux mapping to work. Configuring SSSD is covered in the Red Hat 6 Deployment Guide . If the file exists but the remote user was given the wrong SELinux context, then the pam_selinux module may not be properly configured in the PAM stack. This is the module that reads the SELinux information and sets the user context. If the module is missing, then nothing processes the SELinux map and the user is defined a default context on the system.

Commands:
7.127. libvirt-java 7.127.1. RHBA-2013:0325 - libvirt-java bug fix and enhancement update Updated libvirt-java packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libvirt-java packages provide Java bindings to use libvirt, which is the virtualization API to manage and interact with virtualization capabilities. Note The libvirt-java packages have been upgraded to upstream version 0.4.9, which provides a number of bug fixes and enhancements over the version. (BZ#838046) Bug Fix BZ#836920 Due to a failing Java Native Access (JNA) conversion, the "setSchedulerParameters()" method for domains did not process input parameters properly. With this update, the conversion process has been modified. As a result, setSchedulerParameters() now works as expected. All users of libvirt-java are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
2.3. Block Allocation Issues This section provides a summary of issues related to block allocation in GFS2 file systems. Even though applications that only write data typically do not care how or where a block is allocated, a little knowledge about how block allocation works can help you optimize performance. 2.3.1. Leave Free Space in the File System When a GFS2 file system is nearly full, the block allocator starts to have a difficult time finding space for new blocks to be allocated. As a result, blocks given out by the allocator tend to be squeezed into the end of a resource group or in tiny slices where file fragmentation is much more likely. This file fragmentation can cause performance problems. In addition, when a GFS2 is nearly full, the GFS2 block allocator spends more time searching through multiple resource groups, and that adds lock contention that would not necessarily be there on a file system that has ample free space. This also can cause performance problems. For these reasons, it is recommended that you not run a file system that is more than 85 percent full, although this figure may vary depending on workload.

Commands:
3.3.2. Conditional Statements In some cases, the output of a SystemTap script may be too big. To address this, you need to further refine the script's logic in order to delimit the output into something more relevant or useful to your probe. You can do this by using conditionals in handlers. SystemTap accepts the following types of conditional statements: If/Else Statements Format: The statement1 is executed if the condition expression is non-zero. The statement2 is executed if the condition expression is zero. The else clause ( else statement2 ) is optional. Both statement1 and statement2 can be statement blocks. Example 3.9. ifelse.stp Example 3.9, "ifelse.stp" is a script that counts how many virtual file system reads ( vfs_read ) and writes ( vfs_write ) the system performs within a 5-second span. When run, the script increments the value of the variable countread by 1 if the name of the function it probed matches vfs_read (as noted by the condition if (probefunc()=="vfs_read") ); otherwise, it increments countnonread ( else {countnonread ++} ). While Loops Format: So long as condition is non-zero the block of statements in statement are executed. The statement is often a statement block and it must change a value so condition will eventually be zero. For Loops Format: The for loop is simply shorthand for a while loop. The following is the equivalent while loop: Conditional Operators Aside from == ("is equal to"), you can also use the following operators in your conditional statements: >= Greater than or equal to <= Less than or equal to != Is not equal to

Commands:
if ( condition ) statement1 else statement2
global countread, countnonread probe kernel.function("vfs_read"),kernel.function("vfs_write") { if (probefunc()=="vfs_read") countread ++ else countnonread ++ } probe timer.s(5) { exit() } probe end { printf("VFS reads total %d\n VFS writes total %d\n", countread, countnonread) }
while ( condition ) statement
for ( initialization ; conditional ; increment ) statement
initialization while ( conditional ) { statement increment }
3.6.2. Adding a Member to a Running Cluster To add a member to a running cluster, follow the steps in this section. The starting point of the procedure is at the cluster-specific page that you navigate to from Choose a cluster to administer displayed on the cluster tab. At the detailed menu for the cluster (below the clusters menu), click Nodes . Clicking Nodes causes the display of an Add a Node element and a Configure element with a list of the nodes already configured in the cluster. (In addition, a list of the cluster nodes is displayed in the center of the page.) Click Add a Node . Clicking Add a Node causes the display of the Add a node to cluster name page. At that page, enter the node name in the Node Hostname text box; enter the root password in the Root Password text box. Check the Enable Shared Storage Support checkbox if clustered storage is required. If you want to add more nodes, click Add another entry and enter node name and password for the each additional node. Click Submit . Clicking Submit causes the following actions: Cluster software packages to be downloaded onto the added node. Cluster software to be installed (or verification that the appropriate software packages are installed) onto the added node. Cluster configuration file to be updated and propagated to each node in the cluster - including the added node. Joining the added node to cluster. A progress page shows the progress of those actions for each added node. When the process of adding a node is complete, a page is displayed providing a configuration interface for the cluster. At the detailed menu for the cluster (below the clusters menu), click Nodes . Clicking Nodes causes the following displays: A list of cluster nodes in the center of the page The Add a Node element and the Configure element with a list of the nodes configured in the cluster at the detailed menu for the cluster (below the clusters menu) Click the link for an added node at either the list in the center of the page or in the list in the detailed menu under the clusters menu. Clicking the link for the added node causes a page to be displayed for that link showing how that node is configured. At the bottom of the page, under Main Fencing Method , click Add a fence device to this level . Select a fence device and provide parameters for the fence device (for example port number). Note You can choose from an existing fence device or create a new fence device. Click Update main fence properties and wait for the change to take effect.

Commands:
Chapter 23. Additional resources Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 Planning a Red Hat Process Automation Manager installation Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 Deploying an Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 4 using Operators Deploying an Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 3 using templates

Commands:
Chapter 12. Importing an existing Maven project Overview You might want to import an existing project, for example, to use as a template or starting point for developing an application. For example, the New Fuse Integration Project wizard points to the following Github repositories as sources for examples: https://github.com/apache/camel/tree/master/examples https://github.com/fabric8-quickstarts https://github.com/wildfly-extras/wildfly-camel-examples https://github.com/jboss-fuse/quickstarts Procedure To import an existing Maven project: Select File Import Maven Existing Maven Projects , and then click . For the Root Directory, select the folder that contains the downloaded example projects. In the list of Projects, check the projects that you want to import and then click Finish .

Commands:
7.196. sg3_utils 7.196.1. RHEA-2015:1365 - sg3_utils enhancement update Updated sg3_utils packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The sg3_utils packages provide command-line utilities for devices that use the Small Computer System Interface (SCSI) command sets. Enhancement BZ# 1051363 With this update, the sg3_utils packages introduce more efficient utilities for copying data between storage devices which benefit from the Small Computer System Interface (SCSI) protocol. To enable this functionality, this update backports the sg_xcopy and sg_copy_results programs to the sg3_utils packages. Users of sg3_utils are advised to upgrade to these updated packages, which add this enhancement.

Commands:
9.5. The L1 Cache and Invalidation An invalidation message is generated each time a key is updated. This message is multicast to each node that contains data that corresponds to current L1 cache entries. The invalidation message ensures that each of these nodes marks the relevant entry as invalidated. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands: