mtpti5iD/redhat-docs_dataset huggingface dataset:
16.3. Removing a Guest Virtual Machine Entry If the guest virtual machine is running, unregister the system, by running the following command in a terminal window as root on the guest: If the system has been deleted, however, the virtual service cannot tell whether the service is deleted or paused. In that case, you must manually remove the system from the server side, using the following steps: Login to the Subscription Manager The Subscription Manager is located on the Red Hat Customer Portal . Login to the Customer Portal using your user name and password, by clicking the login icon at the top of the screen. Click the Subscriptions tab Click the Subscriptions tab. Click the Systems link Scroll down the page and click the Systems link. Delete the system To delete the system profile, locate the specified system's profile in the table, select the check box beside its name and click Delete .

Commands:
subscription-manager unregister
Chapter 159. Ignite ID Generator Component Available as of Camel version 2.17 The Ignite ID Generator endpoint is one of camel-ignite endpoints which allows you to interact with Ignite Atomic Sequences and ID Generators . This endpoint only supports producers. 159.1. Options The Ignite ID Generator component supports 4 options, which are listed below. Name Description Default Type ignite (producer) Sets the Ignite instance. Ignite configurationResource (producer) Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. Object igniteConfiguration (producer) Allows the user to set a programmatic IgniteConfiguration. IgniteConfiguration resolveProperty Placeholders (advanced) Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true boolean The Ignite ID Generator endpoint is configured using URI syntax: with the following path and query parameters: 159.1.1. Path Parameters (1 parameters): Name Description Default Type name Required The sequence name. String 159.1.2. Query Parameters (6 parameters): Name Description Default Type batchSize (producer) The batch size. Integer initialValue (producer) The initial value. 0 Long operation (producer) The operation to invoke on the Ignite ID Generator. Superseded by the IgniteConstants.IGNITE_IDGEN_OPERATION header in the IN message. Possible values: ADD_AND_GET, GET, GET_AND_ADD, GET_AND_INCREMENT, INCREMENT_AND_GET. IgniteIdGenOperation propagateIncomingBodyIfNo ReturnValue (producer) Sets whether to propagate the incoming body if the return type of the underlying Ignite operation is void. true boolean treatCollectionsAsCache Objects (producer) Sets whether to treat Collections as cache objects or as Collections of items to insert/update/compute, etc. false boolean synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean 159.2. Spring Boot Auto-Configuration The component supports 5 options, which are listed below. Name Description Default Type camel.component.ignite-idgen.configuration-resource Sets the resource from where to load the configuration. It can be a: URI, String (URI) or an InputStream. The option is a java.lang.Object type. String camel.component.ignite-idgen.enabled Enable ignite-idgen component true Boolean camel.component.ignite-idgen.ignite Sets the Ignite instance. The option is a org.apache.ignite.Ignite type. String camel.component.ignite-idgen.ignite-configuration Allows the user to set a programmatic IgniteConfiguration. The option is a org.apache.ignite.configuration.IgniteConfiguration type. String camel.component.ignite-idgen.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean

Commands:
ignite-idgen:name
8.200. sg3_utils 8.200.1. RHBA-2013:0956 - sg3_utils bug fix update Updated sg3_utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The sg3_utils packages contain a collection of tools for SCSI devices that use the Linux SCSI generic (sg) interface. This collection includes utilities for database copying based on "dd" syntax and semantics (the "sg_dd", "sgp_dd" and "sgm_dd" commands), INQUIRY data checking and associated pages ("sg_inq"), mode and log page checking ("sg_modes" and "sg_logs"), disk spinning ("sg_start") and self-tests ("sg_senddiag"), as well as other utilities. It also contains the rescan-scsi-bus.sh script. Bug Fix BZ# 920687 The logic used in the show_devices() function (as used by the "sginfo" command) to identify the available storage devices opened these devices by scanning the /dev directory. Consequently, the /dev/snapshot file was opened, causing the system to prepare for suspend/hibernate and, as a part of that, to block hot-added CPUs from being activated. To fix this bug, the logic used in the show_devices() function to decide, which devices to open, has been adjusted. As a result, running the "sginfo -l" command no longer has the unintended side effect of blocking the activation of hot-added CPUs. Users of sg3_utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 20. OpenSSH OpenSSH is a free, open source implementation of the SSH ( S ecure S H ell) protocols. It replaces telnet , ftp , rlogin , rsh , and rcp with secure, encrypted network connectivity tools. OpenSSH supports versions 1.3, 1.5, and 2 of the SSH protocol. Since OpenSSH version 2.9, the default protocol is version 2, which uses RSA keys as the default. 20.1. Why Use OpenSSH? If you use OpenSSH tools, you are enhancing the security of your machine. All communications using OpenSSH tools, including passwords, are encrypted. Telnet and ftp use plain text passwords and send all information unencrypted. The information can be intercepted, the passwords can be retrieved, and your system could be compromised by an unauthorized person logging in to your system using one of the intercepted passwords. The OpenSSH set of utilities should be used whenever possible to avoid these security problems. Another reason to use OpenSSH is that it automatically forwards the DISPLAY variable to the client machine. In other words, if you are running the X Window System on your local machine, and you log in to a remote machine using the ssh command, when you run a program on the remote machine that requires X, it will be displayed on your local machine. This feature is convenient if you prefer graphical system administration tools but do not always have physical access to your server.

Commands:
26.8. Sample Parameter File and CMS Configuration File To change the parameter file, begin by extending the shipped generic.prm file. Example of generic.prm file: Example of redhat.conf file configuring a QETH network device (pointed to by CMSCONFFILE in generic.prm ):

Commands:
root="/dev/ram0" ro ip="off" ramdisk_size="40000" cio_ignore="all,!0.0.0009" CMSDASD="191" CMSCONFFILE="redhat.conf" vnc
NETTYPE="qeth" SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602" PORTNAME="FOOBAR" PORTNO="0" LAYER2="1" MACADDR="02:00:be:3a:01:f3" HOSTNAME="foobar.systemz.example.com" IPADDR="192.168.17.115" NETMASK="255.255.255.0" GATEWAY="192.168.17.254" DNS="192.168.17.1" SEARCHDNS="systemz.example.com:example.com" DASD="200-203"
Chapter 4. Updatable Views 4.1. Updatable Views Any view may be marked as updatable. In many circumstances the view definition may allow the view to be inherently updatable without the need to manually define handling of INSERT/UPDATE/DELETE operations. An inherently updatable view cannot be defined with a query that has: A set operation (INTERSECT, EXCEPT, UNION). SELECT DISTINCT Aggregation (aggregate functions, GROUP BY, HAVING) A LIMIT clause A UNION ALL can define an inherently updatable view only if each of the UNION branches is itself inherently updatable. A view defined by a UNION ALL can support inherent INSERTs if it is a partitioned union and the INSERT specifies values that belong to a single partition. Refer to Partitioned Union. Any view column that is not mapped directly to a column is not updatable and cannot be targeted by an UPDATE set clause or be an INSERT column. If a view is defined by a join query or has a WITH clause it may still be inherently updatable. However in these situations there are further restrictions and the resulting query plan may execute multiple statements. For a non-simple query to be updatable, it is required: An INSERT/UPDATE can only modify a single key-preserved table. To allow DELETE operations there must be only a single key-preserved table. If the default handling is not available or you wish to have an alternative implementation of an INSERT/UPDATE/DELETE, then you may use update procedures (see Section 2.10.6, "Update Procedures" ) to define procedures to handle the respective operations.

Commands:
probe::vm.kmem_cache_alloc Name probe::vm.kmem_cache_alloc - Fires when kmem_cache_alloc is requested Synopsis vm.kmem_cache_alloc Values bytes_alloc allocated Bytes ptr pointer to the kmemory allocated name name of the probe point bytes_req requested Bytes gfp_flags type of kmemory to allocate caller_function name of the caller function. gfp_flag_name type of kmemory to allocate(in string format) call_site address of the function calling this kmemory function.

Commands:
Red Hat Ansible Automation Platform operator backup and recovery guide Red Hat Ansible Automation Platform 2.4 Safeguard against data loss with backup and recovery of Ansible Automation Platform operator on OpenShift Container Platform Red Hat Customer Content Services

Commands:
df -h | grep "/var/lib/pgsql/data"
--- apiVersion: automationcontroller.ansible.com/v1beta1 kind: AWXBackup metadata: name: awxbackup-2024-07-15 namespace: my-namespace spec: deployment_name: controller
apiVersion: v1 kind: Secret metadata: name: external-restore-postgres-configuration namespace: <target_namespace> 1 stringData: host: "<external_ip_or_url_resolvable_by_the_cluster>" 2 port: "<external_port>" 3 database: "<desired_database_name>" username: "<username_to_connect_as>" password: "<password_to_connect_with>" 4 sslmode: "prefer" 5 type: "unmanaged" type: Opaque
oc create -f external-postgres-configuration-secret.yml
kind: AutomationControllerRestore apiVersion: automationcontroller.ansible.com/v1beta1 metadata: namespace: my-namespace name: awxrestore-2024-07-15 spec: deployment_name: restored_controller backup_name: awxbackup-2024-07-15 postgres_configuration_secret: 'external-restore-postgres-configuration'
delete automationcontroller <YOUR_DEPLOYMENT_NAME> -n <YOUR_NAMESPACE> delete pvc postgres-13-<YOUR_DEPLOYMENT_NAME>-13-0 -n <YOUR_NAMESPACE>
apply -f restore.yaml
10.2.2. Enabling FIPS Mode for Applications Using NSS The procedure for enabling FIPS mode on Red Hat Enterprise Linux systems described in Section 10.2.1, "Enabling FIPS Mode" does not affect the FIPS state of Network Security Services (NSS), and thus does not affect applications using NSS. When required, the user can switch any NSS application to FIPS mode using the following command: Replace dir with the directory specifying the NSS database used by the application. If more than one NSS application uses this database, all these applications will be switched into FIPS mode. The applications have to be restarted for the NSS FIPS mode to take effect. Provided that the nss-sysinit package is installed, and the application whose NSS database you need to locate opens the /etc/pki/nssdb file, the path to the user NSS database is ~/.pki/nssdb . To enable FIPS mode for the Firefox web browser and the Thunderbird email client, go to Edit Preferences Advanced Certificates Security Devices Enable FIPS .

Commands:
~]# modutil -fips true -dbdir dir
Chapter 15. Removing an ID range after removing a trust to AD If you have removed a trust between your IdM and Active Directory (AD) environments, you might want to remove the ID range associated with it. Warning IDs allocated to ID ranges associated with trusted domains might still be used for ownership of files and directories on systems enrolled into IdM. If you remove the ID range that corresponds to an AD trust that you have removed, you will not be able to resolve the ownership of any files and directories owned by AD users. Prerequisites You have removed a trust to an AD environment. Procedure Display all the ID ranges that are currently in use: Identify the name of the ID range associated with the trust you have removed. The first part of the name of the ID range is the name of the trust, for example AD.EXAMPLE.COM_id_range . Remove the range: Restart the SSSD service to remove references to the ID range you have removed.

Commands:
ipa idrange-find
ipa idrange-del AD.EXAMPLE.COM_id_range
systemctl restart sssd
Chapter 13. Increasing the size of an XFS file system As a system administrator, you can increase the size of an XFS file system to make a complete use of a larger storage capacity. Important It is not currently possible to decrease the size of XFS file systems. 13.1. Increasing the size of an XFS file system with xfs_growfs This procedure describes how to grow an XFS file system using the xfs_growfs utility. Prerequisites Ensure that the underlying block device is of an appropriate size to hold the resized file system later. Use the appropriate resizing methods for the affected block device. Mount the XFS file system. Procedure While the XFS file system is mounted, use the xfs_growfs utility to increase its size: Replace file-system with the mount point of the XFS file system. With the -D option, replace new-size with the desired new size of the file system specified in the number of file system blocks. To find out the block size in kB of a given XFS file system, use the xfs_info utility: Without the -D option, xfs_growfs grows the file system to the maximum size supported by the underlying device. Additional resources xfs_growfs(8) man page on your system.

Commands:
xfs_growfs file-system -D new-size
xfs_info block-device data = bsize=4096
Chapter 1. Key features Streams for Apache Kafka simplifies the process of running Apache Kafka in an OpenShift cluster. This guide is intended as a starting point for building an understanding of Streams for Apache Kafka. The guide introduces some of the key concepts behind Kafka, which is central to Streams for Apache Kafka, explaining briefly the purpose of Kafka components. Configuration points are outlined, including options to secure and monitor Kafka. A distribution of Streams for Apache Kafka provides the files to deploy and manage a Kafka cluster, as well as example files for configuration and monitoring of your deployment . A typical Kafka deployment is described, as well as the tools used to deploy and manage Kafka. 1.1. Kafka capabilities The underlying data stream-processing capabilities and component architecture of Kafka can deliver: Microservices and other applications to share data with extremely high throughput and low latency Message ordering guarantees Message rewind/replay from data storage to reconstruct an application state Message compaction to remove old records when using a key-value log Horizontal scalability in a cluster configuration Replication of data to control fault tolerance Retention of high volumes of data for immediate access 1.2. Kafka use cases Kafka's capabilities make it suitable for: Event-driven architectures Event sourcing to capture changes to the state of an application as a log of events Message brokering Website activity tracking Operational monitoring through metrics Log collection and aggregation Commit logs for distributed systems Stream processing so that applications can respond to data in real time 1.3. How Streams for Apache Kafka supports Kafka Streams for Apache Kafka provides container images and operators for running Kafka on OpenShift. Streams for Apache Kafka operators are purpose-built with specialist operational knowledge to effectively manage Kafka on OpenShift. Operators simplify the process of: Deploying and running Kafka clusters Deploying and running Kafka components Configuring access to Kafka Securing access to Kafka Upgrading Kafka Managing brokers Creating and managing topics Creating and managing users

Commands:
4.364. ypserv 4.364.1. RHBA-2011:1557 - ypserv bug fix and enhancement update An updated ypserv package that fixes two bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6. The ypserv utility provides network information (login names, passwords, home directories, group information) to all of the machines on a network. It can enable users to log in on any machine on the network as long as the machine has the Network Information Service (NIS) client programs running and the user's password is recorded in the NIS passwd database. NIS was formerly known as Sun Yellow Pages (YP). Bug Fixes BZ# 699675 Uninitialized memory could be accessed when running the "yppasswdd" command with the "-x" option to pass data to an external program. As a consequence, redundant characters were prefixed to the request string, which led to incorrect parsing of the request. This update fixes the memory initialization and the request can be now parsed successfully. BZ# 734494 Prior to this update, the root user could see old passwords of other users. This was caused by a change request being logged using syslog when running the "yppaswdd" command with the "-x" option to pass data to an external program. With this update, the old password hash and the new password hash are cleared in syslog and the root user can no longer view the old passwords of other users. Enhancement BZ# 699667 Prior to this update, users were not able to change their passwords by running the "yppasswd" command if using the passwd.adjunct file, which prevents disclosing the encrypted passwords. With this update, users are now able to change their passwords. All users of ypserv are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
6.2. Known Issues Supplying an invalid version number in cluster.conf as a parameter to the cman_tool command will cause the cluster to stop processing information. To work around this issue, ensure that the version number used is valid. Under some circumstances, creating cluster mirrors with the '--nosync' option may cause I/O to become extremely slow. Note that this issue only effects I/O immediately after the creation of the mirror, and only when '--nosync' is used. To work around this issue, run the following command after the creating the mirror. luci will not function with Red Hat Enterprise Linux 5 clusters unless each cluster node has ricci version 0.12.2-14 The sync state of an inactive LVM mirror cannot be determined. Consequently, the primary device of an LVM mirror can only be removed when the mirror is in-sync. If device-mapper-multipath is used, and the default path failure timeout value ( /sys/class/fc_remote_ports/rport-xxx/dev_loss_tmo ) is changed, that the timeout value will revert to the default value after a path fails, and later restored. Note that this issue will present the lpfc, qla2xxx, ibmfc or fnic Fibre Channel drivers. To work around this issue the dev_loss_tmo value must be adjusted after each path fail/restore event. Generally, placing mirror legs on different physical devices improves data availability. The command lvcreate --alloc anywhere does not guarantee placement of data on different physical devices. Consequently, the use of this option is not recommended. If this option is used, the location of the data placement must be manually verified. The GFS2 fsck program, fsck.gfs2, currently assumes that the gfs2 file system is divided into evenly-spaced segments known as resource groups. This is always the case on file systems formatted by mkfs.gfs2. It will also be the case for most file systems created as GFS (gfs1) and converted to gfs2 format with gfs2_convert. However, if a GFS file system was resized (with gfs_grow) while it was in the GFS format, the resource groups might not be evenly spaced. If the resource groups are not evenly spaced, and the resource groups or the resource groups index (rindex) become damaged, fsck.gfs2 might not function correctly. There is currently no workaround for this issue. However, if the resource groups are not damaged, avoid this issue by copying the file system contents to a new device with evenly-spaced resource groups. Format the new device as gfs2 with mkfs.gfs2, and copy the contents from the old device to the new device. The new device will have evenly-spaced resource groups.

Commands:
lvchange --refresh <VG>/<LV>
Preface Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To propose improvements, open a Jira issue and describe your suggested changes. Provide as much detail as possible to enable us to address your request quickly. Prerequisite You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one. Procedure Click the following link: Create issue . In the Summary text box, enter a brief description of the issue. In the Description text box, provide the following information: The URL of the page where you found the issue. A detailed description of the issue. You can leave the information in any other fields at their default values. Click Create to submit the Jira issue to the documentation team. Thank you for taking the time to provide feedback.

Commands:
Chapter 6. Managing Red Hat Cluster With system-config-cluster This chapter describes various administrative tasks for managing a Red Hat Cluster and consists of the following sections: Section 6.1, "Starting and Stopping the Cluster Software" Section 6.2, "Managing High-Availability Services" Section 6.4, "Backing Up and Restoring the Cluster Database" Section 6.5, "Disabling the Cluster Software" Section 6.6, "Diagnosing and Correcting Problems in a Cluster" 6.1. Starting and Stopping the Cluster Software To start the cluster software on a member, type the following commands in this order: service ccsd start service cman start (or service lock_gulmd start for GULM clusters) service fenced start (DLM clusters only) service clvmd start , if CLVM has been used to create clustered volumes service gfs start , if you are using Red Hat GFS service rgmanager start , if the cluster is running high-availability services ( rgmanager ) To stop the cluster software on a member, type the following commands in this order: service rgmanager stop , if the cluster is running high-availability services ( rgmanager ) service gfs stop , if you are using Red Hat GFS service clvmd stop , if CLVM has been used to create clustered volumes service fenced stop (DLM clusters only) service cman stop (or service lock_gulmd stop for GULM clusters) service ccsd stop Stopping the cluster services on a member causes its services to fail over to an active member.

Commands: