HEART software.crash-loop H-06003
Crash loop. A component keeps crashing and restarting.
| Code | HEART software.crash-loop; inside a message "code": "software.crash-loop" |
|---|---|
| H-number | H-06003: area 06, code 003 |
| Area | software: Crashes, versions, updates, settings |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Every product with software |
Likely causes
- A fault a restart cannot fix: bad settings, damaged data, a missing file.
- A broken update.
- A part it needs at start-up is missing or down.
How to fix or prevent it
- Stop restarting it: read the logs of the first crash.
- Roll back the last update or setting change.
- Check the files and services it needs at start-up.
What the HEART does by itself
It stops restarting the component on its own, raises an error alert, and escalates to a person. This is what a failed restart Playbook leaves behind. It resolves when the component runs steadily again.
When to call service
If rolling back does not stop it.
Related codes
software.crashedH-06002: Crashedsoftware.update-failedH-06004: Update failedsoftware.config-invalidH-06005: Settings invalid
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)