[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <014d01d1ce55$aa469730$fed3c590$@opengridcomputing.com>
Date: Fri, 24 Jun 2016 15:19:09 -0500
From: "Steve Wise" <swise@...ngridcomputing.com>
To: "'nborisov'" <n.borisov.lkml@...il.com>,
<linux-kernel@...r.kernel.org>
Subject: RE: vmcore not getting created on linux-4.7
> >> Also what's the content of your /etc/kdump.conf file?
> >>
> >
> > #raw /dev/sda5
> > #ext4 /dev/sda3
> > #ext4 LABEL=/boot
> > #ext4 UUID=03138356-5e61-4ab3-b58e-27507ac41937
> > #net my.server.com:/export/tmp
> > #net user@...server.com
> > path /var/crash
> > #ext4 /dev/nvme0n1
> > core_collector makedumpfile -c --message-level 1 -d 31
> > #core_collector makedumpfile -c --message-level 1 -d 17
> > #core_collector scp
> > #core_collector cp --sparse=always
> > #extra_bins /bin/cp
> > #link_delay 60
> > #kdump_post /var/crash/scripts/kdump-post.sh
> > #extra_bins /usr/bin/lftp
> > #disk_timeout 30
> > #extra_modules gfs2
> > #options modulename options
> > #default shell
> > #debug_mem_level 0
> > #force_rebuild 1
> > #sshkey /root/.ssh/kdump_id_rsa
> >
>
> Rather standart, indeed. I have a similar configuration and everything
> is working as expected. The only other thing which I can suggest is to
> try updating the makedumpfile binary.
Updating to 1.6.0 of makedumpfile didn't help. :(
Powered by blists - more mailing lists