Ins-35423 The Installer Has Detected

95 views

Skip to first unread message

Vickiana Sconyers

unread,

Aug 4, 2024, 9:47:32 PM8/4/24

to studbackdincock

CauseThe ORACLE_HOME environment variable was already set. This prevents proper use of multiple Oracle homes and, as it is not required for any Oracle products to function, it will be unset in your environment.

Cause: Oracle does not recommend placing Oracle Database files on ACFS. Oracle recommends that you place database files directly on the underlying Oracle ASM disk groups, as this provides optimal database performance.

Action: Oracle Grid Infrastructure for Clusterware is not installed. Install it either from the separate installation media included in your media pack, or install it by downloading it from Electronic Product Delivery (EPD) or the Oracle Technology Network (OTN). Oracle Grid Infrastructure normally is installed by a different operating system user than the one used for Oracle Database. It may need to be installed by your system administrator. See the installation guide for more details.

Action: Migrate database storage from Oracle ASM to a file system before upgrading, or migrate earlier release databases versions that use Oracle ASM storage to 64-bit Windows systems. See the upgrade guide for additional information.

Action: Start the Oracle Clusterware stack by running the following command as the root user from the Oracle Clusterware home (Grid home) : /bin/crsctl start crs. When the Oracle Clusterware stack is running, restart the installer and continue with the Oracle RAC installation.

Cause: The installer detects that the location you specified for the Oracle home is under an Oracle ASM Cluster File System (ACFS) mount point that is not registered with Oracle Grid Infrastructure on this server.

Action: Oracle Database homes can only be placed on ACFS locations registered with Oracle Grid Infrastructure software. Specify a different location for the Oracle home, or register this location with Oracle Grid Infrastructure software.

Cause: Installer has detected that the location specified for Oracle home is a sub directory under an Automatic Cluster File System(ACFS) mount point that does not provide permissions to your user id.

[FATAL] [INS-35423] The installer has detected that Oracle Clusterware is not running on local node.

CAUSE: You have chosen to install Oracle RAC when Oracle Clusterware stack is not running on the local node.

ACTION: Start the Oracle Clusterware stack by running the following command as the root user from the Oracle Clusterware home (Grid home) : /bin/crsctl start crs. When the Oracle Clusterware stack is running, restart the installer and continue with the Oracle RAC installation.

A Foreman installation will always contain a central Foreman instancethat is responsible for providing the Web based GUI, nodeconfigurations, initial host configuration files, etc. However, if theForeman installation supports unattended installations, then otheroperations need to be performed to fully automate this process. TheSmart Proxy manages remote services and is generally installed with allForeman installations to manage TFTP, DHCP, DNS, Puppet, Puppet CA,Ansible, and Salt.

A Smart-Proxy is located on or near a machine that performs a specific function and helps Foreman orchestrate the process of commissioning a new host. Placing the Smart Proxy on or near to the actual service will also help reduce latency in large distributed organizations.

Inventory management has always been a core feature of Foreman.In Foreman 2.2 the host detail page redesign was started and made default in Foreman 3.2.This release greatly enhances the page with many more integrations which provides the user a more complete overview without having to navigate to other pages.

For a long time foreman_column_view has provided a way to customize the columns on the host list.The new Selectable columns feature feature brings a lot of this functionality to Foreman itself without the need to know a lot about the Foreman internals.

HTTP/2 is now enabled by default on all platforms.Compared to HTTP/1(.1) the newer HTTP/2 protocol allows multiplexing over a single connection, making it possible for clients to retrieve multiple resources at the same time.For example, browsers no longer need to wait for one one image to complete before requesting the next image.

The installer now ensures Redis 6 is used on Enterprise Linux 8.The Redis 5 AppStream went EOL in May 2022.Previously it was up to the user to switch streams, but now the installer enforces the redis:6 stream and updates the package.

The installer no longer manages ansible.cfg and thus allows users to put in their own modifications.This file was previously used to configure the options that Foreman required to have set.This is no longer the case as the necessary options are set using a different mechanism.During upgrades the file is not touched which means some cruft remains.It is safe to remove the file or remove all content.

Adam Ruzicka, Alex Fisher, Alexander Olofsson, Amit Upadhye, Anthony Somerset, Bastian Schmidt, Bernhard Suttner, Chris Roberts, Christian Ruppert, Dirk Gtz, Dirk Heinrichs, Dyrkon, Elkin Aguas, Eric D. Helms, Evgeni Golov, Ewoud Kohl van Wijngaarden, Frank Adaemmer, Ian Ballou, Jeremy Lenz, Jonas Trstedt, Kamil Szubrycht, Karolina Malyjurkova, Leos Stejskal, Lior Keren, Lucy Fu, Lukš Zapletal, Manuel Laug, Marcel Khlhorn, Marek Huln, Maria Agaphontzev, Matt Darcy, Matěj Mudra, Maximilian Kolb, Nofar Alfassi, Oleh Fedorenko, Ondrej Ezr, Partha Aji, Pat Riehecky, Paul Donohue, Pavel Moravec, Peter Koprda, Quirin Pamp, Ron Lavi, Samir Jha, Sayan Das, Shim Shtein, William Clark, benjamin-robertson, kobybr, timdeluxe, Štefan Nmeth

The Foreman installer is a collection of Puppet modules that installs everything required for a full working Foreman setup. It uses native OS packaging (e.g. RPM and .deb packages) and adds necessary configuration for the complete installation.

The installation run is non-interactive, but the configuration can be customized by supplying any of the options listed in foreman-installer --help, or by running foreman-installer -i for interactive mode. More examples are given in the Installation Options section. Adding -v will disable the progress bar and display all changes. To run the installer, execute:

Over the last year, Foreman community members have been open-sourcing Red Hat documentation to make more comprehensive guides available to Foreman users. At the moment, the following guides have been migrated to a work-in-progress Foreman and Katello documentation site. This project is not yet complete, but you might find useful information in some of the following guides:

Clicking the YAML button when back on the host page will show the ntp class and the servers parameter, as passed to Puppet via the ENC (external node classifier) interface. Re-run puppet agent --test on the Foreman host to see the NTP service automatically reconfigured by Puppet and the NTP module.

Other hosts with Puppet agents installed can use this Puppet server by setting server = foreman.example.com in puppet.conf. Sign their certificates in Foreman by going to Infrastructure > Smart Proxies > Certificates or using puppet cert list and puppet cert sign on the Puppet server.

Puppet classes can be added to host groups in Foreman instead of individual hosts, enabling a standard configuration of many hosts simultaneously. Host groups are typically used to represent server roles.

This sections outlines the system requirements for an installation of Foreman. This will cover the hardware requirements, OS requirements and firewall requirements. This includes variations for all supported database types.

The hardware requirements for Foreman depend primarily on the number of requests that it will receive, which depends on the number of configuration management clients, web UI activity and other systems using the API.

Foreman integrates with Puppet and Facter in a few places, but generally using a recent, stable version will be fine. The exact versions of Puppet, Puppetserver and Facter that Foreman is compatible with are listed below.

The Foreman installer has code for both AIO and non-AIO configurations, switching behavior automatically based on the version of Puppet installed (usually during the first run when answers are stored). Only AIO installations are tested.

Puppetserver is the application for serving Puppet agents used by default since Puppet 4. Both Fedora and Debian have not packaged Puppetserver for their non-AIO packages. The Puppetlabs packages must be used.

The installer is a collection of Puppet modules, which have a large number of parameters available to customize the configuration. Parameters can be set by running foreman-installer with arguments, e.g. --foreman-initial-admin-password, changing settings in interactive mode or by setting up an answers file.

Every parameter available in the installer can be set using command line arguments to foreman-installer. Run foreman-installer --help for most options, or foreman-installer --full-help for a list of every available option.

When running the installer, all arguments passed on the command line will be persisted by default to /etc/foreman-installer/scenarios.d/foreman-answers.yaml and used automatically on subsequent runs, without needing to specify those arguments again. This persistence can be disabled with the -b option.

The answers file describes the classes that will be applied to the host toinstall Foreman, along with their parameters. The foreman-installer package stores it at /etc/foreman-installer/scenarios.d/foreman-answers.yaml. By default, the all-in-one setup will include Foreman, a puppetmaster, Puppet agent, and the Smart Proxy: