"System error" in LarePass
Use this guide when the System section in LarePass displays "System error". There can be multiple underlying causes for this message, so follow the steps below to collect diagnostic information first, and then contact the Olares team with the results. 
Condition
- The System section in LarePass shows "System error".
- Your Olares device is accessible, but LarePass cannot retrieve system status.
Cause
The "System error" message can be triggered by different underlying issues. A common cause is that one or more system pods on the Olares device are not running normally. When this happens, LarePass cannot retrieve system status and displays "System error".
Solution
Use the built-in terminal to locate any failing pods, retrieve their error messages, and then share this information with the Olares team. This helps narrow down the possible causes and speeds up troubleshooting.
Step 1: Identify the failing pod
Check the status of system pods and identify any pods that are not running.
Open a browser and access your Olares system at
https://desktop.<your-olaresID>.olares.com.Open Control Hub. In the left sidebar, under the Terminal section, click Olares.

Run the following command to get the status of all pods across all namespaces:
bashkubectl get pods -ACheck the STATUS column and locate any pods that are not in the
Runningstate. Note down the exact NAMESPACE (the first column) and NAME (the second column) of the problematic pod.
Step 2: Inspect the pod error
View the detailed error message for the problematic pod.
Run the following command, replacing
<namespace>and<pod-name>with the values you noted in the previous step:bashkubectl describe pod <pod-name> -n <namespace>In this example:
bashkubectl describe pod backup-66f8c76996-d7vnq -n os-frameworkScroll down to the Events section in the output to identify the error message related to the failure.

Step 3: Contact support
Create an issue in the Olares GitHub repository and provide the following information:
- The output of
kubectl describe pod <pod-name> -n <namespace>. - A screenshot of the error message, if available.
This information helps our team investigate and resolve the issue faster.