Werk #20139: Crash reports view with broken traceback
| Component | User interface | ||||||
| Title | Crash reports view with broken traceback | ||||||
| Date | Jul 29, 2026 | ||||||
| Level | Trivial Change | ||||||
| Class | Bug Fix | ||||||
| Compatibility | Compatible - no manual interaction needed | ||||||
| Checkmk versions & editions |
|
Previously, opening Monitor > System > Crash reports could fail entirely with:
Internal error: too many values to unpack (expected 4)
This happened when a single stored crash report contained a traceback Checkmk could not interpret, for example one recorded as plain text rather than as individual code locations. One such report made the whole list inaccessible.
The list now renders. Reports with an uninterpretable traceback are still shown; only their Crash source column can no longer tell whether an extension was involved. No currently supported Checkmk version writes reports like this, so this is a safeguard for reports left behind by other producers.