- Overview
- Requirements
- 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
Online Single-node Evaluation Installation
This page explains how you can perform an online 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 .
Take the following steps to install Automation Suite on a single machine that has access to the internet.
The installation process has the following general steps:
Step |
Description |
---|---|
Step 1: Download the installation script and run the interactive wizard |
Step 1.1: Copy the interactive install wizard to the target machine for InstallationStep 1.2: Run the interactive install wizard to configure the install options |
Step 2: Configure the installation |
Step 2.1: Run the interactive wizard to configure the install options: The tool will gather inputs for most common install options and generate a configuration file that will be used during the installation. Step 2.2: (Optional) Configure the advanced install options. The default install configuration includes the products used in the core automation platform, and a shared SQL server to be used by all products. To customize the products installed or have separate SQL servers used for specific products, you can do so by editing the configuration file. If you use a proxy to connect to the internet, you will configure it at this point. After you finish editing the file, you need to re-run the wizard to complete the installation. |
Step 3: Complete the installation |
Step 3: 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
chmod +x ~/installUiPathAS.sh
./installUiPathAS.sh
chmod +x ~/installUiPathAS.sh
./installUiPathAS.sh
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, Automation Hub, and Data Service.
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.
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 access the newly created cluster and suite, see Accessing Automation Suite.
To resize the PVC, see Resizing PVC.
If you installed AI Center, we recommend resizing the PVC to 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 script and running the interactive installer
- Step 1.1: Copying the interactive installer to the target machine
- Step 1.2: Running the interactive installer to configure the installation options
- Step 2: Configuring the installation
- Step 2.1: Basic configuration
- Step 2.2: (Optional) Advanced configuration
- Step 3: Completing the Installation
- Updating Certificates
- Accessing Automation Suite
- Resizing PVC