mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Manual stopping of a dynamic JFR recording The Cryostat agent does not currently support the automatic stopping of dynamic JFR recordings. In this release, a dynamic JFR recording does not stop even if the conditions that triggered the recording are no longer being met. In this situation, if you want a dynamic JFR recording to stop, you must stop the recording manually from the Active Recordings tab in the Cryostat web console. For more information about using the Cryostat web console to stop JFR recordings, see Creating a JFR recording with Cryostat .

Commands:
Chapter 8. Disabling the web console in OpenShift Container Platform You can disable the OpenShift Container Platform web console. 8.1. Prerequisites Deploy an OpenShift Container Platform cluster. 8.2. Disabling the web console You can disable the web console by editing the consoles.operator.openshift.io resource. Edit the consoles.operator.openshift.io resource: USD oc edit consoles.operator.openshift.io cluster The following example displays the parameters from this resource that you can modify: apiVersion: operator.openshift.io/v1 kind: Console metadata: name: cluster spec: managementState: Removed 1 1 Set the managementState parameter value to Removed to disable the web console. The other valid values for this parameter are Managed , which enables the console under the cluster's control, and Unmanaged , which means that you are taking control of web console management.

Commands:
oc edit consoles.operator.openshift.io cluster
apiVersion: operator.openshift.io/v1 kind: Console metadata: name: cluster spec: managementState: Removed 1
14.3. Restoring a bad file When bad files are revealed by the scrubber, you can perform the following process to heal the file by recovering a copy from a replicate volume. Important The following procedure is easier if GFID-to-path translation is enabled. Mount all volumes using the -oaux-gfid-mount mount option, and enable GFID-to-path translation on each volume by running the following command. Files created before this option was enabled must be looked up with the find command. Procedure 14.1. Restoring a bad file from a replicate volume Note the identifiers of bad files Check the output of the scrub status command to determine the identifiers of corrupted files. Determine the path of each corrupted object For files created after GFID-to-path translation was enabled, use the getfattr command to determine the path of the corrupted files. For files created before GFID-to-path translation was enabled, use the find command to determine the path of the corrupted file and the index file that match the identifying GFID. Delete the corrupted files Delete the corrupted files from the path output by the getfattr or find command. Delete the GFID file Delete the GFID file from the /rhgs/brick N /.glusterfs directory. Restore the file Follow these steps to safely restore corrupt files. Disable metadata caching If the metadata cache is enabled, disable it by running the following command: Create a recovery mount point Create a mount point to use for the recovery process. For example, /mnt/recovery . Mount the volume with timeouts disabled Heal files and hard links Access files and hard links to heal them. For example, run the stat command on the files and hard links you need to heal. If you do not have client self-heal enabled, you must manually heal the volume with the following command. Unmount and optionally remove the recovery mount point Optional: Re-enable metadata caching If the metadata cache was enabled previously, re-enable it by running the following command: The time that the bitrot scrubber runs, this GFID is no longer listed (unless it has become corrupted again).

Commands:
gluster volume set VOLNAME build-pgfid on
gluster volume bitrot VOLNAME scrub status Volume name: VOLNAME Node name: NODENAME Error count: 3 Corrupted objects: 5f61ade8-49fb-4c37-af84-c95041ff4bf5 e8561c6b-f881-499b-808b-7fa2bce190f7 eff2433f-eae9-48ba-bdef-839603c9434c
getfattr -n glusterfs.ancestry.path -e text /mnt/ VOLNAME /.gfid/ GFID glusterfs.ancestry.path=" /path/to/corrupted_file "
find /rhgs/brick*/.glusterfs -name GFID /rhgs/brick1/.glusterfs/ path/to/GFID
find /rhgs -samefile /rhgs/brick1/.glusterfs/ path/to/GFID /rhgs/brick1/.glusterfs/ path/to/GFID /rhgs/brick1/ path/to/corrupted_file
gluster volume set VOLNAME stat-prefetch off
mkdir /mnt/recovery
mount -t glusterfs -o attribute-timeout=0,entry-timeout=0 hostname : volume-path /mnt/recovery
stat /mnt/recovery/ corrupt-file
gluster volume heal VOLNAME
umount /mnt/recovery rmdir /mnt/recovery
gluster volume set VOLNAME stat-prefetch on
Chapter 142. KafkaMirrorMaker2ConnectorSpec schema reference Used in: KafkaMirrorMaker2MirrorSpec Property Property type Description tasksMax integer The maximum number of tasks for the Kafka Connector. config map The Kafka Connector configuration. The following properties cannot be set: connector.class, tasks.max. autoRestart AutoRestart Automatic restart of connector and tasks configuration. pause boolean The pause property has been deprecated. Deprecated in Streams for Apache Kafka 2.6, use state instead. Whether the connector should be paused. Defaults to false. state string (one of [running, paused, stopped]) The state the connector should be in. Defaults to running.

Commands:
Chapter 1. Migration to Red Hat build of OpenJDK 21 The Migrating to Red Hat build of OpenJDK 21 from earlier versions guide provides information on how to upgrade your Java applications in Red Hat build of OpenJDK version 8, 11, or 17 to Red Hat build of OpenJDK 21. This guide describes changes in the Red Hat build of OpenJDK 21 release, including new features and deprecated or removed APIs, that might impact your migration from an earlier version of Red Hat build of OpenJDK. If you are migrating from Red Hat build of OpenJDK 11 or earlier, this guide also describes the changes that were introduced in Red Hat build of OpenJDK 17. If you want to migrate from Red Hat build of OpenJDK 11 or earlier, ensure that you also familiarize yourself with the major differences between versions 11 and 17 . If you are migrating from Red Hat build of OpenJDK 8, this guide also describes the changes that were introduced in Red Hat build of OpenJDK 11. If you want to migrate from Red Hat build of OpenJDK 8, ensure that you also familiarize yourself with the major differences between versions 8 and 11 . The OpenJDK project is known for its conservative approach to providing updates and for providing backward compatibility. However, to guarantee the evolution, security and stability of the project, the Red Hat build of OpenJDK project might sometimes introduce a few incompatibilities across major releases of Red Hat build of OpenJDK. These incompatibilities are relevant for the following scenarios: When you use APIs that are considered obsolete or unsecure When you access internals of the project that are considered implementation details and not public or supported API details Note Red Hat recommends that you migrate to the latest supported Red Hat build of OpenJDK distribution. 1.1. About Red Hat build of OpenJDK distributions OpenJDK is the free and open source reference implementation of the Java Platform, Standard Edition (Java SE). Red Hat build of OpenJDK distributions are based on the upstream OpenJDK 8u, OpenJDK 11u, OpenJDK 17u, and OpenJDK 21u projects. The Shenandoah Garbage Collector is included in all supported versions of Red Hat build of OpenJDK. All versions of Red Hat build of OpenJDK provide the following benefits: Multi-platform Red Hat build of OpenJDK is supported on RHEL and Microsoft Windows, so you can standardize applications on a single Java platform across desktop, data center, and hybrid cloud environments. Frequent releases Red Hat delivers quarterly updates of JRE and JDK for Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 distributions. These updates are available as archive, RPM, and Windows MSI-based installer files and container images. Long-term support Red Hat supports the recently released Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, Red Hat build of OpenJDK 17, and Red Hat build of OpenJDK 21 distributions. Additional resources For more information about the support lifecycle, see OpenJDK Life Cycle and Support Policy .

Commands:
Chapter 135. KafkaBridgeHttpConfig schema reference Used in: KafkaBridgeSpec Full list of KafkaBridgeHttpConfig schema properties Configures HTTP access to a Kafka cluster for the Kafka Bridge. The default HTTP configuration is for the Kafka Bridge to listen on port 8080. Example Kafka Bridge HTTP configuration apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # ... http: port: 8080 cors: allowedOrigins: "https://strimzi.io" allowedMethods: "GET,POST,PUT,DELETE,OPTIONS,PATCH" # ... As well as enabling HTTP access to a Kafka cluster, HTTP properties provide the capability to enable and define access control for the Kafka Bridge through Cross-Origin Resource Sharing (CORS). CORS is a HTTP mechanism that allows browser access to selected resources from more than one origin. To configure CORS, you define a list of allowed resource origins and HTTP access methods. For the origins, you can use a URL or a Java regular expression. 135.1. KafkaBridgeHttpConfig schema properties Property Property type Description port integer The port which is the server listening on. cors KafkaBridgeHttpCors CORS configuration for the HTTP Bridge.

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # http: port: 8080 cors: allowedOrigins: "https://strimzi.io" allowedMethods: "GET,POST,PUT,DELETE,OPTIONS,PATCH" #
Chapter 1. Understanding ROSA Learn about Red Hat OpenShift Service on AWS (ROSA), interacting with ROSA by using Red Hat OpenShift Cluster Manager and command line interface (CLI) tools, consumption experience, and integration with Amazon Web Services (AWS) services. 1.1. About ROSA ROSA is a fully-managed, turnkey application platform that allows you to focus on delivering value to your customers by building and deploying applications. Red Hat site reliability engineering (SRE) experts manage the underlying platform so you do not have to worry about the complexity of infrastructure management. ROSA provides seamless integration with Amazon CloudWatch, AWS Identity and Access Management (IAM), Amazon Virtual Private Cloud (VPC), and a wide range of additional AWS services to further accelerate the building and delivering of differentiating experiences to your customers. You subscribe to the service directly from your AWS account. After you create clusters, you can operate your clusters with the OpenShift web console, the ROSA CLI, or through Red Hat OpenShift Cluster Manager. You receive OpenShift updates with new feature releases and a shared, common source for alignment with OpenShift Container Platform. ROSA supports the same versions of OpenShift as Red Hat OpenShift Dedicated and OpenShift Container Platform to achieve version consistency. For additional information about ROSA installation, see Installing Red Hat OpenShift Service on AWS (ROSA) interactive walkthrough . 1.2. Billing and pricing Red Hat OpenShift Service on AWS is billed directly to your Amazon Web Services (AWS) account. ROSA pricing is consumption based, with annual commitments or three-year commitments for greater discounting. The total cost of ROSA consists of two components: ROSA service fees AWS infrastructure fees Visit the Red Hat OpenShift Service on AWS Pricing page on the AWS website for more details. 1.3. Getting started To get started with deploying your cluster, ensure your AWS account has met the prerequisites, you have a Red Hat account ready, and follow the procedures outlined in Getting started with Red Hat OpenShift Service on AWS . Additional resources OpenShift Cluster Manager Getting started with Red Hat OpenShift Service on AWS AWS pricing page

Commands:
Chapter 11. CertSecretSource schema reference Used in: ClientTls , KafkaAuthorizationKeycloak , KafkaAuthorizationOpa , KafkaClientAuthenticationOAuth , KafkaListenerAuthenticationOAuth Property Property type Description secretName string The name of the Secret containing the certificate. certificate string The name of the file certificate in the secret. pattern string Pattern for the certificate files in the secret. Use the glob syntax for the pattern. All files in the secret that match the pattern are used.

Commands:
Chapter 1. Extension APIs 1.1. APIService [apiregistration.k8s.io/v1] Description APIService represents a server for a particular GroupVersion. Name must be "version.group". Type object 1.2. CustomResourceDefinition [apiextensions.k8s.io/v1] Description CustomResourceDefinition represents a resource that should be exposed on the API server. Its name MUST be in the format <.spec.name>.<.spec.group>. Type object 1.3. MutatingWebhookConfiguration [admissionregistration.k8s.io/v1] Description MutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object. Type object 1.4. ValidatingWebhookConfiguration [admissionregistration.k8s.io/v1] Description ValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it. Type object

Commands:
Chapter 1. Overview Troubleshooting OpenShift Data Foundation is written to help administrators understand how to troubleshoot and fix their Red Hat OpenShift Data Foundation cluster. Most troubleshooting tasks focus on either a fix or a workaround. This document is divided into chapters based on the errors that an administrator may encounter: Chapter 2, Downloading log files and diagnostic information using must-gather shows you how to use the must-gather utility in OpenShift Data Foundation. Chapter 4, Commonly required logs for troubleshooting shows you how to obtain commonly required log files for OpenShift Data Foundation. Chapter 7, Troubleshooting alerts and errors in OpenShift Data Foundation shows you how to identify the encountered error and perform required actions. Warning Red Hat does not support running Ceph commands in OpenShift Data Foundation clusters (unless indicated by Red Hat support or Red Hat documentation) as it can cause data loss if you run the wrong commands. In that case, the Red Hat support team is only able to provide commercially reasonable effort and may not be able to restore all the data in case of any data loss.

Commands:
function::uaddr Name function::uaddr - User space address of current running task Synopsis Arguments None Description Returns the address in userspace that the current task was at when the probe occurred. When the current running task isn't a user space thread, or the address cannot be found, zero is returned. Can be used to see where the current task is combined with usymname or usymdata . Often the task will be in the VDSO where it entered the kernel.

Commands:
uaddr:long()
Preface Red Hat Quay container image registries let you store container images in a central location. As a regular user of a Red Hat Quay registry, you can create repositories to organize your images and selectively add read (pull) and write (push) access to the repositories you control. A user with administrative privileges can perform a broader set of tasks, such as the ability to add users and control default settings. This guide assumes you have a Red Hat Quay deployed and are ready to start setting it up and using it.

Commands:
8.239. telnet 8.239.1. RHBA-2014:0868 - telnet bug fix update Updated telnet packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Telnet is a popular protocol for logging in to remote systems over the Internet. The telnet-server packages include a telnet service that supports remote logins into the host machine. The telnet service is disabled by default. Bug Fixes BZ# 772912 Prior to this update, the telnet utility could enter an infinite loop when the user specified the "-b" parameter with a non-existing network interface. This update modifies the telnet command to print errors when users specify a non-existing network interface. BZ# 832059 Prior to this update, the in.telnetd service could fail to update information in the /var/run/utmp directory when a deadlock occurred in a telnet session. This update modifies telnetd to update /var/run/utmp correctly. Users of telnet are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.3. Store and retrieve data Even though the JCache API does not extend either java.util.Map or java.util.concurrent.ConcurrentMap it provides a key/value API to store and retrieve data: Contrary to standard java.util.Map , javax.cache.Cache comes with two basic put methods called put and getAndPut . The former returns void whereas the latter returns the value associated with the key. The equivalent of java.util.Map.put(K) in JCache is javax.cache.Cache.getAndPut(K) . Note Even though JCache API only covers standalone caching, it can be plugged with a persistence store, and has been designed with clustering or distribution in mind. The reason why javax.cache.Cache offers two put methods is because standard java.util.Map put call forces implementors to calculate the value. When a persistent store is in use, or the cache is distributed, returning the value could be an expensive operation, and often users call standard java.util.Map.put(K) without using the return value. Hence, JCache users need to think about whether the return value is relevant to them, in which case they need to call javax.cache.Cache.getAndPut(K) , otherwise they can call java.util.Map.put(K) which avoids returning the potentially expensive operation of returning the value. 23155%2C+Developer+Guide-6.630-06-2017+15%3A00%3A55JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
import javax.cache.*; import javax.cache.configuration.*; CacheManager cacheManager = Caching.getCachingProvider().getCacheManager(); Cache<String, String> cache = cacheManager.createCache("namedCache", new MutableConfiguration<String, String>()); cache.put("hello", "world"); // Notice that javax.cache.Cache.put(K) returns void! String value = cache.get("hello"); // Returns "world"
Chapter 17. Verifying the Red Hat Process Automation Manager installation After you have installed Red Hat Process Automation Manager, create an asset to verify that the installation is working. Procedure In a terminal window, navigate to the EAP_HOME /bin directory and enter the following command to start Red Hat Process Automation Manager: Note If you deployed Business Central without KIE Server, you can start Business Central with the standalone.sh script without specifying the standalone-full.xml file. In this case, ensure that you make any configuration changes to the standalone.xml file before starting Business Central. In a web browser, enter localhost:8080/business-central . If you configured Red Hat Process Automation Manager to run from a domain name, replace localhost with the domain name, for example: http://www.example.com:8080/business-central If you configured Red Hat Process Automation Manager to run in a cluster, replace localhost with the IP address of a particular node, for example: http://<node_IP_address>:8080/business-central Enter the admin user credentials that you created during installation. The Business Central home page appears. Select Menu Deploy Execution Servers . Confirm that default-kieserver is listed under Server Configurations . Select Menu Design Projects . Open the MySpace space. Click Try Samples Mortgages OK . The Assets window appears. Click Add Asset Data Object . Enter MyDataObject in the Data Object field and click OK . Click Spaces MySpace Mortgages and confirm that MyDataObject is in the list of assets. Delete the Mortgages project.

Commands:
./standalone.sh -c standalone-full.xml
16.2. Terminology This section explains the terms used throughout this chapter. libguestfs (Guest file system library) - the underlying C library that provides the basic functionality for opening disk images, reading and writing files and so on. You can write C programs directly to this API, but it is quite low level. guestfish (Guest file system interactive shell) is an interactive shell that you can use from the command line or from shell scripts. It exposes all of the functionality of the libguestfs API. Various virt tools are built on top of libguestfs, and these provide a way to perform specific single tasks from the command line. Tools include virt-df , virt-rescue , virt-resize and virt-edit . hivex and Augeas are libraries for editing the Windows Registry and Linux configuration files respectively. Although these are separate from libguestfs, much of the value of libguestfs comes from the combination of these tools. guestmount is an interface between libguestfs and FUSE. It is primarily used to mount file systems from disk images on your host physical machine. This functionality is not necessary, but can be useful.

Commands:
24.3. Associating Tags 24.3.1. Associating Tags With a Host, User or VM The collection referenced by link rel="tags" from a host , user or vms represents the set of tags associated with the entity. These tag representations also contain a host id , user id or vm id reference to the entity in question. Associating a tag with an entity is achieved by POST ing a tag reference (identifying the tag either by its id or name ) to the collection. Example 24.2. Associating a tag with a virtual machine 24.3.2. Removing a Tag Removing an association is achieved with a DELETE request to the appropriate element in the collection. Example 24.3. Removing a tag from a virtual machine 24.3.3. Querying a Collection for Tagged Resources To query the set of entities associated with a given tag, the collection/search URI template for the appropriate collection should be used to search for entities matching tag=MyTag . Example 24.4. Querying a collection for tagged resources

Commands:
POST /ovirt-engine/api/vms/5114bb3e-a4e6-44b2-b783-b3eea7d84720/tags HTTP/1.1 Accept: application/xml Content-Type: application/xml <tag> <name>Finance</name> </tag> HTTP/1.1 201 Created Content-Type: application/xml <tag id="f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e" href="/ovirt-engine/api/vms/5114bb3e-a4e6-44b2-b783-b3eea7d84720/tags/ f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e"> <name>Finance</name> <description>Resources for the Finance department</description> <vm id="5114bb3e-a4e6-44b2-b783-b3eea7d84720" href="/ovirt-engine/api/vms/5114bb3e-a4e6-44b2-b783-b3eea7d84720"/> </tag>
DELETE /ovirt-engine/api/vms/5114bb3e-a4e6-44b2-b783-b3eea7d84720/tags/f436ebfc-67f2-41bd-8ec6-902b6f7dcb5e HTTP/1.1 HTTP/1.1 204 No Content
GET /ovirt-engine/api/vms?search=tag%3DFinance HTTP/1.1 Accept: application/xml HTTP/1.1 200 OK Content-Type: application/xml <vms> <vm id="5114bb3e-a4e6-44b2-b783-b3eea7d84720" href="/ovirt-engine/api/vms/5114bb3e-a4e6-44b2-b783-b3eea7d84720"> </vm> </vms>