f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel Jan 7 13:16:31 localhost kdumpctl[5208]: Starting kdump: Jan 7 13:16:31 localhost kdump: failed to start up Jan 7 13:16:31 localhost systemd[1]: kdump.service: main process exited, code=exited, status=1 Jan 7 13:16:31 localhost systemd[1]: Unit kdump.service entered failed state.
On Mon, 07 Jan 2013 13:20:00 -0500 Jim binarynut@comcast.net wrote:
f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel
Maybe: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840116
On 01/07/2013 02:23 PM, Frank Murphy wrote:
On Mon, 07 Jan 2013 13:20:00 -0500 Jim binarynut@comcast.net wrote:
f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel
Maybe: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840116
I check the bugzilla out and I have a later kexec-tools than they specify , I have kexec-tools-2.0.3-47-fc17.4.i386 and that does not help either.
On Mon, Jan 7, 2013 at 2:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 02:23 PM, Frank Murphy wrote:
On Mon, 07 Jan 2013 13:20:00 -0500 Jim binarynut@comcast.net wrote:
f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel
Maybe: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840116
I check the bugzilla out and I have a later kexec-tools than they specify , I have kexec-tools-2.0.3-47-fc17.4.i386 and that does not help either.
Do you have the crashkernel= parameter set on the kernel boot/grub.conf settings?
On 01/07/2013 04:43 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 2:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 02:23 PM, Frank Murphy wrote:
On Mon, 07 Jan 2013 13:20:00 -0500 Jim binarynut@comcast.net wrote:
f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel
Maybe: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840116
I check the bugzilla out and I have a later kexec-tools than they specify , I have kexec-tools-2.0.3-47-fc17.4.i386 and that does not help either.
Do you have the crashkernel= parameter set on the kernel boot/grub.conf settings?
yes I do.
On Mon, Jan 7, 2013 at 4:01 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 04:43 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 2:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 02:23 PM, Frank Murphy wrote:
On Mon, 07 Jan 2013 13:20:00 -0500 Jim binarynut@comcast.net wrote:
f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel
Maybe: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840116
I check the bugzilla out and I have a later kexec-tools than they specify , I have kexec-tools-2.0.3-47-fc17.4.i386 and that does not help either.
Do you have the crashkernel= parameter set on the kernel boot/grub.conf settings?
yes I do.
does cat /proc/cmdline show it? That appears to be what it is complaining about, it is not on the current running kernel.
On 01/07/2013 05:10 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 4:01 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 04:43 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 2:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 02:23 PM, Frank Murphy wrote:
On Mon, 07 Jan 2013 13:20:00 -0500 Jim binarynut@comcast.net wrote:
f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel
Maybe: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840116
I check the bugzilla out and I have a later kexec-tools than they
specify , I have kexec-tools-2.0.3-47-fc17.4.i386 and that does not help either.
Do you have the crashkernel= parameter set on the kernel boot/grub.conf settings?
yes I do.
does cat /proc/cmdline show it? That appears to be what it is complaining about, it is not on the current running kernel.
$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.5.2-1.fc17.i686 root=UUID=cf5a1042-bb2b-4c6b-a0e0-1da27273d413 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
On 01/07/2013 05:10 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 4:01 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 04:43 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 2:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 02:23 PM, Frank Murphy wrote:
On Mon, 07 Jan 2013 13:20:00 -0500 Jim binarynut@comcast.net wrote:
f17
Trying to start kdump and I get this error message;
Jan 7 13:16:31 localhost kdump: No crashkernel parameter specified for running kernel
Maybe: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=840116
I check the bugzilla out and I have a later kexec-tools than they
specify , I have kexec-tools-2.0.3-47-fc17.4.i386 and that does not help either.
Do you have the crashkernel= parameter set on the kernel boot/grub.conf settings?
yes I do.
does cat /proc/cmdline show it? That appears to be what it is complaining about, it is not on the current running kernel.
/boot/grub2/grub.conf
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ### if [ -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi crashkernel=128M ### END /etc/grub.d/41_custom ###
does cat /proc/cmdline show it? That appears to be what it is complaining about, it is not on the current running kernel.
$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.5.2-1.fc17.i686 root=UUID=cf5a1042-bb2b-4c6b-a0e0-1da27273d413 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
I don't see it on the current running kernel, the error is correct.
Have you rebooted and/or do you have it on the correct grub line for that kernel?
On Mon, Jan 7, 2013 at 7:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 07:55 PM, Roger Heflin wrote:
correct grub line for that kernel?
what correct grub line for that kernel ? it is in /boot/grub2/grub.conf
The line that booted the current kernel did not have a crashkernel option on it, you either have it on the wrong line in the grub.conf file, or a different grub.conf is being used than you expect or it has not been rebooted since the option was added.
Double check that link that was posted and make sure all is done right.
On 01/07/2013 08:26 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 7:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 07:55 PM, Roger Heflin wrote:
correct grub line for that kernel?
what correct grub line for that kernel ? it is in /boot/grub2/grub.conf
The line that booted the current kernel did not have a crashkernel option on it, you either have it on the wrong line in the grub.conf file, or a different grub.conf is being used than you expect or it has not been rebooted since the option was added.
Double check that link that was posted and make sure all is done right.
Thanks Roger, After I sent the reply it occurred to me what you were talking about.
$cat /proc/cmdline
OOT_IMAGE=/boot/vmlinuz-3.5.2-1.fc17.i686 root=UUID=cf5a1042-bb2b-4c6b-a0e0-1da27273d413 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet crashkernel=128M
I ran # systemctl start kdump.service and it still failed to start
I did restart the computer.
Error in messages for starting kdump;
Jan 7 21:07:12 localhost kdump: kexec: failed to load kdump kernel Jan 7 21:07:12 localhost kdumpctl[1735]: Starting kdump: Jan 7 21:07:12 localhost kdump: failed to start up Jan 7 21:07:12 localhost systemd[1]: kdump.service: main process exited, code=exited, status=1 Jan 7 21:07:12 localhost systemd[1]: Unit kdump.service entered failed state.
On Mon, Jan 7, 2013 at 8:09 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 08:26 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 7:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 07:55 PM, Roger Heflin wrote:
correct grub line for that kernel?
what correct grub line for that kernel ? it is in /boot/grub2/grub.conf
The line that booted the current kernel did not have a crashkernel option on it, you either have it on the wrong line in the grub.conf file, or a different grub.conf is being used than you expect or it has not been rebooted since the option was added.
Double check that link that was posted and make sure all is done right.
Thanks Roger, After I sent the reply it occurred to me what you were talking about.
$cat /proc/cmdline
OOT_IMAGE=/boot/vmlinuz-3.5.2-1.fc17.i686 root=UUID=cf5a1042-bb2b-4c6b-a0e0-1da27273d413 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet crashkernel=128M
I ran # systemctl start kdump.service and it still failed to start
I did restart the computer.
Error in messages for starting kdump;
Jan 7 21:07:12 localhost kdump: kexec: failed to load kdump kernel Jan 7 21:07:12 localhost kdumpctl[1735]: Starting kdump: Jan 7 21:07:12 localhost kdump: failed to start up Jan 7 21:07:12 localhost systemd[1]: kdump.service: main process exited, code=exited, status=1 Jan 7 21:07:12 localhost systemd[1]: Unit kdump.service entered failed state.
/var/log/messages may tell you why it is erroring.
Note that kdump will rebuild the initird so if there is something wrong with the initrd build process that will cause a failure.
On 01/08/2013 08:04 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 8:09 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 08:26 PM, Roger Heflin wrote:
On Mon, Jan 7, 2013 at 7:19 PM, Jim binarynut@comcast.net wrote:
On 01/07/2013 07:55 PM, Roger Heflin wrote:
correct grub line for that kernel?
what correct grub line for that kernel ? it is in /boot/grub2/grub.conf
The line that booted the current kernel did not have a crashkernel option on it, you either have it on the wrong line in the grub.conf file, or a different grub.conf is being used than you expect or it has not been rebooted since the option was added.
Double check that link that was posted and make sure all is done right.
Thanks Roger, After I sent the reply it occurred to me what you were talking about.
$cat /proc/cmdline
OOT_IMAGE=/boot/vmlinuz-3.5.2-1.fc17.i686 root=UUID=cf5a1042-bb2b-4c6b-a0e0-1da27273d413 ro rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 rhgb quiet crashkernel=128M
I ran # systemctl start kdump.service and it still failed to start
I did restart the computer.
Error in messages for starting kdump;
Jan 7 21:07:12 localhost kdump: kexec: failed to load kdump kernel Jan 7 21:07:12 localhost kdumpctl[1735]: Starting kdump: Jan 7 21:07:12 localhost kdump: failed to start up Jan 7 21:07:12 localhost systemd[1]: kdump.service: main process exited, code=exited, status=1 Jan 7 21:07:12 localhost systemd[1]: Unit kdump.service entered failed state.
/var/log/messages may tell you why it is erroring.
Note that kdump will rebuild the initird so if there is something wrong with the initrd build process that will cause a failure.
Above is the only info I get from /var/log/messages .