When installing Automation Suite version 2024.10.7 on RHEL 8.10,
the following error occurs:
How can I troubleshoot and fix this installation error?
Hi @sunyin007
Could you try with the command below to check/troubleshoot if AS is installed and running.
uipath health check
Regards
Soren
Looking at the screenshot, the main error seems to be:
“You already have an offline installation on the VM.”
So this does not look like a fresh install issue only. So it looks like the installer is detecting an existing or partially completed Automation Suite installation on that machine. Could you please check below points:
Regards,
Dhruba
Hi,@SorenB
Thank you for your reply.
The AS installation has not benn completed yet,and the process failed with an error:
“You already have an offline installation on the VM.”
The below command is not executable.
UiPath health check
Regards,
Dhruba
Hi,@Dhruba_Jyoti_Kalita
Thank you for your reply.
So this does not look like a fresh install issue only. So it looks like the installer is detecting an existing or partially completed Automation Suite installation on that machine.
This is a machine with a fresh RHEL installation,and error occurred during the AS installation process.
The below command is not executable.
- Run:
UiPath health check - Chekc whether Automation Suite is already installed or partially running3. 4.
- Review the previous install log mentioned in the error,
- Confirm whether this VM already has a partial / existing AS setup
This is a brand-new,clean physcial host(not a VM),and AS has never been installed on it before.
Regards,
Sun
Thanks for the clarification. Even on a fresh RHEL machine, if the Automation Suite installer fails during the first attempt, it can still create some partial rke2 or installer state. When you run the installer again, it detects that state and throws the “offline installation already exists” error.
Before deleting, you can quickly confirm they exist:
ls /opt/UiPathAutomationSuite
ls /var/lib/rancher
if they exist, it confirms the installer already created partial state, which explains the error.
In that case, you may need to clean the partial installation before retrying. You can try the following:
sudo systemctl stop rke2-server
sudo systemctl stop rke2-agent
sudo rm -rf /opt/UiPathAutomationSuite
sudo rm -rf /etc/rancher/rke2
sudo rm -rf /var/lib/rancher/rke2
sudo rm -rf /var/lib/kubelet
sudo rm -rf /var/lib/rook
@Dhruba_Jyoti_Kalita
Thanks for the solution!
I followed the steps you provided, but now I’m hitting this new error.
Could you help me figure out how to fix it?
(Is it a network issue, or a problem with the installation steps?)
Regards
@sunyin007 It looks like the previous issue is resolved and now the installation is failing at rook-ceph-object-store. Can you run below:
kubectl -n UiPath get pods
kubectl -n UiPath logs
Please share me the results
@Dhruba_Jyoti_Kalita
Thank you for you reply.
kubectl -n UiPath get pods
kubectl -n UiPath logs
Here are the run results(The logs of the other 4 errored pods are similar),got any ideas?
Hi @SorenB
Hi @Dhruba_Jyoti_Kalita
I reinstalled it a few days ago, and here are the results from running command as below:
UiPath health check
Any solutions?
Regards
Hi @sunyin007
Are you able to access the ArgoCD webinterface?
Here you should be able to see the status of the applications.
Regards
Soren
Hi @SorenB
We can access the ArgoCD web UI, and it shows an error with the OC application there.
Got any ideas?
Regards
Hi @SorenB
Hi @Dhruba_Jyoti_Kalita
The issue with the OC application has been fixed, but we’re now encountering the following problems with the webhook application.
Could you help us resolve this?