mtpti5iD/redhat-docs_dataset huggingface dataset:
18.3. Graphical User Interface with X11 or VNC To run anaconda with the graphical user interface, use a workstation that has either an X Window System (X11) server or VNC client installed. You can use X11 forwarding with an SSH client or X11 directly. If the installer on your workstation fails because the X11 server does not support required X11 extensions you might have to upgrade the X11 server or use VNC. To use VNC, disable X11 forwarding in your SSH client prior to connecting to the Linux installation system on the mainframe or specify the vnc parameter in your parameter file. Using VNC is recommended for slow or long-distance network connections. Refer to Section 28.2, "Enabling Remote Access to the Installation System" . Table 18.1, "Parameters and SSH login types" shows how the parameters and SSH login type controls which anaconda user interface is used. Table 18.1. Parameters and SSH login types Parameter SSH login User interface none SSH without X11 forwarding VNC or text vnc SSH with or without X11 forwarding VNC none SSH with X11 forwarding X11 display= IP/hostname : display SSH without X11 forwarding X11 18.3.1. Installation using X11 forwarding You can connect a workstation to the Linux installation system on the mainframe and display the graphical installation program using SSH with X11 forwarding. You require an SSH client that allows X11 forwarding. To open the connection, first start the X server on the workstation. Then connect to the Linux installation system. You can enable X11 forwarding in your SSH client when you connect. For example, with OpenSSH enter the following in a terminal window on your workstation: Replace linuxvm.example.com with the hostname or IP address of the system you are installing. The -X option (the capital letter X ) enables X11 forwarding.

Commands:
ssh -X install@linuxvm.example.com
Chapter 7. Technology previews This part provides a list of all Technology Previews available in Red Hat Satellite 6.16. For information on Red Hat scope of support for Technology Preview features, see Technology Preview Features Support Scope . 7.1. Web UI All Hosts page The new All Hosts page has the following features: Bulk actions: You can now select one or more hosts and use the options menu to perform actions such as such as Build management, Change host group, Delete, Manage content, Packages (install/remove/upgrade), Errata, Content source, and Content view environments to change the content view and lifecycle environment of hosts. Single-host actions: You can perform actions on a single host by using the options menu to Edit, Clone, Delete, and Change content view environments. To use the new page by default, navigate to Administer > Settings and set Show new host overview page to Yes . The legacy and the new All Hosts pages are linked so that you can switch between them. Jira:SAT-20041 [1] Job details page The Job details page is redesigned for enhanced user experience. By default, the web UI displays the design. To view the new design, navigate to Monitor > Jobs , click a job name in the Description column and then click New UI . Note that the Show Experimental Labs setting must be enabled under Administer > Settings . Jira:SAT-18427 [1] 7.2. Host provisioning and management OpenShift Virtualization plugin You can provision virtual machines by using the OpenShift Virtualization plugin. Jira:SAT-18663 [1] Kernel execution template You can use the kernel execution (kexec) provisioning template for PXE-less boot methods. Jira:SAT-21012 [1]

Commands:
Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To provide feedback, open a Jira issue that describes your concerns. Provide as much detail as possible so that your request can be addressed quickly. Prerequisites 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 To provide your feedback, perform the following steps: Click the following link: Create Issue . In the Summary text box, enter a brief description of the issue. In the Description text box, provide more details about the issue. Include the URL where you found the issue. Provide information for any other required fields. Allow all fields that contain default information to remain at the defaults. Click Create to create the Jira issue for the documentation team. A documentation issue will be created and routed to the appropriate documentation team. Thank you for taking the time to provide feedback.

Commands:
Part IV. Creating custom pages in Business Central As a business analyst or business rules developer, you can use the Page Editor in Business Central to create static pages and dynamic dashboards to display specific information about your project. A dashboard is a collection of pages that contain at least one dynamic reporting component. You can define a data set to feed the reporting components of a dashboard. You can export dashboards to the standalone Dashbuilder Runtime dashboard viewer on Red Hat JBoss EAP or the Dashbuilder Standalone dashboard viewer on Red Hat OpenShift Container Platform. Prerequisites You are logged in to Business Central as a user with permission to edit pages.

Commands:
5.117. irssi 5.117.1. RHBA-2012:1171 - irssi bug fix update Updated irssi packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Irssi is a modular IRC client with Perl scripting. Only the text-mode front end is currently supported. Bug Fixes BZ# 639258 Prior to this update, when the user attempted to use the "/unload" command to unload a static module, Irssi incorrectly marked this module as unavailable, rendering the user unable to load this module again without restarting the client. This update adapts the underlying source code to ensure that only dynamic modules can be unloaded. BZ# 845047 The version of the irssi(1) manual page documented "--usage" as a valid command line option. This was incorrect, because Irssi no longer supports this option and an attempt to use it causes it to fail with an error. With this update, the manual page has been corrected and no longer documents unsupported command line options. All users of irssi are advised to upgrade to these updated packages, which fix these bugs.

Commands:
A.6. perf The perf tool provides a number of useful commands, some of which are listed in this section. For detailed information about perf , see the Red Hat Enterprise Linux 7 Developer Guide , or refer to the man pages. perf stat This command provides overall statistics for common performance events, including instructions executed and clock cycles consumed. You can use the option flags to gather statistics on events other than the default measurement events. As of Red Hat Enterprise Linux 6.4, it is possible to use perf stat to filter monitoring based on one or more specified control groups (cgroups). For further information, read the man page: perf record This command records performance data into a file which can be later analyzed using perf report . For further details, read the man page: perf report This command reads the performance data from a file and analyzes the recorded data. For further details, read the man page: perf list This command lists the events available on a particular machine. These events vary based on the performance monitoring hardware and the software configuration of the system. For further information, read the man page: perf top This command performs a similar function to the top tool. It generates and displays a performance counter profile in realtime. For further information, read the man page: perf trace This command performs a similar function to the strace tool. It monitors the system calls used by a specified thread or process and all signals received by that application. Additional trace targets are available; refer to the man page for a full list:

Commands:
man perf-stat
man perf-record
man perf-report
man perf-list
man perf-top
man perf-trace
Chapter 4. Viewing the Ceph overview with Datadog After installing and configuring the Datadog integration with Ceph, return to the Datadog App . The user interface will present navigation on the left side of the screen. Prerequisites Internet access. Procedure Hover over Dashboards to expose the submenu and then click Ceph Overview . Datadog presents an overview of the Ceph Storage Cluster. Click Dashboards->New Dashboard to create a custom Ceph dashboard.

Commands:
Chapter 7. Setting up CDS nodes To provide repositories that clients can connect to and access the updated packages, you must first set up the CDS nodes. The following process explains how to: Register the CDS node Enable the required repositories on the CDS node Important The following procedures assume that your CCSP account uses Simple Content Access (SCA). If that is not the case, refer to Appendix A, Using Entitlement Mode instead. 7.1. Registering the CDS node The following instructions explain how to register your Content Delivery Server (CDS) nodes. Note On the CDS nodes you do not need to use the --type=rhui flag that was required on the RHUA node. Prerequisites Latest version of RHEL 8 is installed. Ensure you have root access to each of the CDS nodes. Procedure On the CDS nodes, enter the following command: Type your CCSP user name and password when prompted. Optional: If your system is already registered, you can override the subscription using the --force option. The new system will be available on the Red Hat Customer Portal, and the new CDS instance will not have any subscriptions attached to it. Verification Navigate to the Red Hat Hybrid Cloud Console . Verify that your system is available by locating it within the inventory. 7.2. Enabling the required repositories on the CDS node To install RHUI on your system, you must first enable certain repositories on your nodes which contain the required packages. If you are planning to use Ceph File System (CephFS) as your shared storage, then you must also enable the rhceph-5-tools-for-rhel-8-x86_64-rpms repository. Note CDS nodes require RHEL installations with base packages and with all repositories disabled except for the rhel-8-for-x86_64-baseos-rpms , rhel-8-for-x86_64-appstream-rpms , and, optionally, rhceph-5-tools-for-rhel-8-x86_64-rpms repositories. This requirement means that you cannot install any third-party configurations or softwares that are not necessary for the direct operation of the server. This restriction includes hardening or other non-Red Hat security software. Prerequisites Ensure that you have root access to all the CDS nodes you plan to use. Procedure The necessary repositories are automatically enabled on all your CDS nodes. Optional: If you are planning to use CephFS, enable the Ceph tools repository on all your CDS nodes. Verification List the enabled repositories and verify whether the relevant repositories appear on the list.

Commands:
subscription-manager register
subscription-manager register --force
subscription-manager repos --enable rhceph-5-tools-for-rhel-8-x86_64-rpms
yum repolist enabled Updating Subscription Management repositories. repo id repo name rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs)
Chapter 13. catalog This chapter describes the commands under the catalog command. 13.1. catalog list List services in the service catalog Usage: Table 13.1. Command arguments Value Summary -h, --help Show this help message and exit Table 13.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 --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 Table 13.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 13.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 13.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. 13.2. catalog show Display service catalog details Usage: Table 13.6. Positional arguments Value Summary <service> Service to display (type or name) Table 13.7. Command arguments Value Summary -h, --help Show this help message and exit Table 13.8. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 13.9. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 13.10. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 13.11. 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 catalog list [-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]
openstack catalog show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] <service>
Chapter 23. Upgrading a director-deployed Ceph Storage cluster to Red Hat Ceph Storage 4 If your deployment uses a Red Hat Ceph Storage cluster that was deployed using director, you must complete the procedures included in this section. Important When you upgrade a Red Hat Ceph Storage cluster from a supported version to version 4.2z2, the upgrade completes with the storage cluster in a HEALTH_WARN state with a warning message that states monitors are allowing insecure global_id reclaim . This is due to the patched CVE (CVE-2021-20288), see Ceph HEALTH_WARN with 'mons are allowing insecure global_id reclaim' after install/upgrade to RHCS 4.2z2 (or newer) . Because the HEALTH_WARN state is displayed due to the CVE, it is possible to mute health warnings temporarily. However, there is a risk that if you mute warnings you do not have visibility about potential older and unpatched clients connected to your cluster. For more information about muting health warnings, see Upgrading a Red Hat Ceph Storage cluster in the Red Hat Ceph Storage documentation. Note If you are upgrading with external Ceph deployments, you must skip the procedures included in this section and continue to the section. After you upgrade the overcloud, upgrade your director-deployed Ceph Storage cluster to Red Hat Ceph Storage cluster to version 4. 23.1. Installing ceph-ansible If your deployment uses a Red Hat Ceph Storage cluster that was deployed using director, you must complete this procedure. The ceph-ansible package is required when you use Ceph Storage with Red Hat OpenStack Platform. Procedure Enable the Ceph Tools repository: Install the ceph-ansible package: 23.2. Upgrading to Ceph Storage 4 Upgrade the Ceph Storage nodes from version 3 to version 4. Note If you are not using the default stack name ( overcloud ), set your stack name with the --stack STACK NAME option replacing STACK NAME with the name of your stack. Procedure Source the stackrc file: Run the Ceph Storage external upgrade process with the ceph tag: Wait until the Ceph Storage upgrade completes.

Commands:
[stack@director ~]USD sudo subscription-manager repos --enable=rhceph-4-tools-for-rhel-8-x86_64-rpms
[stack@director ~]USD sudo dnf install -y ceph-ansible
source ~/stackrc
openstack overcloud external-upgrade run --stack STACK NAME --tags ceph
Providing feedback on Red Hat JBoss Core Services documentation To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account. Procedure Click the following link to create a ticket . Enter a brief description of the issue in the Summary . Provide a detailed description of the issue or enhancement in the Description . Include a URL to where the issue occurs in the documentation. Clicking Submit creates and routes the issue to the appropriate documentation team.

Commands:
probe::socket.readv.return Name probe::socket.readv.return - Conclusion of receiving a message via sock_readv Synopsis socket.readv.return Values name Name of this probe protocol Protocol value family Protocol family value success Was receive successful? (1 = yes, 0 = no) state Socket state value flags Socket flags value size Size of message received (in bytes) or error code if success = 0 type Socket type value Context The message receiver. Description Fires at the conclusion of receiving a message on a socket via the sock_readv function

Commands:
Chapter 12. Upgrading For version upgrades, the Red Hat build of OpenTelemetry Operator uses the Operator Lifecycle Manager (OLM), which controls installation, upgrade, and role-based access control (RBAC) of Operators in a cluster. The OLM runs in the OpenShift Container Platform by default. The OLM queries for available Operators as well as upgrades for installed Operators. When the Red Hat build of OpenTelemetry Operator is upgraded to the new version, it scans for running OpenTelemetry Collector instances that it manages and upgrades them to the version corresponding to the Operator's new version. 12.1. Additional resources Operator Lifecycle Manager concepts and resources Updating installed Operators

Commands:
Chapter 2. Acknowledgments Red Hat Ceph Storage 5 project is seeing amazing growth in the quality and quantity of contributions from individuals and organizations in the Ceph community. We would like to thank all members of the Red Hat Ceph Storage team, all of the individual contributors in the Ceph community, and additionally, but not limited to, the contributions from organizations such as: Intel(R) Fujitsu (R) UnitedStack Yahoo TM Ubuntu Kylin Mellanox (R) CERN TM Deutsche Telekom Mirantis (R) SanDisk TM SUSE

Commands:
7.55. fprintd 7.55.1. RHBA-2015:0663 - fprintd bug fix update Updated fprintd packages that fix one bug are now available for Red Hat Enterprise Linux 6. The fprintd packages contain a D-Bus service to access fingerprint readers. Bug Fix BZ# 1024825 Due to a bug in the fprintd daemon code, long-running Pluggable Authentication Module (PAM) clients were experiencing file descriptor leaks for each iteration of authentication. With this update, the file descriptor closes after completing its job, and therefore the file descriptor leaks no longer occur. Users of fprintd are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 3. Configuring Red Hat Cluster With Conga This chapter describes how to configure Red Hat Cluster software using Conga , and consists of the following sections: Section 3.1, "Configuration Tasks" Section 3.2, "Starting luci and ricci " . Section 3.3, "Creating A Cluster" Section 3.4, "Global Cluster Properties" Section 3.5, "Configuring Fence Devices" Section 3.6, "Configuring Cluster Members" Section 3.7, "Configuring a Failover Domain" Section 3.8, "Adding Cluster Resources" Section 3.9, "Adding a Cluster Service to the Cluster" Section 3.10, "Configuring Cluster Storage" 3.1. Configuration Tasks Configuring Red Hat Cluster software with Conga consists of the following steps: Configuring and running the Conga configuration user interface - the luci server. Refer to Section 3.2, "Starting luci and ricci " . Creating a cluster. Refer to Section 3.3, "Creating A Cluster" . Configuring global cluster properties. Refer to Section 3.4, "Global Cluster Properties" . Configuring fence devices. Refer to Section 3.5, "Configuring Fence Devices" . Configuring cluster members. Refer to Section 3.6, "Configuring Cluster Members" . Creating failover domains. Refer to Section 3.7, "Configuring a Failover Domain" . Creating resources. Refer to Section 3.8, "Adding Cluster Resources" . Creating cluster services. Refer to Section 3.9, "Adding a Cluster Service to the Cluster" . Configuring storage. Refer to Section 3.10, "Configuring Cluster Storage" .

Commands:
7.4. Starting the audit Service Once auditd is configured, start the service to collect Audit information and store it in the log files. Use the following command as the root user to start auditd : Note The service command is the only way to correctly interact with the auditd daemon. You need to use the service command so that the auid value is properly recorded. You can use the systemctl command only for two actions: enable and status . To configure auditd to start at boot time: A number of other actions can be performed on auditd using the service auditd action command, where action can be one of the following: stop Stops auditd . restart Restarts auditd . reload or force-reload Reloads the configuration of auditd from the /etc/audit/auditd.conf file. rotate Rotates the log files in the /var/log/audit/ directory. resume Resumes logging of Audit events after it has been previously suspended, for example, when there is not enough free space on the disk partition that holds the Audit log files. condrestart or try-restart Restarts auditd only if it is already running. status Displays the running status of auditd .

Commands:
~]# service auditd start
~]# systemctl enable auditd
A.6. Troubleshooting DNS Many DNS problems are caused by misconfiguration. Therefore, make sure you meet the conditions in Section 2.1.5, "Host Name and DNS Configuration" . Use the dig utility to check the response from the DNS server: Use the host utility to perform a DNS name lookup: Review the DNS records in LDAP using the ipa dnszone-show command: For details on using the IdM tools to manage DNS, see Chapter 33, Managing DNS . Restart BIND to force resynchronization with LDAP: Get a list of the required DNS records: Use the dig utility to check if the displayed records are present in DNS. If you use the Identity Management DNS, use the ipa dns-update-system-records command to update any missing records.

Commands:
dig _ldap._tcp.ipa.example.com. SRV ; <<>> DiG 9.9.4-RedHat-9.9.4-48.el7 <<>> _ldap._tcp.ipa.example.com. SRV ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17851 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 5 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;_ldap._tcp.ipa.example.com. IN SRV ;; ANSWER SECTION: _ldap._tcp.ipa.example.com. 86400 IN SRV 0 100 389 ipaserver.ipa.example.com. ;; AUTHORITY SECTION: ipa.example.com. 86400 IN NS ipaserver.ipa.example.com. ;; ADDITIONAL SECTION: ipaserver.ipa.example.com. 86400 IN A 192.0.21 ipaserver.ipa.example.com 86400 IN AAAA 2001:db8::1
host server.ipa.example.com server.ipa.example.com. 86400 IN A 192.0.21 server.ipa.example.com 86400 IN AAAA 2001:db8::1
ipa dnszone-show zone_name USD ipa dnsrecord-show zone_name record_name_in_the_zone
systemctl restart named-pkcs11
ipa dns-update-system-records --dry-run