- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Configuring the machines
- Configuring the external objectstore
- Configuring an external Docker registry
- Configuring the load balancer
- Configuring the DNS
- Configuring Microsoft SQL Server
- Configuring the certificates
- Online multi-node HA-ready production installation
- Offline multi-node HA-ready production installation
- Disaster recovery - Installing the secondary cluster
- Downloading the installation packages
- install-uipath.sh parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- 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 bundle
- 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 manually set the ArgoCD log level to Info
- How to generate the encoded pull_secret_value for external registries
- 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
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- GPU node affected by resource unavailability
- Volume unable to mount due to not being ready for workloads
- Support bundle log collection failure
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- 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
- Authentication not working 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 due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- 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
- ArgoCD goes into progressing state after first installation
- Issues accessing the ArgoCD read-only account
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Adding a dedicated agent Node for Task Mining
Before starting the Task Mining installation, make sure to check the Hardware requirements. Task Mining has a dependency on AI Center; therefore, to use Task Mining, you must also install AI Center.
After completing the Automation Suite installation, take the following steps to set up Task Mining.
If you already enabled Task Mining in the configuration during the main install, you can skip this step. If not, you need to enable AI Center and Task Mining by editing the configuration and rerunning the install.
aicenter
and task_mining
in the cluster_config.json
configuration file when applying the advanced configuration.
cluster_config.json
Task Mining config
{
"aicenter": {
"enabled": Boolean
},
"task_mining": {
"enabled": Boolean
}
}
{
"aicenter": {
"enabled": Boolean
},
"task_mining": {
"enabled": Boolean
}
}
Follow the steps for configuring a server node to ensure the disk is partitioned correctly.
For online installation
SSH to the right machine:
- If you added Task Mining to a single-node evaluation install, go to the machine and run this next step.
- If you added Task Mining to a multi-node HA-ready production install, go to any of the server nodes.
UiPathAutomationSuite
folder to the Task Task Mining node (username and DNS are specific to the Task Mining node):
sudo su -
scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt/
scp -r ~/* <username>@<node dns>:/opt/UiPathAutomationSuite/
sudo su -
scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt/
scp -r ~/* <username>@<node dns>:/opt/UiPathAutomationSuite/
For offline installation
SSH to the primary installation node
UiPathAutomationSuite
directory contains as-infra.tar.gz
file ( is a part of the installation package download step )
scp -r ~/opt/UiPathAutomationSuite <username>@<node dns>:/var/tmp
scp -r ~/opt/UiPathAutomationSuite <username>@<node dns>:/var/tmp
For online installation
SSH to the Task Mining Node and run the following commands:
sudo su -
cd /opt/UiPathAutomationSuite
yum install unzip jq -y
CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json
UNATTENDED_ACTION="accept_eula,download_bundle,extract_bundle,join_task_mining" ./installUiPathAS.sh
sudo su -
cd /opt/UiPathAutomationSuite
yum install unzip jq -y
CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json
UNATTENDED_ACTION="accept_eula,download_bundle,extract_bundle,join_task_mining" ./installUiPathAS.sh
For offline installation
Connect via SSH to the Task Mining dedicated node & install the platform bundle on it using the script below.
sudo su
mv /var/tmp/UiPathAutomationSuite /opt
cd /opt/UiPathAutomationSuite
sudo chmod -R 755 /opt/UiPathAutomationSuite
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j task-mining --offline-bundle ./as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreement
sudo su
mv /var/tmp/UiPathAutomationSuite /opt
cd /opt/UiPathAutomationSuite
sudo chmod -R 755 /opt/UiPathAutomationSuite
sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j task-mining --offline-bundle ./as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreement
Run below command to set the kubectl context on taskmining machine
sudo su -
export KUBECONFIG=/var/lib/rancher/rke2/agent/kubelet.kubeconfig
export PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes
sudo su -
export KUBECONFIG=/var/lib/rancher/rke2/agent/kubelet.kubeconfig
export PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes
You should see the nodes and their corresponding names. You need the name of the Task Mining node for the next step.
Finally, run the following command to check if the Task Mining node is configured. Please update the \<node name\> with Task Mining node name in below command.
kubectl describe node <node name> | grep -i "taints"
kubectl describe node <node name> | grep -i "taints"
Above command should return you the following output
At this point, you have successfully completed the installation for Task Mining. Sign in to the Automation Suite Portal and enable it in the tenant management UX under the Admin section.
You must configure system email notifications as Task Mining relies on the Automation Suite notification system to send emails.
For instructions on creating a Task Mining project, see the Task Mining documentation.
Follow the steps for the given deployment type, online or offline.
Before proceeding with the steps below, it is mandatory to start with following the steps from Uploading ML Packages.
After uploading the ML package, follow the listed steps:
5. Name the package, choose the most recent package version, and click Submit to create a machine-learning deployment package.
As Task Mining is a data-heavy application, we recommend an additional 1024 GiB of storage to handle the screenshots and metadata collected during studies. After adding a secondary disk, you must resize the Longhorn storage to incorporate it.
You can add the additional disk either pre- or post installation. If you add it post-installation, you must take additional steps to configure the new disk in the cluster.
For details, see Configuring new data disk in the cluster.
UiPathAutomationSuite
folder and run the following command:
sudo su -
cd /opt/UiPathAutomationSuite
sudo ./configureUiPathAS.sh objectstore resize-pvc --size 1000Gi --sub-component data
sudo su -
cd /opt/UiPathAutomationSuite
sudo ./configureUiPathAS.sh objectstore resize-pvc --size 1000Gi --sub-component data
- Hardware requirements
- Enable Task Mining on the Cluster
- Editing the Configuration
- Configuring a Dedicated Node for Task Mining
- Step One: Configure the Machine
- Step Two: Copy the Interactive Installation Wizard to the Target Machine for Installation
- Step Three: Run the Interactive Installer to Configure the Dedicated Node
- Step Four: Enabling Kubectl
- Step Five: Verifying Task Mining Configuration
- Configuring email
- Starting a Task Mining project
- Configuring the Task Mining ML Model in AI Center
- Online and Offline Installations
- Increasing secondary disk/Longhorn storage
- Configuring a new disk in the cluster
- Increasing storage capacity