Description of problem: Experiencing this issue of Kdump service not starting. After googling to find some solutions and going through the documentation of configuring "kdump" and implementing those steps, only managed to see "kdump" service successfully failing. Hence thought of posting this issue. I have configured "kdump" in RHEL-6 and no issues were faced, although it was quite sometime back. This is first time I am trying to configure "kdump" in fedora. Version-Release number of selected component (if applicable): Static hostname: vibha.fedora.home Icon name: computer-desktop Chassis: desktop Machine ID: bb98bfc152c14ef5ac8ebaeed4fdda14 Boot ID: 96050e1ce3a542ab88b8bcba722632e2 Operating System: Fedora 27 (Twenty Seven) CPE OS Name: cpe:/o:fedoraproject:fedora:27 Kernel: Linux 4.16.11-200.fc27.x86_64 Architecture: x86-64 How reproducible: always Steps to Reproduce: 1. systemctl restart kdump 2. Reboot of the host does not generate the kdump "initrd" file and service fails to start Actual results: $ systemctl status kdump ● kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-05-29 11:50:37 AEST; 4h 9min ago Process: 21300 ExecStart=/usr/bin/kdumpctl start (code=exited, status=1/FAILURE) Main PID: 21300 (code=exited, status=1/FAILURE) May 29 11:50:37 vibha.fedora.home systemd[1]: Starting Crash recovery kernel arming... May 29 11:50:37 vibha.fedora.home kdumpctl[21300]: No memory reserved for crash kernel May 29 11:50:37 vibha.fedora.home kdumpctl[21300]: Starting kdump: [FAILED] May 29 11:50:37 vibha.fedora.home systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE May 29 11:50:37 vibha.fedora.home systemd[1]: Failed to start Crash recovery kernel arming. May 29 11:50:37 vibha.fedora.home systemd[1]: kdump.service: Unit entered failed state. May 29 11:50:37 vibha.fedora.home systemd[1]: kdump.service: Failed with result 'exit-code'. Expected results: The service is expected to be up and running. Additional info: # cat /sys/kernel/kexec_crash_size 0 Configuration: 1. /etc/kdump.conf xfs /dev/mapper/sysvg-var_crash path / core_collector makedumpfile -l --message-level 1 -d 31 default reboot 1.a. "/var/crash" file system Filesystem Size Used Avail Use% Mounted on /dev/mapper/sysvg-var_crash 30G 63M 30G 1% /var/crash 2. grub2.cfg linux16 /vmlinuz-4.16.11-200.fc27.x86_64 root=/dev/mapper/sysvg-root ro crashkernel=auto rd.lvm.lv=sysvg/root rd.lvm.lv=sysvg/swap rhgb quiet 2.a. System Memory total used free shared buff/cache available Mem: 64418 3595 51859 173 8963 60663 Swap: 16383 0 16383 3. sysctl configuration kernel.sysrq = 1 vm.panic_on_oom = 1 kernel.softlockup_panic = 1 kernel.panic_on_unrecovered_nmi = 1 kernel.unknown_nmi_panic = 1 kernel.panic = 1 kernel.panic_on_io_nmi = 1 kernel.panic_on_oops = 1 kernel.panic_on_stackoverflow = 1 4. Kernel configs (already enabled) CONFIG_KEXEC=y CONFIG_CRASH_DUMP=y CONFIG_RELOCATABLE=y CONFIG_PROC_VMCORE=y CONFIG_SYSFS=y CONFIG_DEBUG_INFO=y
+ KEXEC=/sbin/kexec + KDUMP_KERNELVER= + KDUMP_COMMANDLINE= + KEXEC_ARGS= + KDUMP_CONFIG_FILE=/etc/kdump.conf + MKDUMPRD='/sbin/mkdumprd -f' + SAVE_PATH=/var/crash + SSH_KEY_LOCATION=/root/.ssh/kdump_id_rsa + INITRD_CHECKSUM_LOCATION=/boot/.fadump_initrd_checksum + DUMP_TARGET= + DEFAULT_INITRD= + DEFAULT_INITRD_BAK= + TARGET_INITRD= + FADUMP_REGISTER_SYS_NODE=/sys/kernel/fadump_registered + DEFAULT_DUMP_MODE=kdump + image_time=0 + [[ -n '' ]] + dracutbasedir=/usr/lib/dracut + . /usr/lib/dracut/dracut-functions.sh ++ export LC_MESSAGES=C ++ LC_MESSAGES=C + . /lib/kdump/kdump-lib.sh ++ DEFAULT_PATH=/var/crash/ ++ FENCE_KDUMP_CONFIG_FILE=/etc/sysconfig/fence_kdump ++ FENCE_KDUMP_SEND=/usr/libexec/fence_kdump_send ++ FADUMP_ENABLED_SYS_NODE=/sys/kernel/fadump_enabled + standard_kexec_args=-p + KDUMP_COMMANDLINE_REMOVE='hugepages hugepagesz slub_debug' + '[' -f /etc/sysconfig/kdump ']' + . /etc/sysconfig/kdump ++ KDUMP_KERNELVER= ++ KDUMP_COMMANDLINE= ++ KDUMP_COMMANDLINE_REMOVE='hugepages hugepagesz slub_debug quiet' ++ KDUMP_COMMANDLINE_APPEND='irqpoll nr_cpus=1 reset_devices cgroup_disable=memory mce=off numa=off udev.children-max=2 panic=10 rootflags=nofail acpi_no_memhotplug transparent_hugepage=never nokaslr' ++ KEXEC_ARGS= ++ KDUMP_IMG=vmlinuz ++ KDUMP_IMG_EXT= + '[' '!' -f /etc/kdump.conf ']' + single_instance_lock + local rc timeout=5 + exec + '[' 0 -ne 0 ']' + flock -n 9 + rc=0 + '[' 0 -ne 0 ']' + exec + main start + determine_dump_mode + is_fadump_capable + '[' -f /sys/kernel/fadump_enabled ']' + return 1 + case "$1" in + '[' -s /proc/vmcore ']' + start + check_dump_feasibility + '[' kdump == fadump ']' + check_kdump_feasibility + '[' '!' -e /sys/kernel/kexec_crash_loaded ']' + check_crash_mem_reserved + local mem_reserved ++ cat /sys/kernel/kexec_crash_size + mem_reserved=0 + '[' 0 -eq 0 ']' + echo 'No memory reserved for crash kernel' No memory reserved for crash kernel <=================== + return 1 + return 1 + return 1 + '[' 1 -ne 0 ']' + echo 'Starting kdump: [FAILED]' Starting kdump: [FAILED] + return 1 + exit 1
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.