mtpti5iD/redhat-docs_dataset huggingface dataset:
25.21. Troubleshooting Online Storage Configuration This section provides solution to common problems users experience during online storage reconfiguration. Logical unit removal status is not reflected on the host. When a logical unit is deleted on a configured filer, the change is not reflected on the host. In such cases, lvm commands will hang indefinitely when dm-multipath is used, as the logical unit has now become stale . To work around this, perform the following procedure: Procedure 25.17. Working Around Stale Logical Units Determine which mpath link entries in /etc/lvm/cache/.cache are specific to the stale logical unit. To do this, run the following command: Example 25.16. Determine Specific mpath Link Entries For example, if stale-logical-unit is 3600d0230003414f30000203a7bc41a00, the following results may appear: This means that 3600d0230003414f30000203a7bc41a00 is mapped to two mpath links: dm-4 and dm-5 . , open /etc/lvm/cache/.cache . Delete all lines containing stale-logical-unit and the mpath links that stale-logical-unit maps to. Example 25.17. Delete Relevant Lines Using the same example in the step, the lines you need to delete are:

Commands:
ls -l /dev/mpath | grep stale-logical-unit
lrwxrwxrwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00 -> ../dm-4 lrwxrwxrwx 1 root root 7 Aug 2 10:33 /3600d0230003414f30000203a7bc41a00p1 -> ../dm-5
/dev/dm-4 /dev/dm-5 /dev/mapper/3600d0230003414f30000203a7bc41a00 /dev/mapper/3600d0230003414f30000203a7bc41a00p1 /dev/mpath/3600d0230003414f30000203a7bc41a00 /dev/mpath/3600d0230003414f30000203a7bc41a00p1
6.5. Disabling the Cluster Software It may become necessary to temporarily disable the cluster software on a cluster member. For example, if a cluster member experiences a hardware failure, you may want to reboot that member, but prevent it from rejoining the cluster to perform maintenance on the system. Use the /sbin/chkconfig command to stop the member from joining the cluster at boot-up as follows: Once the problems with the disabled cluster member have been resolved, use the following commands to allow the member to rejoin the cluster: You can then reboot the member for the changes to take effect or run the following commands in the order shown to restart cluster software: 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 )

Commands:
chkconfig --level 2345 rgmanager off chkconfig --level 2345 gfs off chkconfig --level 2345 clvmd off chkconfig --level 2345 fenced off chkconfig --level 2345 lock_gulmd off chkconfig --level 2345 cman off chkconfig --level 2345 ccsd off
chkconfig --level 2345 rgmanager on chkconfig --level 2345 gfs on chkconfig --level 2345 clvmd on chkconfig --level 2345 fenced on chkconfig --level 2345 lock_gulmd on chkconfig --level 2345 cman on chkconfig --level 2345 ccsd on
Chapter 2. Overview .NET is a general purpose, modular, cross-platform, and open source implementation of .NET that features automatic memory management and modern programming languages. It allows users to build high-quality applications efficiently. .NET 9.0 is available on RHEL 8.10, RHEL 9.5, and later. .NET 9.0 is a Short Term Support (STS) release. STS releases releases reach End of Support after around 1.5 years. For more information, see the Life Cycle and Support Policies for the .NET Program . .NET offers: The ability to follow a microservices-based approach, where some components are built with .NET and others with Java or JavaScript, but all can run on a common, supported platform in RHEL. The capacity to more easily develop new .NET workloads on Microsoft Windows. You can deploy and run on either RHEL or Windows Server. A heterogeneous data center, where the underlying infrastructure is capable of running .NET applications without having to rely solely on Windows Server.

Commands:
7.319. openswan 7.319.1. RHSA-2013:0827 - Important: openswan security update Updated openswan packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link associated with the description below. Openswan is a free implementation of Internet Protocol Security (IPsec) and Internet Key Exchange (IKE). IPsec uses strong cryptography to provide both authentication and encryption services. These services allow you to build secure tunnels through untrusted networks. When using Opportunistic Encryption, Openswan's pluto IKE daemon requests DNS TXT records to obtain public RSA keys of itself and its peers. Security Fix CVE-2013-2053 A buffer overflow flaw was found in Openswan. If Opportunistic Encryption were enabled ("oe=yes" in "/etc/ipsec.conf") and an RSA key configured, an attacker able to cause a system to perform a DNS lookup for an attacker-controlled domain containing malicious records (such as by sending an email that triggers a DKIM or SPF DNS record lookup) could cause Openswan's pluto IKE daemon to crash or, potentially, execute arbitrary code with root privileges. With "oe=yes" but no RSA key configured, the issue can only be triggered by attackers on the local network who can control the reverse DNS entry of the target system. Opportunistic Encryption is disabled by default. This issue was discovered by Florian Weimer of the Red Hat Product Security Team. All users of openswan are advised to upgrade to these updated packages, which contain backported patches to correct this issue. After installing this update, the ipsec service will be restarted automatically.

Commands:
Chapter 9. Logging 9.1. Configuring logging The client uses the SLF4J API, enabling users to select a particular logging implementation based on their needs. For example, users can provide the slf4j-log4j binding to select the Log4J implementation. More details on SLF4J are available from its website . The client uses Logger names residing within the org.apache.qpid.jms hierarchy, which you can use to configure a logging implementation based on your needs. 9.2. Enabling protocol logging When debugging, it is sometimes useful to enable additional protocol trace logging from the Qpid Proton AMQP 1.0 library. There are two ways to achieve this. Set the environment variable (not the Java system property) PN_TRACE_FRM to 1 . When the variable is set to 1 , Proton emits frame logging to the console. Add the option amqp.traceFrames=true to your connection URI and configure the org.apache.qpid.jms.provider.amqp.FRAMES logger to log level TRACE . This adds a protocol tracer to Proton and includes the output in your logs. You can also configure the client to emit low-level tracing of input and output bytes. To enable this, add the option transport.traceBytes=true to your connection URI and configure the org.apache.qpid.jms.transports.netty.NettyTcpTransport logger to log level DEBUG .

Commands:
Chapter 5. Desktop Cancelling shutdown from a GUI session now switches to running session Previously, the policykit credentials for shutting down the system were not obtained up front before logging out. Consequently, if the users cancelled the policykit authentication dialog, they were sent back to the login screen instead of the graphical user interface (GUI) session. With this update, the dialog for obtaining credentials appears up front before the logout starts. As a result, when the users cancel the authentication dialog, they are sent back to their session instead of the login screen. (BZ# 1320245 )

Commands:
Appendix A. Revision History 0.1-3 Tue Sep 29 2020, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.9 Package Manifest. 0.1-2 Tue Mar 31 2020, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.8 Package Manifest. 0.1-1 Fri Nov 15 2019, Lenka Spackova ( lspackova@redhat.com ) Formal improvements to the document. 0.1-0 Thu Jul 18 2019, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.7 Package Manifest. 0.0-9 Sun Mar 31 2019, Lenka Spackova ( lspackova@redhat.com ) Updated information for the Supplementary channel. 0.0-8 Fri Jan 11 2019, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.6 Package Manifest. 0.0-7 Tue Apr 03 2018, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.5 Package Manifest. 0.0-6 Wed Nov 01 2017, Lenka Spackova ( lspackova@redhat.com ) Marked the bind packages correctly as Core. 0.0-5 Tue Aug 01 2017, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.4 Package Manifest. 0.0-4 Tue Nov 01 2016, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.3 Package Manifest. 0.0-3 Thu Nov 19 2015, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.2 Package Manifest. 0.0-2 Tue Mar 03 2015, Milan Navratil Release of the Red Hat Enterprise Linux 7.1 Package Manifest. 0.0-1 Tue Jun 10 2014, Eliska Slobodova Release of the Red Hat Enterprise Linux 7 Package Manifest.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ .NET in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To use AMQ .NET on Red Hat Enterprise Linux, you must install the the .NET Core 3.1 developer tools. For information, see the .NET Core 3.1 getting started guide . To build programs using AMQ .NET on Microsoft Windows, you must install Visual Studio. 2.2. Installing on Red Hat Enterprise Linux Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.10.0 .NET Core .zip file. Use the unzip command to extract the file contents into a directory of your choosing. USD unzip amq-clients-2.10.0-dotnet-core.zip When you extract the contents of the .zip file, a directory named amq-clients-2.10.0-dotnet-core is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document. Use a text editor to create the file USDHOME/.nuget/NuGet/NuGet.Config and add the following content: <?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3"/> <add key="amq-clients" value=" <install-dir> /nupkg"/> </packageSources> </configuration> If you already have a NuGet.Config file, add the amq-clients line to it. Alternatively, you can move the .nupkg file inside the <install-dir> /nupkg directory to an existing package source location. 2.3. Installing on Microsoft Windows Procedure Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.10.0 .NET .zip file. Extract the file contents into a directory of your choosing by right-clicking on the zip file and selecting Extract All . When you extract the contents of the .zip file, a directory named amq-clients-2.10.0-dotnet is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document.

Commands:
unzip amq-clients-2.10.0-dotnet-core.zip
<?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3"/> <add key="amq-clients" value=" <install-dir> /nupkg"/> </packageSources> </configuration>
Chapter 4. Publishing applications with .NET 8.0 .NET 8.0 applications can be published to use a shared system-wide version of .NET or to include .NET. The following methods exist for publishing .NET 8.0 applications: Self-contained deployment (SCD) - The application includes .NET. This method uses a runtime built by Microsoft. Framework-dependent deployment (FDD) - The application uses a shared system-wide version of .NET. Note When publishing an application for RHEL, Red Hat recommends using FDD, because it ensures that the application is using an up-to-date version of .NET, built by Red Hat, that uses a set of native dependencies. Prerequisites Existing .NET application. For more information about how to create a .NET application, see Creating an application using .NET . 4.1. Publishing .NET applications The following procedure outlines how to publish a framework-dependent application. Procedure Publish the framework-dependent application: Replace my-app with the name of the application you want to publish. Optional: If the application is for RHEL only, trim out the dependencies needed for other platforms: Replace architecture based on the platform you are using: For Intel: x64 For IBM Z and LinuxONE: s390x For 64-bit Arm: arm64 For IBM Power: ppc64le

Commands:
dotnet publish my-app -f net8.0
dotnet publish my-app -f net8.0 -r rhel.9- architecture --self-contained false
8.4. Configure Replication Mode (Library Mode) The following procedure shows a replication mode configuration in Red Hat JBoss Data Grid's Library mode. Procedure 8.2. Replication Mode Configuration Configure the Clustering Element The clustering element's mode parameter's value determines the clustering mode selected for the cache. The sync element's replTimeout parameter specifies the maximum time period in milliseconds for an acknowledgment after a remote call. If the time period ends without any acknowledgment, an exception is thrown. The stateTransfer element specifies how state is transferred when a node leaves or joins the cluster. It uses the following parameters: The chunkSize parameter is the number of cache entries to be transferred in one chunk. The default chunkSize value is 512. The chunkSize depends on many parameters (for example, size of entries) and the best setting needs to be measured. To change the value for larger cache entries, smaller chunks are advisable and for smaller cache entries, increasing the chunkSize offers better performance. The fetchInMemoryState parameter when set to true , requests state information from neighboring caches on start up. This impacts the startup time for the cache. Set the default to true if there is no shared cache store behind to avoid cache inconsistency. The awaitInitialTransfer parameter causes the first call to method CacheManager.getCache() on the joiner node to block and wait until the joining is complete and the cache has finished receiving state from neighboring caches (if fetchInMemoryState is enabled). This option applies to distributed and replicated caches only and is enabled by default. The timeout parameter specifies the maximum time (in milliseconds) the cache waits for responses from neighboring caches with the requested states. If no response is received within the timeout period, the start up process aborts and an exception is thrown. As a result of the failed state transfer, the cache is not available on that instance. Specify Transport Configuration The transport element defines the transport configuration for the cache container as follows: The clusterName parameter specifies the name of the cluster. Nodes can only connect to clusters that share the same name. The distributedSyncTimeout parameter specifies the time to wait to acquire a lock on the distributed lock. This distributed lock ensures that a single cache can transfer state or rehash state at a time. The transportClass parameter specifies a class that represents a network transport for the cache container. Report a bug

Commands:
<clustering mode="replication"> <sync replTimeout="USD{TIME}" /> <stateTransfer chunkSize="USD{SIZE}" fetchInMemoryState="{true/false}" awaitInitialTransfer="{true/false}" timeout="USD{TIME}" />
<global> <transport clusterName="USD{NAME}" distributedSyncTimeout="USD{TIME}" transportClass="USD{CLASS}" /> </global>
2.2. Networking QFQ queuing discipline In Red Hat Enterprise Linux 6.3, the tc utility has been updated to work with the Quick Fair Scheduler (QFQ) kernel features. Users can now take advantage of the new QFQ traffic queuing discipline from userspace. This feature is considered a Technology Preview. Package: kernel-2.6.32-279 vios-proxy, BZ# 721119 vios-proxy is a stream-socket proxy for providing connectivity between a client on a virtual guest and a server on a Hypervisor host. Communication occurs over virtio-serial links. Package: vios-proxy-0.1-1 IPv6 support in IPVS The IPv6 support in IPVS (IP Virtual Server) is considered a Technology Preview. Package: kernel-2.6.32-279

Commands:
1.3.2. Threats to Server Security Server security is as important as network security because servers often hold a great deal of an organization's vital information. If a server is compromised, all of its contents may become available for the attacker to steal or manipulate at will. The following sections detail some of the main issues. 1.3.2.1. Unused Services and Open Ports A full installation of Red Hat Enterprise Linux 7 contains 1000+ application and library packages. However, most server administrators do not opt to install every single package in the distribution, preferring instead to install a base installation of packages, including several server applications. A common occurrence among system administrators is to install the operating system without paying attention to what programs are actually being installed. This can be problematic because unneeded services may be installed, configured with the default settings, and possibly turned on. This can cause unwanted services, such as Telnet, DHCP, or DNS, to run on a server or workstation without the administrator realizing it, which in turn can cause unwanted traffic to the server, or even, a potential pathway into the system for attackers. Refer To Section 2.2, "Server Security" for information on closing ports and disabling unused services.

Commands:
8.4.2. Displaying SCAP Content SCAP standard defines numerous file formats. The oscap utility can process or create files conforming to many of the formats. In order to further process the given file with SCAP content, you need to understand how to use oscap with the given file type. If you are unsure how to use a particular file, you can either open and read the file, or you can use the info module of oscap which parses the file and extracts relevant information in human-readable format. Run the following command to examine the internal structure of a SCAP document and display useful information such as the document type, specification version, a status of the document, the date the document was published, and the date the document was copied to a file system: oscap info file where file is the full path to the security content file being examined. The following example better illustrates the usage of the oscap info command: Example 8.5. Displaying Information About SCAP Content

Commands:
~]USD oscap info /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml Document type: Source Data Stream Imported: 2014-08-28T15:41:34 Stream: scap_org.open-scap_datastream_from_xccdf_ssg-rhel6-xccdf-1.2.xml Generated: (null) Version: 1.2 Checklists: Ref-Id: scap_org.open-scap_cref_ssg-rhel6-xccdf-1.2.xml Profiles: xccdf_org.ssgproject.content_profile_test xccdf_org.ssgproject.content_profile_CS2 xccdf_org.ssgproject.content_profile_common xccdf_org.ssgproject.content_profile_server xccdf_org.ssgproject.content_profile_stig-rhel6-server-upstream xccdf_org.ssgproject.content_profile_usgcb-rhel6-server xccdf_org.ssgproject.content_profile_rht-ccp xccdf_org.ssgproject.content_profile_CSCF-RHEL6-MLS xccdf_org.ssgproject.content_profile_C2S Referenced check files: ssg-rhel6-oval.xml system: http://oval.mitre.org/XMLSchema/oval-definitions-5 Checks: Ref-Id: scap_org.open-scap_cref_ssg-rhel6-oval.xml Ref-Id: scap_org.open-scap_cref_output--ssg-rhel6-cpe-oval.xml Ref-Id: scap_org.open-scap_cref_output--ssg-rhel6-oval.xml Dictionaries: Ref-Id: scap_org.open-scap_cref_output--ssg-rhel6-cpe-dictionary.xml
probe::netfilter.bridge.forward Name probe::netfilter.bridge.forward - Called on an incoming bridging packet destined for some other computer Synopsis netfilter.bridge.forward Values br_fd Forward delay in 1/256 secs nf_queue Constant used to signify a 'queue' verdict brhdr Address of bridge header br_mac Bridge MAC address indev Address of net_device representing input device, 0 if unknown br_msg Message age in 1/256 secs nf_drop Constant used to signify a 'drop' verdict llcproto_stp Constant used to signify Bridge Spanning Tree Protocol packet pf Protocol family -- always " bridge " br_vid Protocol version identifier indev_name Name of network device packet was received on (if known) br_poid Port identifier outdev Address of net_device representing output device, 0 if unknown nf_repeat Constant used to signify a 'repeat' verdict llcpdu Address of LLC Protocol Data Unit length The length of the packet buffer contents, in bytes nf_stolen Constant used to signify a 'stolen' verdict br_cost Total cost from transmitting bridge to root nf_stop Constant used to signify a 'stop' verdict br_type BPDU type br_max Max age in 1/256 secs br_htime Hello time in 1/256 secs protocol Packet protocol br_bid Identity of bridge br_rmac Root bridge MAC address br_prid Protocol identifier outdev_name Name of network device packet will be routed to (if known) br_flags BPDU flags nf_accept Constant used to signify an 'accept' verdict br_rid Identity of root bridge

Commands: