ba0aa24316
Add ssh dump support changes including below items: 1. sshkey option 2. sshkey propagate 3. fix a bug of _server ip calculation for dump target string 4. change the prefix of kdump hook from 93 to 01 to avoid dhclient and other cleanups happening before us 5. enable network with dracut cmdline rd.neednet=1 when there's network target config [v1 - v2]: Only check_ssh_target when there's ssh dump target in kdump config file [v2 -> v3] style fixes: trailing spaces and space before tab indent remove set -x simply check_ssh_target use awk to get sshkey option value change pivot hook order to 0000 Signed-off-by: Dave Young <dyoung@redhat.com>
115 lines
4.6 KiB
Plaintext
115 lines
4.6 KiB
Plaintext
# Configures where to put the kdump /proc/vmcore files
|
|
#
|
|
# This file contains a series of commands to perform (in order) when a
|
|
# kernel crash has happened and the kdump kernel has been loaded. Directives in
|
|
# this file are only applicable to the kdump initramfs, and have no effect if
|
|
# the root filesystem is mounted and the normal init scripts are processed
|
|
#
|
|
# Currently only one dump target and path may be configured at once
|
|
# if the configured dump target fails, the default action will be preformed
|
|
# the default action may be configured with the default directive below. If the
|
|
# configured dump target succedes
|
|
#
|
|
# Basics commands supported are:
|
|
# raw <partition> - Will dd /proc/vmcore into <partition>.
|
|
#
|
|
# net <nfs mount> - Will mount fs and copy /proc/vmcore to
|
|
# <mnt>/var/crash/%HOST-%DATE/, supports DNS.
|
|
#
|
|
# net <user@server> - Will scp /proc/vmcore to
|
|
# <user@server>:/var/crash/%HOST-%DATE/, supports DNS
|
|
# NOTE: make sure user has necessary write
|
|
# permissions on server
|
|
#
|
|
# <fs type> <partition> - Will mount -t <fs type> <partition> /mnt and copy
|
|
# /proc/vmcore to /mnt/var/crash/%DATE/.
|
|
# NOTE: <partition> can be a device node, label or uuid.
|
|
#
|
|
# path <path> - Append path to the filesystem device which you are
|
|
# dumping to. Ignored for raw device dumps.
|
|
# If unset, will default to /var/crash.
|
|
#
|
|
# core_collector makedumpfile <options>
|
|
# - This directive allows you to use the dump filtering
|
|
# program makedumpfile to retrieve your core, which on
|
|
# some arches can drastically reduce core file size.
|
|
# See /sbin/makedumpfile --help for a list of options.
|
|
# Note that the -i and -g options are not needed here,
|
|
# as the initrd will automatically be populated with
|
|
# a config file appropriate for the running kernel.
|
|
#
|
|
# link_delay <seconds>
|
|
# - Some network cards take a long time to initialize, and
|
|
# some spanning tree enabled networks do not transmit
|
|
# user traffic for long periods after a link state
|
|
# changes. This optional parameter defines a wait
|
|
# period after a link is activated in which the
|
|
# initramfs will wait before attempting to transmit
|
|
# user data.
|
|
#
|
|
# kdump_post <binary | script>
|
|
# - This directive allows you to run a specified
|
|
# executable just after the memory dump process
|
|
# terminates. The exit status from the dump process
|
|
# is fed to the kdump_post executable, which can be
|
|
# used to trigger different actions for success or
|
|
# failure.
|
|
#
|
|
# kdump_pre <binary | script>
|
|
# - works just like the kdump_post directive, but instead
|
|
# of running after the dump process, runs immediately
|
|
# before. Exit status of this binary is interpreted
|
|
# as follows:
|
|
# 0 - continue with dump process as usual
|
|
# non 0 - reboot/halt the system
|
|
#
|
|
# extra_bins <binaries | shell scripts>
|
|
# - This directive allows you to specify additional
|
|
# binaries or shell scripts you'd like to include in
|
|
# your kdump initrd. Generally only useful in
|
|
# conjunction with a kdump_post binary or script that
|
|
# relies on other binaries or scripts.
|
|
#
|
|
# extra_modules <module(s)>
|
|
# - This directive allows you to specify extra kernel
|
|
# modules that you want to be loaded in the kdump
|
|
# initrd, typically used to set up access to
|
|
# non-boot-path dump targets that might otherwise
|
|
# not be accessible in the kdump environment. Multiple
|
|
# modules can be listed, separated by a space, and any
|
|
# dependent modules will automatically be included.
|
|
#
|
|
# default <reboot | halt | poweroff | shell>
|
|
# - Action to preform instead of mounting root fs and
|
|
# running init process
|
|
# reboot: If the default action is reboot simply reboot
|
|
# the system and loose the core that you are
|
|
# trying to retrieve.
|
|
# halt: If the default action is halt, then simply
|
|
# halt the system after attempting to capture
|
|
# a vmcore, regardless of success or failure.
|
|
# poweroff: The system will be powered down
|
|
# shell: If the default action is shell, then drop to
|
|
# an msh session inside the initramfs from
|
|
# where you can try to record the core manually.
|
|
# Exiting this shell reboots the system.
|
|
# NOTE: If no default action is specified, the initramfs
|
|
# will mount the root file system and run init.
|
|
|
|
#raw /dev/sda5
|
|
#ext4 /dev/sda3
|
|
#ext4 LABEL=/boot
|
|
#ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
|
|
#net my.server.com:/export/tmp
|
|
#net user@my.server.com
|
|
#sshkey /root/.ssh/kdump_id_rsa
|
|
#path /var/crash
|
|
#core_collector makedumpfile -c
|
|
#link_delay 60
|
|
#kdump_post /var/crash/scripts/kdump-post.sh
|
|
#extra_bins /usr/bin/lftp
|
|
#disk_timeout 30
|
|
#extra_modules gfs2
|
|
#default shell
|
|
|