Skip to content
This repository has been archived by the owner on May 11, 2020. It is now read-only.

Latest commit

 

History

History
75 lines (55 loc) · 2.68 KB

README.md

File metadata and controls

75 lines (55 loc) · 2.68 KB
Raw

This Role Has Been Deprecated: Please use the version in the oasis_roles.system Ansible Collection

Build Status

KDUMP

Role to setup Kernel dump files

Requirements

Ansible 2.4 or higher

Red Hat Enterprise Linux 7 or equivalent

Valid Red Hat Subscriptions

Role Variables

Currently the following variables are supported:

General

  • kdump_conf_path - the path to the remote host's kernel dump config file
  • kdump_become_user - the user to run tasks as on the remote host
  • kdump_crash_path - the path in which to store kernel crash dump files
  • kdump_core_collector_args - parameters/options to pass into the core collector configuration (not configured by default)
  • kdump_dracut_device - the location of a device to mount onto a specified mountpoint (not configured by default)
  • kdump_dracut_mountpoint - the location a specified device is to be mounted (not configured by default)
  • kdump_dracut_filesystem_type - the type of filesystem of the device in its initramfs (not configured by default)
  • kdump_dracut_filesystem_options - configuration options for the filesystem (not configured by default)

Dependencies

If your system has too little memory for auto-provisioning crash memory, you might need to configure a static amount of memory for the crash kernel tool on the bootloader commandline. Generally this is only a problem on systems with less than 1GB of memory. If this is an issue, you can search for directions on editing the boot line of your system.

On a RHEL or CentOS system you would change this value by editing the /etc/defaults/grub file and changing the value crashkernel=auto to crashkernel=32M or whatever value you want. You will then need to regenerate your grub2.cfg file using the grub2-mkconfig file. On a traditional system this is a command like grub2-mkconfig -o /boot/grub2/grub.cfg. If your system uses EFI, the path will live under /boot/efi/EFI. Consult your operating system documentation for appropriate directions on how to do this and for the appropriate amount of physical RAM to reserve for this purpose.

Example Playbook

- hosts: setup_kdump-servers
  roles:
    - role: oasis_roles.kdump
      kdump_conf_path: /etc/kdump.conf
      kdump_become_user: root
      kdump_crash_path: /var/crash
      kdump_core_collector_args: makedumpfile -l --message-level 1 -d 31
      kdump_dracut_mountpoint: /mnt/vmcore

License

GPLv3

Author Information

Andrew Euredjian [email protected]