HEART software.crashed H-06002
Crashed. A program or component crashed.
| Code | HEART software.crashed; inside a message "code": "software.crashed" |
|---|---|
| H-number | H-06002: area 06, code 002 |
| Area | software: Crashes, versions, updates, settings |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every product with software |
Likely causes
- A bug met an unusual input.
- Memory ran out.
- A worker hung and stopped answering.
- A library or driver failed.
How to fix or prevent it
- Restart the component.
- Check memory, and the logs just before the crash.
- Update the software if a fix exists.
What the HEART does by itself
It raises a warning, and a Playbook may restart the component (restart_component) within its limits, such as six a day and 60 s apart. If it crashes again soon after, the alert becomes software.crash-loop and goes to a person. It resolves when the component answers again.
When to call service
If it crashes more than once a day.
Related codes
software.crash-loopH-06003: Crash loopperformance.memory-exhaustedH-05004: Memory exhaustedsystem.unexpected-restartH-01004: Unexpected restart
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)