apps
2023.10
true
LEGACY
Legacy Apps User Guide for Automation Suite
Automation CloudAutomation Cloud Public SectorAutomation Suite
Last updated Jan 18, 2024

Apps On-prem Troubleshooting

This section covers troubleshooting procedures applicable for UiPath Apps in the Automation Suite environment, especially during installation or configuration.

Message: UNEXPECTED INCONSISTENCY; RUN Fsck MANUALLY

While installing or upgrading Automation Suite, if the MongoDB pods cannot mount to the PVC pods, the following error message is displayed:

UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY



Recovery Steps

If you encounter the error above, follow the recovery steps below:

  1. SSH to the system by running the following command:

    ssh <user>@<node-ip>ssh <user>@<node-ip>
  2. Check the events of the PVC and verify that the issue is related to the PVC mount failure due to file error. To do this, run the following command:

    export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin:/usr/local/bin
    kubectl get events -n mongodb
    kubectl get events -n longhorn-systemexport KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin:/usr/local/bin
    kubectl get events -n mongodb
    kubectl get events -n longhorn-system
  3. Check the PVC volume mentioned in the event and run the fsck command.
    fsck -a <pvc-volume-name>
    Eg - fsck -a /dev/longhorn/pvc-5abe3c8f-7422-44da-9132-92be5641150afsck -a <pvc-volume-name>
    Eg - fsck -a /dev/longhorn/pvc-5abe3c8f-7422-44da-9132-92be5641150a
  4. Delete the failing MongoDB pod to properly mount it to the PVC.

    kubectl delete pod <pod-name> -n mongodbkubectl delete pod <pod-name> -n mongodb
  • Message: UNEXPECTED INCONSISTENCY; RUN Fsck MANUALLY
  • Recovery Steps

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.