Attachment 827732 Details for Bug 1033585 – configuration for kdump

configuration for kdump

kdump.conf (text/plain), 4.69 KB, created by Frank Büttner on 2013-11-22 12:45:12 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Frank Büttner

Created: 2013-11-22 12:45:12 UTC

Size: 4.69 KB

patch

obsolete

># 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
>path /var/crash
>ext4 /dev/mapper/VG_System-LV_System
>core_collector makedumpfile -c -d 31

Actions: View

Attachments on bug 1033585: 827732