mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 13. Self-heal does not complete If a self-heal operation never completes, the cause could be a Gluster File ID (GFID) mismatch. 13.1. Gluster File ID mismatch Diagnosis Check self-heal state. Run the following command several times over a few minutes. Note the entries that are shown. If the same entries are shown each time, these entries may have a GFID mismatch. Check the GFID of each entry on each host. On each host, run the following command for each entry: The <backend_path> for an entry is comprised of the brick path and the entry. For example, if the brick for the engine volume has the path of /gluster_bricks/engine/engine and the entry shown in heal info is 58d392a6-e5b1-4aed-9bbc-952210a7137d/ha_agent/hosted-engine.metadata , the backend_path to use is /gluster_bricks/engine/engine/58d392a6-e5b1-4aed-9bbc-952210a7137d/ha_agent/hosted-engine.metadata . Compare the output from each host. If the trusted.gfid for an entry is not the same on all hosts, there is a GFID mismatch. Solution Resolve the mismatch in favor of the GFID with the most recent modification time: For example: Manually trigger a heal on the volume.

Commands:
gluster volume heal <volname> info
getfattr -d -m. -ehex <backend_path> -h
gluster volume heal <volume> split-brain latest-mtime <entry>
gluster volume heal engine split-brain latest-mtime /58d392a6-e5b1-4aed-9bbc-952210a7137d/ha_agent/hosted-engine.metadata
gluster volume heal <volname>
7.298. boost 7.298.1. RHBA-2013:0692 - boost bug fix update Updated boost packages that fix one bug are now available for Red Hat Enterprise Linux 6. The boost packages provide free peer-reviewed portable C++ source libraries with emphasis on libraries which work well with the C++ Standard Library. Bug Fix BZ# 921441 Users experienced problems when trying to build MongoDB, because the version of boost (1.41), which was installed by default on Red Hat Enterprise Linux 6.4 had codes that violated the compilation rules which the version of GCC (4.4.7) verified. The version of GCC did not check for the error in the boost code, and this caused builds to fail for any projects that included the boost/thread.h header file from boost version 1.41. This update fixes this bug by explicitly spelling out the full destructor definition of the boost::exception_ptr class, and the version is now fully compatible with version 4.4.7. Users of boost are advised to upgrade to these updated packages, which fix this bug.

Commands:
B.8.2. RHBA-2011:0361 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix a bug are now available for Red Hat Enterprise Linux 6. The cluster packages contain the core clustering libraries for Red Hat High Availability as well as utilities to maintain GFS2 file systems for users of Red Hat Resilient Storage. Bug Fix BZ# 643279 Due to an incorrect conversion of directory inodes with the height larger than 1, running the gfs2_convert utility on a file system with extremely large directories may have caused the file system to become corrupted. With this update, the underlying source code has been modified to target this issue, and the gfs2_convert utility now works as expected. All users of Red Hat High Availability and Red Hat Resilient Storage are advised to upgrade to these updated packages, which resolve this issue.

Commands:
Chapter 16. DHCP Servers Dynamic Host Configuration Protocol ( DHCP ) is a network protocol that automatically assigns TCP/IP information to client machines. Each DHCP client connects to the centrally located DHCP server, which returns the network configuration (including the IP address, gateway, and DNS servers) of that client. 16.1. Why Use DHCP? DHCP is useful for automatic configuration of client network interfaces. When configuring the client system, you can choose DHCP instead of specifying an IP address, netmask, gateway, or DNS servers. The client retrieves this information from the DHCP server. DHCP is also useful if you want to change the IP addresses of a large number of systems. Instead of reconfiguring all the systems, you can just edit one configuration file on the server for the new set of IP addresses. If the DNS servers for an organization changes, the changes happen on the DHCP server, not on the DHCP clients. When you restart the network or reboot the clients, the changes go into effect. If an organization has a functional DHCP server correctly connected to a network, laptops and other mobile computer users can move these devices from office to office.

Commands:
5.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: allow_ftpd_use_nfs When enabled, this Boolean allows the ftpd daemon to access NFS volumes. cobbler_use_nfs When enabled, this Boolean allows the cobblerd daemon to access NFS volumes. git_system_use_nfs When enabled, this Boolean allows the Git system daemon to read system shared repositories on NFS volumes. httpd_use_nfs When enabled, this Boolean allows the httpd daemon to access files stored on NFS volumes. qemu_use_nfs When enabled, this Boolean allows Qemu to use NFS volumes. rsync_use_nfs When enabled, this Boolean allows rsync servers to share NFS volumes. samba_share_nfs When enabled, this Boolean allows the smbd daemon to share NFS volumes. When disabled, this Boolean prevents smbd from having full access to NFS shares via Samba. sanlock_use_nfs When enabled, this Boolean allows the sanlock daemon to manage NFS volumes. sge_use_nfs When enabled, this Boolean allows the sge scheduler to access NFS volumes. use_nfs_home_dirs When enabled, this Boolean adds support for NFS home directories. virt_use_nfs When enabled, this Boolean allows confident virtual guests to manage files on NFS volumes. xen_use_nfs When enabled, this Boolean allows Xen to manage files on NFS volumes. git_cgi_use_nfs When enabled, this Boolean allows the Git Common Gateway Interface ( CGI ) to access NFS volumes. tftp_use_nfs When enabled, this Boolean allows The Trivial File Transfer Protocol ( TFTP ) to read from NFS volumes for public file transfer services. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
Chapter 6. Testing your Fujitsu ETERNUS configuration After you configure the Block Storage service to use the new ETERNUS back ends, declare a volume type for each back end. Use volume types to specify which back end to use when you create new volumes. Create a Fibre Channel back end and map it to the respective back end with the following commands: Create an iSCSI back end and map it to the respective back end with the following commands: For more information about volume types, see Chapter 4, Creating the Fujitsu ETERNUS environment file : Create a 1GB iSCSI volume named test_iscsi to verify your configuration: Test the Fibre Channel back end:

Commands:
cinder type-create FJFC cinder type-key FJFC set volume_backend_name=FJFC
cinder type-create FJISCSI cinder type-key FJISCSI volume_backend_name=FJISCSI
cinder create --volume_type FJISCSI --display_name test_iscsi 1
cinder create --volume_type FJFC --display_name test_fc 1
1.3. Query Termination 1.3.1. Canceling Queries When a query is canceled, processing will be stopped in the query engine and in all connectors involved in the query. The semantics of what a connector does in response to a cancellation command is dependent on the connector implementation. For example, JDBC connectors will asynchronously call cancel on the underlying JDBC driver, which may or may not actually support this method. 1.3.2. User Query Timeouts User query timeouts in Data Virtualization can be managed on the client-side or server-side. Timeouts are only relevant for the first record returned. If the first record has not been received by the client within the specified timeout period, a "cancel" command is issued to the server for the request and no results are returned to the client. The cancel command is issued asynchronously by the JDBC API without the client's intervention. The JDBC API uses the query timeout set by the java.sql.Statement.setQueryTimeout method. You can also set a default statement timeout via the connection property QUERYTIMEOUT . ODBC clients may also use QUERYTIMEOUT as an execution property via a set statement to control the default timeout setting. See Red Hat JBoss Development Guide: Client Development for more on connection/execution properties and set statements. Server-side timeouts start when the query is received by the engine. The timeout will be canceled if the first result is sent back before the timeout has ended. See Section 6.2, "VDB Definition: The VDB Element" for more on setting the query-timeout VDB property. See the Red Hat JBoss Administration Guide for more information on setting the default query timeout for all queries.

Commands:
17.3. Trouble During the Installation 17.3.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 , there is probably a SCSI controller that is not being recognized by the installation program. Check your hardware vendor's website to determine if a driver disk image is available that fixes your problem. For more general information on driver disks, refer to Chapter 13, Updating Drivers During Installation on IBM Power Systems Servers . You can also refer to the Red Hat Hardware Compatibility List , available online at: https://hardware.redhat.com/

Commands:
10.5. JSON Representation of a Cluster Example 10.2. A JSON representation of a cluster

Commands:
{ "cluster" : [ { "cpu" : { "architecture" : "X86_64", "id" : "Intel Penryn Family" }, "data_center" : { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255", "id" : "00000002-0002-0002-0002-000000000255" }, "memory_policy" : { "overcommit" : { "percent" : "100" }, "transparent_hugepages" : { "enabled" : "true" } }, "scheduling_policy" : { "policy" : "none", "name" : "none", "href" : "/ovirt-engine/api/schedulingpolicies/b4ed2332-a7ac-4d5f-9596-99a439cb2812", "id" : "b4ed2332-a7ac-4d5f-9596-99a439cb2812" }, "version" : { "major" : "4", "minor" : "0" }, "error_handling" : { "on_error" : "migrate" }, "virt_service" : "true", "gluster_service" : "false", "threads_as_cores" : "false", "tunnel_migration" : "false", "trusted_service" : "false", "ha_reservation" : "false", "optional_reason" : "false", "ballooning_enabled" : "false", "ksm" : { "enabled" : "true" }, "required_rng_sources" : { }, "name" : "Default", "description" : "The default server cluster", "href" : "/ovirt-engine/api/clusters/00000001-0001-0001-0001-0000000002fb", "id" : "00000001-0001-0001-0001-0000000002fb", "link" : [ { "href" : "/ovirt-engine/api/clusters/00000001-0001-0001-0001-0000000002fb/networks", "rel" : "networks" }, { "href" : "/ovirt-engine/api/clusters/00000001-0001-0001-0001-0000000002fb/permissions", "rel" : "permissions" }, { "href" : "/ovirt-engine/api/clusters/00000001-0001-0001-0001-0000000002fb/glustervolumes", "rel" : "glustervolumes" }, { "href" : "/ovirt-engine/api/clusters/00000001-0001-0001-0001-0000000002fb/glusterhooks", "rel" : "glusterhooks" }, { "href" : "/ovirt-engine/api/clusters/00000001-0001-0001-0001-0000000002fb/affinitygroups", "rel" : "affinitygroups" }, { "href" : "/ovirt-engine/api/clusters/00000001-0001-0001-0001-0000000002fb/cpuprofiles", "rel" : "cpuprofiles" } ] } ] }
Opening a support case at Red Hat Support Create a support case from Red Hat Insights at Red Hat Support by performing the following steps: Prerequisites You are logged in to the Red Hat Customer Portal. Procedure Access the Red Hat Hybrid Cloud Console : Click Help ? and select Open a support case . You are redirected to the Customer support page. From the Get Support page, select the type of issue that you want to report and click Continue . From the Summarize page, perform the following steps: On the Summary field, describe the issue. Note If Red Hat Insights is not auto-selected, you must manually select the product. From the Product dropdown menu, select Red Hat Insights . From the Version dropdown menu, select the component you have issues with. From the Review page, click Submit . A support case is created.

Commands:
Chapter 88. versions This chapter describes the commands under the versions command. 88.1. versions show Show available versions of services Usage: Table 88.1. Command arguments Value Summary -h, --help Show this help message and exit --all-interfaces Show values for all interfaces --interface <interface> Show versions for a specific interface. --region-name <region_name> Show versions for a specific region. --service <service> Show versions for a specific service. the argument should be either an exact match to what is in the catalog or a known official value or alias from service-types-authority ( https://service- types.openstack.org/) --status <status> Show versions for a specific status. valid values are: - SUPPORTED - CURRENT - DEPRECATED - EXPERIMENTAL Table 88.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated --sort-ascending Sort the column(s) in ascending order --sort-descending Sort the column(s) in descending order Table 88.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 88.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 88.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack versions show [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--sort-ascending | --sort-descending] [--all-interfaces | --interface <interface>] [--region-name <region_name>] [--service <service>] [--status <status>]
Installing Red Hat Trusted Application Pipeline Red Hat Trusted Application Pipeline 1.4 Learn how to install Red Hat Trusted Application Pipeline in your cluster. Red Hat Customer Content Services

Commands:
podman login registry.redhat.io
podman pull registry.redhat.io/rhtap-cli/rhtap-cli-rhel9:latest
podman run -it --entrypoint=bash --publish 8228:8228 --rm rhtap-cli:latest
bash-5.1USD oc login https://api.<input omitted>.openshiftapps.com:443 --username cluster-admin --password <input omitted>
bash-5.1USD rhtap-cli integration github-app --create --token="USDGH_TOKEN" --org="USDGH_ORG_NAME" USDGH_APP_NAME
bash-5.1USD rhtap-cli integration acs --endpoint="USDACS_ENDPOINT" --token="USDACS_TOKEN"
bash-5.1USD rhtap-cli integration quay --dockerconfigjson='USDQUAY_DOCKERCONFIGJSON' --token="USDQUAY_TOKEN" --url="USDQUAY_URL"
bash-5.1USD rhtap-cli integration bitbucket --username="USDBB_USERNAME" --app-password="USDBB_TOKEN" --host="USDBB_URL"
bash-5.1USD rhtap-cli integration gitlab --token="USDGL_API_TOKEN" --host="USDGL_URL"
bash-5.1USD rhtap-cli integration jenkins --token="USDJK_API_TOKEN" --url="USDJK_URL" --username="USDJK_USERNAME"
bash-5.1USD rhtap-cli integration artifactory --url="USDAF_URL" --dockerconfigjson='USDAF_DOCKERCONFIGJSON' --token="USDAF_API_TOKEN"
bash-5.1USD cp config.yaml my-config.yaml
bash-5.1USD vi my-config.yaml
redHatDeveloperHub: enabled: &rhdhEnabled true namespace: *installerNamespace properties: catalogURL: https://github.com/<your username>/tssc-sample-templates/blob/release/all.yaml
redHatAdvancedClusterSecurity: enabled: &rhacsEnabled false namespace: rhtap-acs
bash-5.1USD rhtap-cli deploy --config=USDCONFIG
2.7. Setting Parameters Set subsystem parameters by running the cgset command from a user account with permission to modify the relevant cgroup. For example, if cpuset is mounted to /cgroup/cpu_and_mem/ and the /cgroup/cpu_and_mem/group1 subdirectory exists, specify the CPUs to which this group has access with the following command: The syntax for cgset is: where: parameter is the parameter to be set, which corresponds to the file in the directory of the given cgroup. value is the value for the parameter. path_to_cgroup is the path to the cgroup relative to the root of the hierarchy . For example, to set the parameter of the root group (if the cpuacct subsystem is mounted to /cgroup/cpu_and_mem/ ), change to the /cgroup/cpu_and_mem/ directory, and run: Alternatively, because . is relative to the root group (that is, the root group itself) you could also run: Note, however, that / is the preferred syntax. Note Only a small number of parameters can be set for the root group (such as the cpuacct.usage parameter shown in the examples above). This is because a root group owns all of the existing resources, therefore, it would make no sense to limit all existing processes by defining certain parameters, for example the cpuset.cpu parameter. To set the parameter of group1 , which is a subgroup of the root group, run: A trailing slash after the name of the group (for example, cpuacct.usage=0 group1/ ) is optional. The values that you can set with cgset might depend on values set higher in a particular hierarchy. For example, if group1 is limited to use only CPU 0 on a system, you cannot set group1/subgroup1 to use CPUs 0 and 1, or to use only CPU 1. You can also use cgset to copy the parameters of one cgroup into another existing cgroup. For example: The syntax to copy parameters with cgset is: where: path_to_source_cgroup is the path to the cgroup whose parameters are to be copied, relative to the root group of the hierarchy. path_to_target_cgroup is the path to the destination cgroup, relative to the root group of the hierarchy. Ensure that any mandatory parameters for the various subsystems are set before you copy parameters from one group to another, or the command will fail. For more information on mandatory parameters, refer to Important . Alternative method To set parameters in a cgroup directly, insert values into the relevant subsystem pseudofile using the echo command. In the following example, the echo command inserts the value of 0-1 into the cpuset.cpus pseudofile of the cgroup group1 : With this value in place, the tasks in this cgroup are restricted to CPUs 0 and 1 on the system.

Commands:
cpu_and_mem]# cgset -r cpuset.cpus=0-1 group1
cgset -r parameter = value path_to_cgroup
cpu_and_mem]# cgset -r cpuacct.usage=0 /
cpu_and_mem]# cgset -r cpuacct.usage=0 .
cpu_and_mem]# cgset -r cpuacct.usage=0 group1
cpu_and_mem]# cgset --copy-from group1/ group2/
cgset --copy-from path_to_source_cgroup path_to_target_cgroup
~]# echo 0-1 > /cgroup/cpu_and_mem/group1/cpuset.cpus
7.204. qt 7.204.1. RHBA-2012:1246 - qt bug fix update Updated qt packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The qt packages contain a software toolkit that simplifies the task of writing and maintaining GUI (Graphical User Interface) applications for the X Window System. Bug Fixes BZ# 678604 Prior to this update, the mouse pointer could, under certain circumstances, disappear when using the IRC client Konversation. This update modifies the underlying codes to reset the cursor on the parent and set the cursor on the new window handle. Now, the mouse pointer no longer disappears. BZ#847866 Prior to this update, the high precision coordinates of the QTabletEvent class failed to handle multiple Wacom devices. As a consequence, only the device that was loaded first worked correctly. This update modifies the underlying code so that multiple Wacom devices are handled as expected. All users of qt are advised to upgrade to these updated packages, which fix this bugs.

Commands:
23.6. Memory Backing Memory backing allows the hypervisor to properly manage large pages within the guest virtual machine. <domain> ... <memoryBacking> <hugepages> <page size="1" unit="G" nodeset="0-3,5"/> <page size="2" unit="M" nodeset="4"/> </hugepages> <nosharepages/> <locked/> </memoryBacking> ... </domain> Figure 23.8. Memory backing For detailed information on memoryBacking elements, see the libvirt upstream documentation .

Commands:
<domain> <memoryBacking> <hugepages> <page size="1" unit="G" nodeset="0-3,5"/> <page size="2" unit="M" nodeset="4"/> </hugepages> <nosharepages/> <locked/> </memoryBacking> </domain>
10.5.9.4. MinSpareServers and MaxSpareServers These values are only used with the prefork MPM. They adjust how the Apache HTTP Server dynamically adapts to the perceived load by maintaining an appropriate number of spare server processes based on the number of incoming requests. The server checks the number of servers waiting for a request and kills some if there are more than MaxSpareServers or creates some if the number of servers is less than MinSpareServers . The default MinSpareServers value is 5 ; the default MaxSpareServers value is 20 . These default settings should be appropriate for most situations. Be careful not to increase the MinSpareServers to a large number as doing so creates a heavy processing load on the server even when traffic is light.

Commands:
3.4. Resource Constraints You can determine the behavior of a resource in a cluster by configuring constraints . You can configure the following categories of constraints: location constraints - A location constraint determines which nodes a resource can run on. order constraints - An order constraint determines the order in which the resources run. colocation constraints - A colocation constraint determines where resources will be placed relative to other resources. As a shorthand for configuring a set of constraints that will locate a set of resources together and ensure that the resources start sequentially and stop in reverse order, Pacemaker supports the concept of resource groups.

Commands:
Preface Insights image builder provides the controls and information to keep your systems secure, available and operating efficiently. Update all your systems with secure, over the air updates. Organize your systems in groups that match your business and send updates that match your workflows. Use Red Hat Insights to find and fix potential vulnerabilities in your edge systems with one click. With the Insights image builder application, you can create an image and manage the packages associated with an image. You can build an image, download it, install it on a system, and then register that system so it can receive updates. Provisioning and registration involve the following high-level tasks: Build a Red Hat Enterprise Linux for Edge image using the Insights image builder application. Download the image and modify it with your organization credentials, using Podman and the fleet management ISO utility. Deploy the image to systems. View systems in the edge management and Red Hat Insights applications, in the Red Hat Hybrid Cloud Console.

Commands: