Automation Suite
2021.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- 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 Disable TLS 1.0 and 1.1
- 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 debug failed Automation Suite installations
- How to disable NIC checksum offloading
- 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
- SQL connection string validation error
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- 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).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- 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
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Using the Automation Suite Support Bundle Tool
Automation Suite Installation Guide
Last updated Apr 19, 2024
Using the Automation Suite Support Bundle Tool
Download the
supportability-tools
zip and extract its contents using the following commands:
curl "https://download.uipath.com/automation-suite/2021.10.6/supportability-tools-2021.10.6.zip" -o supportability-tools-2021.10.6.zip
unzip supportability-tools-2021.10.6.zip -d support-tools
curl "https://download.uipath.com/automation-suite/2021.10.6/supportability-tools-2021.10.6.zip" -o supportability-tools-2021.10.6.zip
unzip supportability-tools-2021.10.6.zip -d support-tools
You can generate the support bundle from the
support-tools/support-bundle/
folder using the bash support-bundle.sh
command. You can run the command from anywhere you have set the proper kubeconfig context to the cluster.
Note: In Azure, make sure your IP is added to the Network Security Group.
The following image shows a typical output for this command:
- Running only
bash support-bundle.sh
collects logs from the S3 store of the past 7 days. - If you want to collect logs from a particular date, run
bash support-bundle.sh -F 2021-06-22 -D 1
- use
-F
as date in YYYY-MM-DD format - use
-D
as number of days for which you want to collect the logs from the start date in -F (default value is 7 days).
- use
- Currently we are collecting logs for almost all the namespaces used in Automation Suite. If you want to collect logs for only
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.
- use
- If you want to generate the support bundle for MongoDB, use
-m
at the end of the command (bash support-bundle.sh -m
). This command generates a.tgz
compressed file namedmongo_support_bundle_<current_timestamp>.tgz
under the same folder where the bash command is run. Attach this file and send it to UiPath Support Team.
The
.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. |
If passed specific namespace list to the command, the structure would look similar to the one shown in the following image: