Subscribe

UiPath AI Center

UiPath AI Center

AI Center stand-alone troubleshooting

This section provides troubleshooting information for AI Center in stand-alone environment.

The sections below are specific for AI Center.

How to recreate databases


If there is an issue with your databases, you can recreate them from scratch directly post-installation.
You can do this by running an SQL command to drop all the DBs and recreate them as follows:

USE [master]
ALTER DATABASE [SF_AI_Helper] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [SF_AI_Helper]
ALTER DATABASE [SF_AI_Pkgmanager] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [SF_AI_Pkgmanager]
ALTER DATABASE [SF_AI_Deployer] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [SF_AI_Deployer]
ALTER DATABASE [SF_AI_Trainer] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [SF_AI_Trainer]
ALTER DATABASE [SF_AI_Appmanager] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [SF_AI_Appmanager]
CREATE DATABASE [SF_AI_Helper]
CREATE DATABASE [SF_AI_Pkgmanager]
CREATE DATABASE [SF_AI_Deployer]
CREATE DATABASE [SF_AI_Trainer]
CREATE DATABASE [SF_AI_Appmanager]
GO

Installer cannot connect to ArgoCD to check if password was reset


Description

This issue might occur during fabric installation. The installer might fail with below similar error.

appproject.argoproj.io/fabric created
configmap/argocd-cm configured
[INFO] [2021-09-02T09:21:15+0000]: Checking if ArgoCD password was reset, looking for secrets/argocd-admin-password.
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:21:16+0000]: Secret not found, trying to log in with initial password...1/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:21:36+0000]: Secret not found, trying to log in with initial password...2/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:21:56+0000]: Secret not found, trying to log in with initial password...3/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:22:16+0000]: Secret not found, trying to log in with initial password...4/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:22:36+0000]: Secret not found, trying to log in with initial password...5/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:22:56+0000]: Secret not found, trying to log in with initial password...6/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:23:17+0000]: Secret not found, trying to log in with initial password...7/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:23:37+0000]: Secret not found, trying to log in with initial password...8/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:23:57+0000]: Secret not found, trying to log in with initial password...9/10
FATA[0000] dial tcp: lookup remusr-sf on 168.63.129.16:53: no such host
[INFO] [2021-09-02T09:24:17+0000]: Secret not found, trying to log in with initial password...10/10
[ERROR][2021-09-02T09:24:37+0000]: Failed to log in

Solution 1

Check all the required subdomains and ensure they are configured correctly and are routable as follows:

getent ahosts automationsuite.mycompany.com | awk '{print $1}' | sort | uniq
getent ahosts alm.automationsuite.mycompany.com | awk '{print $1}' | sort | uniq
getent ahosts registry.automationsuite.mycompany.com | awk '{print $1}' | sort | uniq
getent ahosts monitoring.automationsuite.mycompany.com | awk '{print $1}' | sort | uniq
getent ahosts objectstore.automationsuite.mycompany.com | awk '{print $1}' | sort | uniq

🚧

Important!

Replace automationsuite.mycompany.com with you cluster FQDN.

If the above commands/lines do not return a routable IP address, then the subdomain required for AI Center is not configured properly.

📘

Note:

This error is encountered when the DNS is not public.

You need to add the Private DNS Zone (for Azure) or route 53 (for AWS).

If above commands return the proper IP address, then follow the below steps.

Solution 2

  1. Delete the ArgoCD namespace by executing following command:
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml
export PATH=$PATH:/var/lib/rancher/rke2/bin

kubectl delete namespace argocd
  1. Run the following command to verify:
kubectl get namespace

There should not be ArgoCD namespace in the output of this command.

📘

Note:

Once the ArgoCD namespace is deleted, resume with the installation.

Updated about a month ago

AI Center stand-alone troubleshooting


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.