• ceph crash归档排查


    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:

    ceph mgr module enable crash
    

    Commands

    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.

    ceph crash rm <crashid>
    

    Remove a specific crash dump.

    ceph crash ls
    

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

    ceph crash ls-new
    

    List the timestamp/uuid crashids for all newcrash info.

    ceph crash stat
    

    Show a summary of saved crash info grouped by age.

    ceph crash info <crashid>
    

    Show all details of a saved crash.

    ceph crash prune <keep>
    

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

    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).

    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.

  • 相关阅读:
    Meteor + node-imap(nodejs) + mailparser(nodejs) 实现完整收发邮件
    详解log4j2(上)
    循序渐进之Spring AOP(6)
    循序渐进之Spring AOP(5)
    循序渐进之Spring AOP(3)
    循序渐进之Spring AOP(4)
    循序渐进之Spring AOP(2)
    循序渐进之Spring AOP(1)
    通俗的解释JAVA wait/notify机制
    开发高性能JAVA应用程序基础(内存篇)
  • 原文地址:https://www.cnblogs.com/weifeng1463/p/13747475.html
Copyright © 2020-2023  润新知