7e10236038
This patch updates kexec-tools from 2.0.15 to 2.0.21 (and its supporting software package makedumpfile from 1.6.2 to 1.6.9) for compatibility with the newer v5.10 kernel. This commit clones the kexec-tools package's supporting files from commit 26a7a543427eac59ed39728466f3d95d320f735a in the CentOS RPM packaging git repository. Links for reference: -26a7a54342-26a7a54342Please note that this patch causes the build system to pull in and extract an SRPM file to acquire: kdump-anaconda-addon-003-29-g4c517c5.tar.gz This is done for security, because the only public reference to commit 4c517c5 is on a Red Hat developer's personal Github account: https://github.com/ryncsn/kdump-anaconda-addon/commits/rhel-7 kexec-tools package's supporting files cloned by this commit trigger a large number of shell script linting errors. Given that the shell scripts in question are inherited from upstream (i.e., CentOS 7), the "files" directory of this package is excluded from automated linting via the changes in tox.ini. Verification: A kexec-tools RPM package built with this commit was installed onto an existing StarlingX system. A vmcore file was succesfully collected from a kernel crash triggered with /proc/sysrq-trigger. A recent version of the crash utility was found to succesfully parse the collected vmcore file. Credits: Thanks to Jiping Ma for helping with cleaning up and publishing an earlier version of this patch. Story: 2008921 Task: 43040 Depends-On: https://review.opendev.org/c/starlingx/tools/+/805127 Signed-off-by: Jiping Ma <jiping.ma2@windriver.com> Signed-off-by: M. Vefa Bicakci <vefa.bicakci@windriver.com> Change-Id: Idc4e523610e4c09259300c8b67ea5e0fbe59c611
164 lines
7.1 KiB
Plaintext
164 lines
7.1 KiB
Plaintext
# This file contains a series of commands to perform (in order) in the kdump
|
|
# kernel after a kernel crash in the crash kernel(1st kernel) has happened.
|
|
#
|
|
# Directives in this file are only applicable to the kdump initramfs, and have
|
|
# no effect once the root filesystem is mounted and the normal init scripts are
|
|
# processed.
|
|
#
|
|
# Currently, only one dump target and path can be specified. If the dumping to
|
|
# the configured target fails, the default action which can be configured via
|
|
# the "default" directive will be performed.
|
|
#
|
|
# Supported options:
|
|
#
|
|
# raw <partition>
|
|
# - Will dd /proc/vmcore into <partition>.
|
|
# Use persistent device names for partition devices,
|
|
# such as /dev/vg/<devname>.
|
|
#
|
|
# nfs <nfs mount>
|
|
# - Will mount nfs to <mnt>, and copy /proc/vmcore to
|
|
# <mnt>/<path>/%HOST-%DATE/, supports DNS.
|
|
#
|
|
# ssh <user@server>
|
|
# - Will scp /proc/vmcore to <user@server>:<path>/%HOST-%DATE/,
|
|
# supports DNS.
|
|
# NOTE: make sure the user has write permissions on the server.
|
|
#
|
|
# sshkey <path>
|
|
# - Will use the sshkey to do ssh dump.
|
|
# Specify the path of the ssh key to use when dumping
|
|
# via ssh. The default value is /root/.ssh/kdump_id_rsa.
|
|
#
|
|
# <fs type> <partition>
|
|
# - Will mount -t <fs type> <partition> <mnt>, and copy
|
|
# /proc/vmcore to <mnt>/<path>/%DATE/.
|
|
# NOTE: <partition> can be a device node, label or uuid.
|
|
# It's recommended to use persistent device names
|
|
# such as /dev/vg/<devname>.
|
|
# Otherwise it's suggested to use label or uuid.
|
|
#
|
|
# path <path>
|
|
# - "path" represents the file system path in which vmcore
|
|
# will be saved. If a dump target is specified in
|
|
# kdump.conf, then "path" is relative to the specified
|
|
# dump target.
|
|
#
|
|
# Interpretation of "path" changes a bit if the user didn't
|
|
# specify any dump target explicitly in kdump.conf. In this
|
|
# case, "path" represents the absolute path from root. The
|
|
# dump target and adjusted path are arrived at automatically
|
|
# depending on what's mounted in the current system.
|
|
#
|
|
# Ignored for raw device dumps. If unset, will use the default
|
|
# "/var/crash".
|
|
#
|
|
# core_collector <command> <options>
|
|
# - This allows you to specify the command to copy
|
|
# the vmcore. The default is makedumpfile, which on
|
|
# some architectures can drastically reduce vmcore 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.
|
|
# The default core_collector for raw/ssh dump is:
|
|
# "makedumpfile -F -l --message-level 1 -d 31".
|
|
# The default core_collector for other targets is:
|
|
# "makedumpfile -l --message-level 1 -d 31".
|
|
#
|
|
# "makedumpfile -F" will create a flattened vmcore.
|
|
# You need to use "makedumpfile -R" to rearrange the dump data to
|
|
# a normal dumpfile readable with analysis tools. For example:
|
|
# "makedumpfile -R vmcore < vmcore.flat".
|
|
#
|
|
# For core_collector format details, you can refer to
|
|
# kexec-kdump-howto.txt or kdump.conf manpage.
|
|
#
|
|
# kdump_post <binary | script>
|
|
# - This directive allows you to run a executable binary
|
|
# or script after the vmcore dump process terminates.
|
|
# The exit status of the current dump process is fed to
|
|
# the executable binary or script as its first argument.
|
|
#
|
|
# kdump_pre <binary | script>
|
|
# - Works like the "kdump_post" directive, but instead of running
|
|
# after the dump process, runs immediately before it.
|
|
# Exit status of this binary is interpreted as follows:
|
|
# 0 - continue with dump process as usual
|
|
# non 0 - reboot the system
|
|
#
|
|
# extra_bins <binaries | shell scripts>
|
|
# - This directive allows you to specify additional binaries or
|
|
# shell scripts to be included in the kdump initrd.
|
|
# Generally they are useful in conjunction with a kdump_post
|
|
# or kdump_pre binary or script which depends on these extra_bins.
|
|
#
|
|
# extra_modules <module(s)>
|
|
# - This directive allows you to specify extra kernel modules
|
|
# that you want to be loaded in the kdump initrd.
|
|
# Multiple modules can be listed, separated by spaces, and any
|
|
# dependent modules will automatically be included.
|
|
#
|
|
# default <reboot | halt | poweroff | shell | dump_to_rootfs>
|
|
# - Action to perform in case dumping fails.
|
|
# reboot: Reboot the system.
|
|
# halt: Halt the system.
|
|
# poweroff: Power down the system.
|
|
# shell: Drop to a bash shell.
|
|
# Exiting the shell reboots the system.
|
|
# dump_to_rootfs: Dump vmcore to rootfs from initramfs context and
|
|
# reboot. Useful when non-root dump target is specified.
|
|
# The default option is "reboot".
|
|
#
|
|
# force_rebuild <0 | 1>
|
|
# - By default, kdump initrd will only be rebuilt when necessary.
|
|
# Specify 1 to force rebuilding kdump initrd every time when kdump
|
|
# service starts.
|
|
#
|
|
# force_no_rebuild <0 | 1>
|
|
# - By default, kdump initrd will be rebuilt when necessary.
|
|
# Specify 1 to bypass rebuilding of kdump initrd.
|
|
#
|
|
# force_no_rebuild and force_rebuild options are mutually
|
|
# exclusive and they should not be set to 1 simultaneously.
|
|
#
|
|
# override_resettable <0 | 1>
|
|
# - Usually an unresettable block device can't be a dump target.
|
|
# Specifying 1 when you want to dump even though the block
|
|
# target is unresettable
|
|
# By default, it is 0, which will not try dumping destined to fail.
|
|
#
|
|
# dracut_args <arg(s)>
|
|
# - Pass extra dracut options when rebuilding kdump initrd.
|
|
#
|
|
# fence_kdump_args <arg(s)>
|
|
# - Command line arguments for fence_kdump_send (it can contain
|
|
# all valid arguments except hosts to send notification to).
|
|
#
|
|
# fence_kdump_nodes <node(s)>
|
|
# - List of cluster node(s) except localhost, separated by spaces,
|
|
# to send fence_kdump notifications to.
|
|
# (this option is mandatory to enable fence_kdump).
|
|
#
|
|
|
|
#raw /dev/vg/lv_kdump
|
|
#ext4 /dev/vg/lv_kdump
|
|
#ext4 LABEL=/boot
|
|
#ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
|
|
#nfs my.server.com:/export/tmp
|
|
#ssh user@my.server.com
|
|
#sshkey /root/.ssh/kdump_id_rsa
|
|
path /var/crash
|
|
core_collector makedumpfile -l --message-level 1 -d 31
|
|
#core_collector scp
|
|
#kdump_post /var/crash/scripts/kdump-post.sh
|
|
#kdump_pre /var/crash/scripts/kdump-pre.sh
|
|
#extra_bins /usr/bin/lftp
|
|
#extra_modules gfs2
|
|
#default shell
|
|
#force_rebuild 1
|
|
#force_no_rebuild 1
|
|
#dracut_args --omit-drivers "cfg80211 snd" --add-drivers "ext2 ext3"
|
|
#fence_kdump_args -p 7410 -f auto -c 0 -i 10
|
|
#fence_kdump_nodes node1 node2
|