Hide Forgot
Description of problem: When I try to enable the kdump using the s-c-kdump it fails with the following error: /usr/bin/kdumpctl start Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initramfs-3.9.8-300.fc19.x86_64kdump.img Starting kdump: [FAILED] dracut-install: ERROR: installing '/usr/lib/kbd/consolefonts/True.*' E: /usr/lib/dracut/dracut-install -D /var/tmp/initramfs.H81QI5 /usr/lib/kbd/consolefonts/True.* No memory reserved for crash kernel. Version-Release number of selected component (if applicable): system-config-kdump-2.0.11-2.fc19.noarch How reproducible: 100% Steps to Reproduce: 1. run s-c-kdump 2. go to manual settings tab, leave the defaults 3. press apply
This should be already fixed in the upstream[1]. See also bug #971228. [1] https://git.fedorahosted.org/cgit/system-config-kdump.git/commit/?id=8978f148559dc27e6648fde0c90ead4ab89da624
Update has been submitted to testing: https://admin.fedoraproject.org/updates/system-config-kdump-2.0.13-1.fc19
I'm able to reproduce a similar problem to this in Fedora 18 by running "sudo /usr/bin/kdumpctl restart" [gmann@localhost ~]$ sudo /usr/bin/kdumpctl restart Memory for crashkernel is not reserved Please reserve memory by passing "crashkernel=X@Y" parameter to the kernel Stopping kdump: Starting kdump: [gmann@localhost ~]$ rpm -q --whatprovides /usr/bin/kdumpctl kexec-tools-2.0.3-64.fc18.2.i686 Is the problem with this that the grub2-mkconfig generator is not adding crashkernel parameter to the command line? [gmann@localhost ~]$ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.10.13-101.fc18.i686.PAE root=UUID=082ee34e-3da3-4494-a44d-c5de6eefb95b ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.