mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 15. Deleting the Bootstrap User Important Before you delete the bootstrap user, create a real PKI administrative user as described in Chapter 14, Creating a role user . To delete the bootstrap user, follow the procedure described in 11.3.2.4 Deleting a Certificate System User in the Administration Guide (Common Criteria Edition) . 15.1. Disabling multi-roles support By default, users can belong to more than one subsystem group at once, allowing the user to act as more than one role. For example, John Smith could belong to both an agent and an administrator group. However, for highly secure environments, the subsystem roles should be restricted so that a user can only belong to one role. This can be done by disabling the multirole attribute in the instance's configuration. For all subsystems: Stop the server: OR if using the Nuxwdog watchdog: Open the CS.cfg file: Change the multiroles.enable parameter value from true to false . Add or edit the list of default roles in Certificate System that are affected by the multi-roles setting. If multi-roles is disabled and a user belongs to one of the roles listed in the multiroles.false.groupEnforceList parameter, then the user cannot be added to any group for any of the other roles in the list. Restart the server: OR if using the Nuxwdog watchdog:

Commands:
systemctl stop pki-tomcatd@instance_name.service
systemctl stop pki-tomcatd-nuxwdog@instance_name.service
vim /var/lib/pki/instance_name/ca/conf/CS.cfg
multiroles.false.groupEnforceList=Administrators,Auditors,Trusted Managers,Certificate Manager Agents,Registration Manager Agents,Key Recovery Authority Agents,Online Certificate Status Manager Agents,Token Key Service Manager Agents,Enterprise CA Administrators,Enterprise KRA Adminstrators,Enterprise OCSP Administrators,Enterprise TKS Administrators,Enterprise TPS Administrators,Security Domain Administrators,Subsystem Group
systemctl start pki-tomcatd@instance_name.service
systemctl start pki-tomcatd-nuxwdog@instance_name.service
function::user_string_n Name function::user_string_n - Retrieves string of given length from user space Synopsis Arguments addr the user space address to retrieve the string from n the maximum length of the string (if not null terminated) Description Returns the C string of a maximum given length from a given user space address. Reports an error on the rare cases when userspace data is not accessible at the given address.

Commands:
user_string_n:string(addr:long,n:long)
5.17. biosdevname 5.17.1. RHBA-2013:0138 - biosdevname bug fix update Updated biosdevname packages that fix one bug are now available for Red Hat Enterprise Linux 6. The biosdevname packages contain an optional convention for naming network interfaces; it assigns names to network interfaces based on their physical location. Biosdevname is disabled by default, except for a limited set of Dell PowerEdge, C Series, and Precision Workstation systems. Bug Fix BZ# 865446 Previously, biosdevname did not handle PCI cards with multiple ports properly. Consequently, only the network interface of the first port of these cards was renamed according to the biosdevname naming scheme. This bug has been fixed and network interfaces of all ports of these cards are now renamed as expected. Users of biosdevname are advised to upgrade to these update packages, which fix this bug.

Commands:
5.200. mod_wsgi 5.200.1. RHBA-2012:1358 - mod_wsgi bug fix and enhancement update Updated mod_wsgi packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The mod_wsgi packages provide a Apache httpd module, which implements a WSGI compliant interface for hosting Python based web applications. Bug Fix BZ# 670577 Prior to this update, a misleading warning message from the mod_wsgi utilities was logged during startup of the Apache httpd daemon. This update removes this message from the mod_wsgi module. Enhancement BZ# 719409 With this update, access to the SSL connection state is now available in WSGI scripts using the methods "mod_ssl.is_https" and "mod_ssl.var_lookup". All users of mod_wsgi are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Appendix C. Using AMQ Broker with the examples The AMQ Spring Boot Starter examples require a running message broker with a queue named example . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named example . USD <broker-instance-dir> /bin/artemis queue create --name example --address example --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2020-10-08 11:29:45 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name example --address example --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Chapter 16. Accessing odf-console with the ovs-multitenant plugin by manually enabling global pod networking In OpenShift Container Platform, when ovs-multitenant plugin is used for software-defined networking (SDN), pods from different projects cannot send packets to or receive packets from pods and services of a different project. By default, pods can not communicate between namespaces or projects because a project's pod networking is not global. To access odf-console, the OpenShift console pod in the openshift-console namespace needs to connect with the OpenShift Data Foundation odf-console in the openshift-storage namespace. This is possible only when you manually enable global pod networking. Issue When`ovs-multitenant` plugin is used in the OpenShift Container Platform, the odf-console plugin fails with the following message: Resolution Make the pod networking for the OpenShift Data Foundation project global:

Commands:
GET request for "odf-console" plugin failed: Get "https://odf-console-service.openshift-storage.svc.cluster.local:9001/locales/en/plugin__odf-console.json": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
oc adm pod-network make-projects-global openshift-storage
Chapter 4. Embedding applications for offline use You can embed microservices-based workloads and applications in a Red Hat Enterprise Linux for Edge (RHEL for Edge) image. Embedding means you can run a Red Hat build of MicroShift cluster in air-gapped, disconnected, or offline environments. 4.1. Embedding workload container images for offline use To embed container images in devices at the edge that do not have any network connection, you must create a new container, mount the ISO, and then copy the contents into the file system. Prerequisites You have root access to the host. Application RPMs have been added to a blueprint. You installed the OpenShift CLI ( oc ). Procedure Render the manifests, extract all of the container image references, and translate the application image to blueprint container sources by running the following command: USD oc kustomize ~/manifests | grep "image:" | grep -oE '[^ ]+USD' | while read line; do echo -e "[[containers]]\nsource = \"USD{line}\"\n"; done >><my_blueprint>.toml Push the updated blueprint to image builder by running the following command: USD sudo composer-cli blueprints push <my_blueprint>.toml If your workload containers are located in a private repository, you must provide image builder with the necessary pull secrets: Set the auth_file_path in the [containers] section in the /etc/osbuild-worker/osbuild-worker.toml configuration file to point to the pull secret. If needed, create a directory and file for the pull secret, for example: Example directory and file [containers] auth_file_path = "/<path>/pull-secret.json" 1 1 Use the custom location previously set for copying and retrieving images. Build the container image by running the following command: USD sudo composer-cli compose start-ostree <my_blueprint> edge-commit Proceed with your preferred rpm-ostree image flow, such as waiting for the build to complete, exporting the image and integrating it into your rpm-ostree repository or creating a bootable ISO. 4.2. Additional resources Options for embedding Red Hat build of MicroShift applications in a RHEL for Edge image Creating the RHEL for Edge image Add the blueprint to image builder and build the ISO Download the ISO and prepare it for use Upgrading RHEL for Edge systems

Commands:
oc kustomize ~/manifests | grep "image:" | grep -oE '[^ ]+USD' | while read line; do echo -e "[[containers]]\nsource = \"USD{line}\"\n"; done >><my_blueprint>.toml
sudo composer-cli blueprints push <my_blueprint>.toml
[containers] auth_file_path = "/<path>/pull-secret.json" 1
sudo composer-cli compose start-ostree <my_blueprint> edge-commit
Chapter 23. MVEL Overview MVEL is a Java-based dynamic language that is similar to OGNL, but is reported to be much faster. The MVEL support is in the camel-mvel module. Syntax You use the MVEL dot syntax to invoke Java methods, for example: Because MVEL is dynamically typed, it is unnecessary to cast the message body instance (of Object type) before invoking the getFamilyName() method. You can also use an abbreviated syntax for invoking bean attributes, for example: Adding the MVEL module To use MVEL in your routes you need to add a dependency on camel-mvel to your project as shown in Example 23.1, "Adding the camel-mvel dependency" . Example 23.1. Adding the camel-mvel dependency Built-in variables Table 23.1, "MVEL variables" lists the built-in variables that are accessible when using MVEL. Table 23.1. MVEL variables Name Type Description this org.apache.camel.Exchange The current Exchange exchange org.apache.camel.Exchange The current Exchange exception Throwable the Exchange exception (if any) exchangeID String the Exchange ID fault org.apache.camel.Message The Fault message(if any) request org.apache.camel.Message The IN message response org.apache.camel.Message The OUT message properties Map The Exchange properties property( name ) Object The value of the named Exchange property property( name , type ) Type The typed value of the named Exchange property Example Example 23.2, "Route using MVEL" shows a route that uses MVEL. Example 23.2. Route using MVEL

Commands:
getRequest().getBody().getFamilyName()
request.body.familyName
<!-- Maven POM File --> <properties> <camel-version>2.23.2.fuse-7_13_0-00013-redhat-00001</camel-version> </properties> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-mvel</artifactId> <version>USD{camel-version}</version> </dependency> </dependencies>
<camelContext> <route> <from uri="seda:foo"/> <filter> <language langauge="mvel">request.headers.foo == 'bar'</language> <to uri="seda:bar"/> </filter> </route> </camelContext>
7.183. piranha 7.183.1. RHBA-2013:0351 - piranha bug fix and enhancement update Updated piranha packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Piranha provides high-availability and load-balancing services for Red Hat Enterprise Linux. The piranha packages contain various tools to administer and configure the Linux Virtual Server (LVS), as well as the heartbeat and failover components. LVS is a dynamically-adjusted kernel routing mechanism that provides load balancing, primarily for Web and FTP servers. Bug Fixes BZ# 857917 The IPVS timeout values in the Piranha web interface could be reset whenever the Global Settings page was visited. As a consequence, if the Transmission Control Protocol (TCP) timeout, TCP FIN timeout, or User Datagram Protocol (UDP) timeout values had been set, these values could be erased from the configuration file. This bug has been fixed and all IPVS timeout values are preserved as expected. BZ#860924 Previously, the Piranha web interface incorrectly displayed the value "5" for a virtual server interface. With this update, the Piranha web interface properly displays the interface associated with a virtual server. All users of piranha are advised to upgrade to these updated packages, which fix these bugs. 7.183.2. RHBA-2013:0576 - piranha bug fix update Updated piranha packages that fix one bug are now available for Red Hat Enterprise Linux 6. Piranha provides high-availability and load-balancing services for Red Hat Enterprise Linux. The piranha packages contain various tools to administer and configure the Linux Virtual Server (LVS), as well as the heartbeat and failover components. LVS is a dynamically-adjusted kernel routing mechanism that provides load balancing, primarily for Web and FTP servers. Bug Fix BZ# 915584 Previously, the lvsd daemon did not properly activate the sorry server fallback service when all real servers were determined to be unavailable. As a result, incoming traffic for a virtual service with no available real servers were not directed to the sorry server. With this update, the lvsd daemon properly activates the sorry server when no real servers are available. Users of piranha are advised to upgrade to these updated packages, which fix this bug.

Commands:
4.3. Configuring Static Routes with GUI To set a static route, open the IPv4 or IPv6 settings window for the connection you want to configure. See Section 3.4.1, "Connecting to a Network Using the control-center GUI" for instructions on how to do that. Routes Address - Enter the IP address of a remote network, sub-net, or host. Netmask - The netmask or prefix length of the IP address entered above. Gateway - The IP address of the gateway leading to the remote network, sub-net, or host entered above. Metric - A network cost, a preference value to give to this route. Lower values will be preferred over higher values. Automatic When Automatic is ON , routes from RA or DHCP are used, but you can also add additional static routes. When OFF , only static routes you define are used. Use this connection only for resources on its network Select this check box to prevent the connection from becoming the default route. Typical examples are where a connection is a VPN tunnel or a leased line to a head office and you do not want any Internet-bound traffic to pass over the connection. Selecting this option means that only traffic specifically destined for routes learned automatically over the connection or entered here manually will be routed over the connection.

Commands:
Chapter 103. Checking services using IdM Healthcheck You can monitor services used by the Identity Management (IdM) server using the Healthcheck tool. For details, see Healthcheck in IdM . Prerequisites The Healthcheck tool is only available on RHEL 8.1 and newer 103.1. Services Healthcheck test The Healthcheck tool includes a test to check if any IdM services is not running. This test is important because services which are not running can cause failures in other tests. Therefore, check that all services are running first. You can then check all other test results. To see all services tests, run ipa-healthcheck with the --list-sources option: You can find all services tested with Healthcheck under the ipahealthcheck.meta.services source: certmonger dirsrv gssproxy httpd ipa_custodia ipa_dnskeysyncd ipa_otpd kadmin krb5kdc named pki_tomcatd sssd Note Run these tests on all IdM servers when trying to discover issues. 103.2. Screening services using Healthcheck Follow this procedure to run a standalone manual test of services running on the Identity Management (IdM) server using the Healthcheck tool. The Healthcheck tool includes many tests, whose results can be shortened with: Excluding all successful test: --failures-only Including only services tests: --source=ipahealthcheck.meta.services Procedure To run Healthcheck with warnings, errors and critical issues regarding services, enter: A successful test displays empty brackets: If one of the services fails, the result can looks similarly to this example: Additional resources See man ipa-healthcheck .

Commands:
ipa-healthcheck --list-sources
ipa-healthcheck --source=ipahealthcheck.meta.services --failures-only
{ "source": "ipahealthcheck.meta.services", "check": "httpd", "result": "ERROR", "kw": { "status": false, "msg": "httpd: not running" } }
1.3. Automated Installation Anaconda installations can be automated through the use of a Kickstart file. Kickstart files can be used to configure any aspect of installation, allowing installation without user interaction, and can be used to easily automate installation of multiple instances of Red Hat Enterprise Linux. In most situations, you can simply follow the procedure outlined in Section 4.2, "Automatic Installation" to create and configure a Kickstart file, which can be used to perform an arbitrary number of non-interactive installations of Red Hat Enterprise Linux. Kickstart files can be automatically created based on choices made using the graphical interface, through the online Kickstart Generator tool, or written from scratch using any text editor. For more information, see Section 27.2.1, "Creating a Kickstart File" . Kickstart files can be easily maintained and updated using various utilities in Red Hat Enterprise Linux. For more information, see Section 27.2.2, "Maintaining the Kickstart File" .

Commands:
B.111. yum-rhn-plugin and rhn-client-tools B.111.1. RHEA-2010:0949 - yum-rhn-plugin and rhn-client-tools enhancement update Updated yum-rhn-plugin and rhn-client-tools packages that add an enhancement are now available for Red Hat Enterprise Linux 6. Red Hat Network Client Tools provide programs and libraries that allow a system to receive software updates from Red Hat Network (RHN). yum-rhn-plugin allows yum to access a Red Hat Network server for software updates. Enhancement BZ# 649435 These packages have been updated to support the Red Hat Network Satellite Server Maintenance Window, allowing a user to download scheduled packages and errata before the start of the maintenance window. Users of rhn-client-tools and yum-rhn-plugin are advised to upgrade to these updated packages, which add this enhancement. Note that this feature is disabled by default. For information on how to enable it, refer to https://access.redhat.com/site/solutions/42227 .

Commands:
Migrating from a standalone Manager to a self-hosted engine Red Hat Virtualization 4.3 How to migrate the Red Hat Virtualization Manager from a standalone server to a self-managed virtual machine Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to migrate your Red Hat Virtualization environment from a Manager installed on a physical server (or a virtual machine running in a separate environment) to a Manager installed on a virtual machine running on the same hosts it manages.

Commands:
5.300. setroubleshoot 5.300.1. RHBA-2012:1005 - setroubleshoot bug fix update Updated setroubleshoot packages that fix one bug are now available for Red Hat Enterprise Linux 6. The setroubleshoot packages provide tools to help diagnose SELinux problems. When AVC messages are returned, an alert can be generated that provides information about the problem and helps to track its resolution. Alerts can be customized to user preference. The same tools can used to process log files. Bug Fix BZ# 832186 Previously, SELinux Alert Browser did not display alerts even if selinux denials were presented. This was caused by sedispatch, which did not handle audit messages correctly, and users were not able to fix their SELinux issues according to the SELinux alerts. With this update, this bug has been fixed so that users are now able to fix their SELinux issues using setroubleshoot, as expected. All users of setroubleshoot are advised to upgrade to these updated packages, which fix this bug. 5.300.2. RHBA-2012:0781 - setroubleshoot bug fix update Updated setroubleshoot packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The setroubleshoot packages provide tools to help diagnose SELinux problems. When AVC messages are returned, an alert can be generated that provides information about the problem and helps to track its resolution. Alerts can be customized to user preference. The same tools can be used to process log files. Bug Fixes BZ# 757857 Previously, when the system produced a large amount of SELinux denials, the setroubleshootd daemon continued to process all of these denials and increased its memory consumption. Consequently, a memory leak could occur. This bug has been fixed and memory leaks no longer occur in the described scenario. BZ# 633213 When a duplicated command-line option was passed to the sealert utility, sealert terminated with an error message. With this update, the duplicate options are ignored and sealert works as expected, thus fixing this bug. BZ# 575686 Previously, some translations for setroubleshoot were incomplete or missing. This update provides complete translations for 22 languages. Users of setroubleshoot are advised to upgrade to these updated packages, which fix these bugs.

Commands: