- Overview
- Requirements
- Installation
- Q&A: Deployment Templates
- Configuring the Machines
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the Certificates
- Online Single-node Evaluation Installation
- Offline Single-node Evaluation Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to address weak ciphers in TLS 1.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure After Certificate Update
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to Resize Objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Cannot Log in After Migration
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Pods cannot communicate with FQDN in a proxy environment
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Offline Single-node Evaluation Installation
This page explains how you can perform an offline Automation Suite installation with a single-node evaluation setup.
You must meet the hardware and software prerequisites before proceeding with the installation. See Hardware and software requirements.
You can use a dedicated script to validate the installation prerequisites and infrastructure readiness. See Validating the prerequisites.
For a smooth installation experience, make sure to follow our best practices. See .
Use the offline installation steps in this document when deploying UiPath Automation suite in a airgapped environment with no access to the internet. If deploying an environment where the machines have internet access we recommend using the online installation steps which are optimized for that case.
The installation process has the following general steps:
Step |
Description |
---|---|
Step 1: Download the installation packages |
This step needs to be performed from a machine with access to internet and to the air-gapped machines where Automation Suite will be deployed. While these are finishing downloading, you can continue to some of the next steps. This can be done from a Linux or windows machine. |
Step 2: Configure the installation |
The interactive install wizard gathers inputs for most common install options and generate a configuration file that will be used during the installation. |
Step 3: Run the installation |
Run the installation.Once the installation is complete, you can start using the cluster. |
Step 4: Complete the installation |
You have completed the installation successfully and can move to post-installation steps. You can now access the newly created cluster and suite, update certificates, resize the PVC, and more. |
RHEL kernel version kernel-4.18.0-477.10.1.el8_8 is affected by an issue that interrupts the installation or management of the Automation Suite cluster. Make sure that none of the Automation Suite nodes uses this kernel version either pre- or post-installation. You can update the kernel version by running the following command:
dnf install -y kernel kernel-tools kernel-tools-libs
dnf install -y kernel kernel-tools kernel-tools-libs
This machine can be Linux or Windows. The commands in this guide are for RHEL-based OS. For Windows or other OSes, adjust for equivalent commands specific to those environments.
The Automation Suite installer is a wrapper of multiple packages that also installs some dependencies using Red Hat Package Manager (RPM). It provides an interactive experience that helps you configure external resources such as SQL and other installation options.
ON THE SEPARATE MACHINE WITH INTERNET ACCESS
This section explains how to get the required files to start the installation process.
Make sure to take the following steps:
- Check that all files finished downloaded on the machine with internet access;
- Create the target folder on the machine;
- Copy the files from the online machine to the target machine.
ON THE MAIN MACHINE OF THE CLUSTER
Create the installation folder by running the following command:
sudo su -
mkdir -p /opt/UiPathAutomationSuite/
chmod -R 755 /opt/UiPathAutomationSuite
mkdir -p /uipath/tmp
chmod -R 777 /uipath/tmp
sudo su -
mkdir -p /opt/UiPathAutomationSuite/
chmod -R 755 /opt/UiPathAutomationSuite
mkdir -p /uipath/tmp
chmod -R 777 /uipath/tmp
mkdir -p /opt/UiPathAutomationSuite/
is not required if you use the configureUiPathDisks.sh script.
Copy the files to one of the nodes:
Running the interactive wizard in single-node offline mode
Run the interactive install wizard to configure the installation options. The tool gathers inputs for most common installation options and generates a configuration file that you can use during the installation.
By running the installation using the default configuration, you are opting to run our default experience. You will install our core platform: Orchestrator, Insights, Test Manager, Action Center, Automation Ops, and Automation Hub.
To install Automation Suite using the interactive wizard, take the following steps:
This step is optional.
cluster_config.json
file in the UiPathAutomationSuite
folder. You can use this file to enable additional products, disable any of the default products, configure your SQL DBs
and their respective connection strings, and certificates. You can also enable proxy settings if you use a proxy for internet
connection.
For single-node evaluation installation, note that you cannot enable High Availability.
For advanced configuration, see Advanced installation experience.
You must to re-run the interactive installer to complete the installation.
Make sure you copied the downloaded files on the main offline machine, where you performed the configuration, in the install folder created by the install wizard.
Before running the installation, make sure to read the License Agreement.
To accept the license agreement, choose one of the following methods:
- Option 1 (Environment Variable): Set the
LICENSE_AGREEMENT
environment variable to accept by executing the following command:export LICENSE_AGREEMENT=accept
- Option 2 (Inline parameter): Alternatively, append
--accept-license-agreement
to every execution ofinstall-uipath.sh
.
Run the installation commands to execute the offline bundle (estimated duration: 2h30min - 3h30min):
./install-uipath.sh -i ./cluster_config.json -o ./output.json -a --offline-bundle /uipath/tmp/sf.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement
./install-uipath.sh -i ./cluster_config.json -o ./output.json -a --offline-bundle /uipath/tmp/sf.tar.gz --offline-tmp-folder /uipath/tmp --install-offline-prereqs --accept-license-agreement
./install-uipath.sh -h --accept-license-agreement
.
To load the optional Document Understanding bundles, execute the following commands:
./configureUiPathAS.sh registry upload --optional-offline-bundle "/uipath/tmp/du-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp"
./configureUiPathAS.sh registry upload --optional-offline-bundle "/uipath/tmp/du-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp"
./configureUiPathAS.sh registry upload --optional-offline-bundle "/uipath/tmp/cv-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp"
./configureUiPathAS.sh registry upload --optional-offline-bundle "/uipath/tmp/cv-ondemand.tar.gz" --offline-tmp-folder "/uipath/tmp"
This document focuses on -a command argument as this caters to need of installing all the required components.
If you install Task Mining in single-node evaluation mode, you need to run an additional set of steps. Follow the Task Mining installation guide to complete the steps for Task Mining.
The installation process generates self-signed certificates on your behalf. However, the Azure deployment template also gives you the option to provide a CA-issued server certificate at installation time instead of using an auto-generated self-signed certificate.
Self-signed certificates will expire in 90 days, and you must replace them with certificates signed by a trusted CA as soon as installation completes. If you do not update the certificates, the installation will stop working after 90 days.
For instructions, see Managing certificates.
To resize the PVC, see Resizing PVC.
200
immediately after the installation to avoid downtimes. For more information on this, check Resizing PVC for AI Center.
- Overview
- Step 1: Downloading the installation packages and getting the files on the machine
- Step 1.1: Downloading the installation packages
- Step 1.2: Getting all downloaded files on the machine
- Step 2: Configuring the installation
- Step 2.1: Basic configuration
- Step 2.2: (Optional) Advanced configuration
- Step 3: Running the installation
- Accepting the license agreement
- Running the installation
- Loading the optional bundles
- Installing Task Mining
- Step 4: Completing the Installation
- Updating Certificates
- Accessing Automation Suite
- Resizing PVC
- Adding Rancher/pause:3.5