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:

1. Check if the nodes are active.
   1. For server nodes, run sudo systemctl status rke2-server.
   2. For agent nodes, run sudo systemctl status rke2-agent.
      1. If the nodes are active, but the installation failed, use the diagnostic tool to troubleshoot.
      2. If a node is inactive, check the installation logs for any errors.

2. Capture basic installation logs.

   The installer prints the installation log location when using installUiPathAS.sh. For install-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, run install-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.

3. 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