- 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 bucket
- How to debug failed Automation Suite installations
- How to disable TX 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
- Exploring Logs
Installation best practices
To avoid your SSH session getting interrupted, we recommend initiating a tmux session and then running the installation process in the context of that session. If run under the tmux session, the SSH session can be interrupted, and you can reconnect to the previous session from where the installer was initiated.
Take the following steps:
-
SSH into the remote machine.
-
Install
tmuxon the machine using the following command:sudo yum install tmuxsudo yum install tmux -
Create a
tmuxsession by running the following command.tmux new -s uipath_installtmux new -s uipath_install -
Once inside
tmux, you can start the installation process.-
Commands such as the one below run in the session.
./installUiPathAS.sh sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j server --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /var/tmp --install-offline-prereqs --accept-license-agreement./installUiPathAS.sh sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j server --offline-bundle ./sf-infra.tar.gz --offline-tmp-folder /var/tmp --install-offline-prereqs --accept-license-agreement -
To list all sessions, run the following command:
tmux lstmux ls -
To connect to most recent session, run the following command:
tmux atmux a -
To connect to a session by name, run the following command:
tmux attach -t uipath_installtmux attach -t uipath_install
-
-
To leave or detach from the
tmuxsession, press Ctrl+B and then press D.