> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cyberup24.com/llms.txt
> Use this file to discover all available pages before exploring further.

# System Status

The LARK runs all of its services as managed workloads on the appliance. As an administrator, you have access to a system status view in the admin interface that gives you a real-time overview of every service on the appliance. Checking this view regularly — especially after power-on or a configuration change — helps you catch problems early and confirm that the platform is ready for analyst use.

<Tip>
  Make it a habit to check system status every time the LARK is powered on. Services take a few minutes to start after boot, so wait two to three minutes before reviewing status to avoid false alarms. If any service is still not running after five minutes, begin investigating.
</Tip>

## Accessing the System Status View

1. Log in to the LARK admin interface using your administrator credentials.
2. Select **System Status** from the main navigation menu.
3. The status dashboard loads a live view of all services, grouped by application.

You can refresh the view manually at any time, or enable auto-refresh for continuous monitoring.

## What Healthy Status Looks Like

A fully healthy LARK will show all services in the **Running** state with their readiness checks passing. In the status view, healthy indicators include:

<CardGroup cols={2}>
  <Card title="Running" icon="circle-check">
    The service has started successfully, passed its readiness check, and is actively serving requests. This is the expected state for all services during normal operation.
  </Card>

  <Card title="Completed" icon="flag-checkered">
    Seen on short-lived task services that ran a one-time job and exited cleanly. This is normal and does not require action.
  </Card>
</CardGroup>

When all services show **Running** and no warnings appear on the dashboard, the appliance is in a healthy state and ready for use.

## Recognising Unhealthy States

If a service is not functioning correctly, it will appear in one of the following states:

| State                | Meaning                                                                        | Typical Cause                                                                |
| -------------------- | ------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
| **Pending**          | The service has been scheduled but has not started yet.                        | Insufficient resources; the appliance may be overloaded or still booting.    |
| **CrashLoopBackOff** | The service started but crashed repeatedly and is being retried automatically. | Application error, misconfiguration, or missing dependency.                  |
| **Error**            | The service exited with an error code.                                         | Application crash or failed startup.                                         |
| **ImagePullBackOff** | The appliance cannot load the service's software package.                      | Storage issue or corrupted package in the local registry.                    |
| **Terminating**      | The service is being shut down.                                                | Normal after disabling an application; abnormal if it persists indefinitely. |

A small number of **Pending** services immediately after power-on is normal. Any **CrashLoopBackOff**, **Error**, or **ImagePullBackOff** state that persists beyond a few minutes warrants investigation.

## When to Act vs. When to Wait

Not every non-Running status requires immediate action. Use the following guidance:

* **After power-on:** Allow two to three minutes for all services to initialise. Services will cycle through **Pending** and brief intermediate states before reaching **Running**. This is expected behaviour.
* **After enabling a new application:** Allow one to two minutes for the new service to reach **Running**. If it remains **Pending** or enters **CrashLoopBackOff**, check the appliance's available resources.
* **Persistent CrashLoopBackOff or Error:** If a service has been in a failed state for more than five minutes without recovering, the issue is unlikely to self-resolve. Begin troubleshooting.
* **Persistent Terminating:** A service stuck in **Terminating** for more than a few minutes may indicate a deeper platform issue and should be investigated promptly.

## System Status and Troubleshooting

The system status view is your first stop when something on the LARK is not working as expected. Identifying which service is unhealthy narrows down where to look next. From the status view, you can select any service to inspect its recent log output, which often contains the error message needed to diagnose the problem.

For a structured approach to investigating problems, see the [Troubleshooting Approach](/troubleshooting/troubleshooting-approach) page. For guidance on resolving specific service failure states, refer to the [Service Errors](/troubleshooting/pod-errors) troubleshooting page.