- Getting Started
- Before You Begin
- How To
- Build Your First App
- Build a Mobile-friendly App
- Embed Apps
- Embed Maps
- General User Experience Guidelines
- Hide Containers Using a Button
- Include Excel Charts in Apps
- Include MailTo Links
- Include Star Ratings
- Use Count With Choice Set Values
- Use Document Viewer
- Use Master Detail View
- Use Selected Values From a Table
- Use the Send Interim Result Activity
- Set External Context
- Work With Data Source and Value Bind
- Notifications
- Designing your App
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Values
- Rule: Start Process
- Rule: Upload File to Storage Bucket
- Rule: Get File From Storage Bucket
- Rule: Reset Values
- Rule: Create/Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Function: And, Or, Not
- Function: Concat
- Function: Contains
- Function: Count
- Function: EndsWith
- Function: If
- Function: IsBlank
- Function: Guid
- Function: Length
- Function: List
- Function: StartsWith
- Function: Sum
- Function: Sort
- Function: Now
- Function: Today
- Function: Time
- Function: Year
- Function: Month
- Function: Day
- Function: Hour
- Function: Minute
- Function: New
- Function: Lookup
- Function: Filter
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Application Lifecycle Management (ALM)
- Basic Troubleshooting Guide
- Apps Troubleshooting and FAQs
- Apps On-prem Troubleshooting
Solução de problemas do Apps On-Prem
Esta seção aborda os procedimentos de solução de problemas aplicáveis aos aplicativos UiPath no ambiente Automation Suite , especialmente durante a instalação ou configuração.
Ao instalar ou atualizar o Automation Suite, se os pods do MongoDB não puderem ser montados nos pods de PVC, a seguinte mensagem de erro será exibida:
UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Se você encontrar o erro acima, siga as etapas de recuperação abaixo:
-
Faça SSH para o sistema executando o seguinte comando:
ssh <user>@<node-ip>
ssh <user>@<node-ip> -
Verifique os eventos do PVC e verifique se o problema está relacionado à falha de montagem do PVC devido a erro de arquivo. Para fazer isso, execute o seguinte comando:
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-system
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-system -
Verifique o volume de PVC mencionado no evento e execute o comando
fsck
.fsck -a <pvc-volume-name> Eg - fsck -a /dev/longhorn/pvc-5abe3c8f-7422-44da-9132-92be5641150a
fsck -a <pvc-volume-name> Eg - fsck -a /dev/longhorn/pvc-5abe3c8f-7422-44da-9132-92be5641150a -
Exclua o pod do MongoDB com falha para montá-lo corretamente no PVC.
kubectl delete pod <pod-name> -n mongodb
kubectl delete pod <pod-name> -n mongodb