- 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
- Performing a 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 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
- How to work with certificates
- How to collect DU usage data with in-cluster objectstore (Ceph)
- How to install RKE2 SELinux on air-gapped environments
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Failure to configure email alerts post upgrade
- No healthy upstream issue
- Document Understanding not on the left rail of Automation Suite
- Failed status when creating a data labeling session
- Failed status when trying to deploy an ML skill
- Migration job fails in ArgoCD
- Handwriting recognition with intelligent form extractor not working
- Failed ML skill deployment due to token expiry
- 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
- Exploring Logs

Automation Suite on Linux installation guide
Using the Automation Suite support bundle
linkOverview
linkYou can get the Automation Suite Support Bundle tool in the following ways:
- By unzipping the as-installer.zip installer package
- By downloading the supportability-tools.zip
Before running the Automation Suite Support Bundle tool, navigate to the installer folder. You can find the installer in the following location or anywhere you downloaded it:
cd /opt/UiPathAutomationSuite/{version}/installer
cd /opt/UiPathAutomationSuite/{version}/installer
To start using the Automation Suite Support Bundle tool, run the following commands:
cd ./Support-Tools/support-bundle
./support-bundle.sh
cd ./Support-Tools/support-bundle
./support-bundle.sh
The following image shows a typical output for this command:
Automation Suite Support Bundle Tool parameters
link-
Running only
bash support-bundle.sh
collects logs for the last 2 days from the S3-compatible objectstore, if you use an external objectstore, or from Ceph, if you use the in-cluster objectstore. -
To set the start date for the log collection process, use the
-F
argument and enter the date in theYYYY-MM-DD
format. To set the number of days for which you want to collect logs, calculated from the start date, use the-D
argument and enter the number of days as an integer. For example, to collect logs for the interval between July 20, 2024, and July 24, 2024, runbash support-bundle.sh -F 2024-07-20 -D 5
.To collect logs for a particular date, use the-F
argument to specify the date and the-D
argument to set an interval of one day. For example, to collect logs for July 20, 2024, runbash support-bundle.sh -F 2024-07-20 -D 1
.If you do not set the number of days for which you want to collect logs, the tool uses a default interval of 7 days, calculated from the start date. For example, runningbash support-bundle.sh -F 2024-07-20
collects logs for the interval between July 20, 2024, and July 26, 2024. - We collect logs for almost all the namespaces used in Automation Suite. To collect logs only for particular namespaces, run
bash support-bundle.sh -N uipath,uipath-infra
. Use-N
as list of namespaces for which you want to collect the logs. - The RKE2, uipath, Redis, and Longhorn bundles are generated by default.
- To disable the RKE2 bundle, run the
support-bundle.sh -e
command. - Long-running commands in the RKE bundle are disabled. To enable them, run the
scripts/rke2-support-bundle.sh -a
command. - To disable Redis bundle generation, run the
support-bundle.sh -s
command.
- To disable the RKE2 bundle, run the
- High-level summarized usage telemetry is also exported with this tool generating an XML file. This telemetry includes:
- Robot execution duration per month by robot type.
- Robot concurrency - the maximum number of robots that executed at the same time.
- Metrics on jobs run, processes run, queue items, job failure rate, and users.
- Environment information.
- You can upload the XML file in the Customer Portal to share your high-level self-hosted usage telemetry with the UiPath Support team.
- You can opt out of generating this summarized telemetry by using
-c
in the RKE environments for Automation Suite 2023.10 and lower.
Automation Suite Support Bundle Structure
link.zip
archive contains following files and folders:
File/folder |
Description |
---|---|
|
Contains logs collected from the S3 store. |
|
Contains event descriptions from all the namespaces. |
|
Contains descriptions of all the nodes in the cluster. |
|
Contains descriptions of corresponding objects from all namespaces. |
|
Contains last 4 hour logs from currently running pods. We are collecting this to handle the scenario where Ceph S3 store is down. |
|
Contains high level usage telemetry stored in individual XML files. |
If passed specific namespace list to the command, the structure would look similar to the one shown in the following image:
Exploring Logs
linkAs we are providing a publicly downloadable link to the Automation Suite Support Bundle tool, you can download it on any machine and open it in any editor, such as VS Code, to use it.
support-bundle.sh -F 2023-09-18 -D 30
.