Crash Module

The crash module collects information about daemon crashdumps and stores it in the Ceph cluster for later analysis.

Daemon crashdumps are dumped in /var/lib/ceph/crash by default; this can be configured with the option ‘crash dir’. Crash directories are named by time and date and a randomly-generated UUID, and contain a metadata file ‘meta’ and a recent log file, with a “crash_id” that is the same. This module allows the metadata about those dumps to be persisted in the monitors’ storage.

Enabling

The crash module is enabled with:

  1. ceph mgr module enable crash

Commands

  1. ceph crash post -i <metafile>

Save a crash dump. The metadata file is a JSON blob stored in the crash dir as meta. As usual, the ceph command can be invoked with -i -, and will read from stdin.

  1. ceph crash rm <crashid>

Remove a specific crash dump.

  1. ceph crash ls

List the timestamp/uuid crashids for all new and archived crash info.

  1. ceph crash ls-new

List the timestamp/uuid crashids for all newcrash info.

  1. ceph crash stat

Show a summary of saved crash info grouped by age.

  1. ceph crash info <crashid>

Show all details of a saved crash.

  1. ceph crash prune <keep>

Remove saved crashes older than ‘keep’ days. <keep> must be an integer.

  1. ceph crash archive <crashid>

Archive a crash report so that it is no longer considered for the RECENT_CRASH health check and does not appear in the crash ls-new output (it will still appear in the crash ls output).

  1. ceph crash archive-all

Archive all new crash reports.

Options

  • mgr/crash/warn_recent_interval [default: 2 weeks] controls what constitutes “recent” for the purposes of raising the RECENT_CRASH health warning.

  • mgr/crash/retain_interval [default: 1 year] controls how long crash reports are retained by the cluster before they are automatically purged.