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
How to debug failed Automation Suite installations
Automation Suite Installation Guide
Last updated Apr 19, 2024
How to debug failed Automation Suite installations
If the Automation Suite installation fails while running the
installUiPathAS.sh
or install-uipath.sh
installers, take the following steps to debug it:
- Check if the nodes are active.
- For server nodes, run
sudo systemctl status rke2-server
. - For agent nodes, run
sudo systemctl status rke2-agent
.- If the nodes are active, but the installation failed, use the diagnostic tool to troubleshoot.
- If a node is inactive, check the installation logs for any errors.
- For server nodes, run
-
Capture basic installation logs.
The installer prints the installation log location when usinginstallUiPathAS.sh
. Forinstall-uipath.sh
, logs are stored in the directory from where the installation command was executed.If the installation logs do not reveal the issue, run the installers in debug mode for more details. For both online and offline installations, runinstall-uipath.sh -d
. The-d
flag runs the installer in debug mode.Troubleshooting can also be done based on the logs available in ArgoCD, Istio, or on the machine itself. For more details, see Exploring logs.
-
Capture all installation logs.
To capture all logs related to the Automation Suite installation, download the
rke2logCollector.sh
script from GitHub and run it under the root account.The script collects the following data:
- system info
- network info
- docker info
- k3s info
- rke2 info
- rancher logs
- k8s component logs
- system pod logs
- nginx-proxy info
- k3s cluster logs
- system pod logs
- rke2 cluster logs
- rke2 system pod logs
- rke2 agent/server logs
- system logs from /var/log
- system logs from journald
- k8s directory state
- k8s certificates
- k3s directory state
- k3s certificates
- k3s server certificates
- rke2 directory state
- rke2 certificates
- rke2 server certificates
- rke etcd info
- etcdctl output
- rke2 etcd info