> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/holoplot-control/maintaining-the-system/device-issues-list.md).
# Issue Tracker reference
This reference lists issue names that can appear in the **Issue Tracker**. Issues describe a device's current condition. They clear when the underlying condition recovers.
Use [Monitoring device health](/holoplot-control/maintaining-the-system/monitoring-device-health.md) to find and inspect active issues. Use the [Event Log](/holoplot-control/maintaining-the-system/device-events-list.md) for recorded changes over time.
### Controller issues
Controller - All issues
{% hint style="info" %}
Network role issues indicate that a required network role is unfulfilled. See [Networking overview](/user-guides/holoplot-system-deployment/networking-overview.md#network-roles) for each role and its traffic.
{% endhint %}
| Issue Name | Description |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| PSU - Error | Power supply unit error |
| Drive - Error | Storage drive error |
| Fans - Error | Cooling fans error |
| Network - Link Down | Network connection is down |
| Network - No IP | Network interface has no IP address |
| Network - No Mac | Network interface has no MAC address |
| Network - Low Speed | Network is operating at lower than expected speed |
| NTP - Not Synchronized | Time synchronization issue |
| No Internet | No internet connectivity. Corresponds to the **Disconnected from internet** event in the Event Logger |
| No HOLOPLOT VPN | No connection to the HOLOPLOT VPN. The VPN uses a WireGuard® tunnel to connect to the HOLOPLOT cloud. This issue appears as the 'Disconnected from Wireguard®' event in the Event Logger, prior to OS2.6.3.
From OS2.6.3 onwards, this problem no longer impacts the system's health calculations and will be removed from the Issue list.
|
| Network Role - Audio Module Control Network Primary | Primary audio module control network role unfulfilled |
| Network Role - Audio Module Control Network Secondary | Secondary audio module control network role unfulfilled |
| Network Role - Audio Network Primary | Primary audio network role unfulfilled |
| Network Role - Audio Network Secondary | Secondary audio network role unfulfilled |
| Network Role - Intercontroller Network | Intercontroller network role unfulfilled |
| Network Role - HOLOPLOT Control Network Primary | Primary control network role unfulfilled |
| Network Role - HOLOPLOT Control Network Secondary | Secondary control network role unfulfilled |
***
### Module issues
Module - Hardware issues
#### Amplifier issues
| Issue Name | Description |
| -------------------------- | -------------------------------------------------------- |
| AMP - Debricking | Amplifier is in recovery mode |
| AMP - Error | General amplifier error |
| AMP - High Temperature | Amplifier temperature is high but within operating range |
| AMP - Initializing | Amplifier is starting up |
| AMP - Over Temperature | Amplifier temperature exceeds safe operating range |
| AMP - Power Cycle Required | Amplifier needs to be power cycled |
| AMP - Power Cycling | Amplifier is in power cycling process |
| AMP - Unknown | Amplifier status cannot be determined |
| AMP - Unrecognized | Amplifier returned an unrecognized status |
| AMP - Updating | Amplifier firmware is updating |
#### Driver issues
| Issue Name | Description |
| ------------------------ | ---------------------------------------------- |
| Driver - Above Tolerance | Driver parameter exceeds acceptable tolerance |
| Driver - Below Tolerance | Driver parameter is below acceptable tolerance |
| Driver - Unknown | Driver status cannot be determined |
#### General hardware issues
| Issue Name | Description |
| ---------------------------- | -------------------------- |
| Hardware - Critical | Critical hardware problem |
| Hardware - Error | General hardware error |
| Hardware - Unspecified Issue | Unspecified hardware issue |
| Hardware - Warning | Hardware warning condition |
#### Power supply issues
| Issue Name | Description |
| -------------------------- | ----------------------------------------------------------- |
| PSU - Error | General power supply error |
| PSU - High Temperature | Power supply temperature is high but within operating range |
| PSU - Initializing | Power supply is initializing |
| PSU - Over Temperature | Power supply temperature exceeds safe operating range |
| PSU - Power Cycle Required | Power supply needs to be power cycled |
| PSU - Power Cycling | Power supply is in power cycling process |
| PSU - Unknown | Power supply status is unknown |
| PSU - Unrecognized | Unrecognized power supply status |
| PSU - Updating | Power supply firmware is updating |
#### Sublink issues
| Issue Name | Description |
| -------------------------------- | ---------------------------------------------- |
| Sublinks - Both Connection Lost | Both sublinks have lost connection |
| Sublinks - Both Error | Both sublinks have errors |
| Sublinks - Both High Temperature | Both sublinks have high temperature |
| Sublinks - Both Initializing | Both sublinks are initializing |
| Sublinks - Both Not Connected | Both sublinks are not connected |
| Sublinks - Both Over Temperature | Both sublinks have exceeded temperature limits |
| Sublinks - Both Unknown | Status of both sublinks is unknown |
| Sublinks - Both Updating | Both sublinks are updating |
| Sublinks - Both Ok | Both sublinks are functioning properly |
Module - Network issues
#### Network issues
| Issue Name | Description |
| ------------------------------ | ---------------------------------------------- |
| Network - Group On Same Subnet | Multiple network groups on the same subnet |
| Network - Low Speed | Network operating at lower than expected speed |
| Network - No IP | Network interface has no IP address |
| Network - No MAC | Network interface has no MAC address |
| Network - Link Down | Network connection is down |
#### PTP (Precision Time Protocol) issues
| Issue Name | Description |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| PTP - Disabled | Port administratively/operationally off; no PTP messages at all. → INITIALIZING when re-enabled. |
| PTP - Faulty | Fault detected (implementation-specific); no normal PTP activity until cleared. → INITIALIZING. |
| PTP - Initializing | PTP is initializing. Startup state; port initializes hardware/data sets, doesn't send/receive PTP traffic yet. |
| PTP - Leader Has No MAC | PTP leader has no MAC address. It needs investigation when PTP is expected. |
| PTP - Listening | No qualified foreign leader yet (just started, or timeout expired). Watching for Announce messages; no Sync/Delay exchange. |
| PTP - Pre-Leader | PTP is in pre-leader state |
| PTP - Uncalibrated | Transitional; port has picked a leader and is running the delay/offset exchange, but the server hasn't converged yet. |
| PTP - Unknown | PTP status is unknown. It needs investigation when PTP is expected. |
| PTP - Unrecognized | Unrecognized PTP state |
| PTP - Not Synced | PTP is not synchronized. It needs immediate investigation. Audio playback may be compromised. |
{% hint style="info" %}
**Interpreting PTP issues.** The Issue Tracker reports unhealthy PTP conditions. It does not report normal interface roles such as **Follower** or **Passive**.
**Initializing**, **Listening**, and **Uncalibrated** can occur during startup. Investigate them if they persist. **Not Synced** needs immediate investigation because audio playback may be compromised. Investigate **Disabled**, **Faulty**, **Unknown**, and **Leader Has No MAC** whenever PTP is expected on the Audio Network.
See the [PTP events reference](/holoplot-control/maintaining-the-system/device-events-list.md) for complete PTP interface-state definitions.
{% endhint %}
### Processor issues
Processor - Software & Hardware issues
#### Software issues
| Issue name | Description |
| -------------------- | ----------------------------------------------------- |
| DSP - Waiting | Processor is waiting for the DSP configuration |
| DSP - Stopped | Processor DSP is not running |
| DSP - Unknown | Processor DSP is in an unknown state. |
| Sync - Error | Issue reported with the project sync to the Processor |
| Audio Engine - Error | Issue with the Hardware Audio Interface |
#### Hardware issues
| Issue Name | Description |
| ------------------ | ----------------------- |
| PSU - Error | Power supply unit error |
| Drive - Error | Storage drive error |
| Fans - Error | Cooling fans error |
| CPU - High Usage | CPU usage ≥ 70%, ≤90% |
| CPU - Severe Usage | CPU usage >90% |
| CPU - Unknown | Unknown CPU usage |
Processor - Network issues
{% hint style="info" %}
Network role issues indicate that a required network role is unfulfilled. See [Networking overview](/user-guides/holoplot-system-deployment/networking-overview.md#network-roles) for each role and its traffic.
{% endhint %}
| Issue Name | Description |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Network - Link Down | Network connection is down |
| Network - No IP | Network interface has no IP address |
| Network - No Mac | Network interface has no MAC address |
| Network - Low Speed | Network is operating at lower than expected speed |
| NTP - Not Synchronized | Time synchronization issue |
| No Internet | No internet connectivity. Corresponds to the **Disconnected from internet** event in the Event Logger |
| No HOLOPLOT VPN | No connection to the HOLOPLOT VPN. The VPN is a WireGuard® tunnel to the HOLOPLOT cloud, so this corresponds to the **Disconnected from Wireguard®** event in the Event Logger |
| Network Role - Audio Module Control Network Primary | Primary audio module control network role unfulfilled |
| Network Role - Audio Module Control Network Secondary | Secondary audio module control network role unfulfilled |
| Network Role - Audio Network Primary | Primary audio network role unfulfilled |
| Network Role - Audio Network Secondary | Secondary audio network role unfulfilled |
| Network Role - Intercontroller Network | Intercontroller network role unfulfilled |
| Network Role - HOLOPLOT Control Network Primary | Primary control network role unfulfilled |
| Network Role - HOLOPLOT Control Network Secondary | Secondary control network role unfulfilled |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.holoplot.com/holoplot-control/maintaining-the-system/device-issues-list.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.