kdump doesn't support network dump

Bug #1477449 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
makedumpfile (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Problem Description
====================
kdump doesn't support dump through network. Looks like tis works fine in 15.04.

---uname output---
Linux pinelp2 3.19.0-22-generic #22~14.04.1-Ubuntu SMP Wed Jun 17 10:03:39 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

Steps to Reproduce
=====================
1. install 14.04.3
2. check /etc/default/kdump-tools, there is no options for dumping through network

Userspace tool common name: kdump-tools
The userspace tool has the following bit modes: 64-bit
Userspace rpm: 1.5.5-2ubuntu1

== Comment: # - Vaishnavi Bhat <email address hidden> - ==
Hi Ping Tian Han,

Like mentioned in the bug description, I see there is no option for dumping through network in /etc/default/kdump-tools,

Can you try manually adding NFS"<nfs location to dump vmcore>" in the /etc/default.kdump-tools and check if this fails to dump vmcore or successful ?

Thank you.

== Comment: # - Ping Tian Han <email address hidden> - ==
(In reply to comment #4)
> Hi Ping Tian Han,
>
> Like mentioned in the bug description, I see there is no option for dumping
> through network in /etc/default/kdump-tools,
>
> Can you try manually adding NFS"<nfs location to dump vmcore>" in the
> /etc/default.kdump-tools and check if this fails to dump vmcore or
> successful ?
>
> Thank you.

I added NFS="10.33.4.4:/distros" in the file then run "service kdump-tools restart", then triggered kdump, but it doesn't try the NFS location, still dump to local disk.

== Comment: # - Vaishnavi Bhat <email address hidden> - ==
After adding the NFS details in /etc/default/kdump-tools and restarting the kdump service, there is no NFS details while doing a 'kdump-config show'.

root@pinelp2:~# kdump-config show
USE_KDUMP: 1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR: /var/crash
crashkernel addr:
current state: ready to kdump

kexec command:
  /sbin/kexec -p --args-linux --command-line="BOOT_IMAGE=/boot/vmlinux-3.19.0-22-generic root=UUID=8846b7fd-86b3-4823-a985-b57c279d1856 ro irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-22-generic /boot/vmlinux-3.19.0-22-generic

Revision history for this message
bugproxy (bugproxy) wrote : console log of kdump after adding NFS=<location>

Default Comment by Bridge

tags: added: architecture-ppc64le bugnameltc-127853 severity-high targetmilestone-inin14043
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1477449/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
vaishnavi (vaishnavi)
affects: ubuntu → makedumpfile (Ubuntu)
Louis Bouchard (louis)
Changed in makedumpfile (Ubuntu):
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Louis Bouchard (louis-bouchard)
Revision history for this message
Louis Bouchard (louis) wrote :

Hello,

You are correct, the networked kernel dumping mechanism was introduced in Utopic Unicorn (14.10). Being a major functionality upgrade, it cannot be backported to the stable release as it would go against SRU rules.

What I can offer is to request for a backport of the version in Vivid into the -backports archive but it will not be possible to have the functionality in the main archive.

Please let me know if the trusty-backports is acceptable to you

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-07-29 03:12 EDT-------
(In reply to comment #15)
> Hello,
>
> You are correct, the networked kernel dumping mechanism was introduced in
> Utopic Unicorn (14.10). Being a major functionality upgrade, it cannot be
> backported to the stable release as it would go against SRU rules.
>

I agree.

> What I can offer is to request for a backport of the version in Vivid into
> the -backports archive but it will not be possible to have the functionality
> in the main archive.
>

Thanks for considering this but we are okay without the backport.

> Please let me know if the trusty-backports is acceptable to you

------- Comment From <email address hidden> 2015-07-29 03:15 EDT-------
(In reply to comment #21)
> (In reply to comment #15)
> > Hello,
> >
> > You are correct, the networked kernel dumping mechanism was introduced in
> > Utopic Unicorn (14.10). Being a major functionality upgrade, it cannot be
> > backported to the stable release as it would go against SRU rules.
> >
>
> I agree.
>
> > What I can offer is to request for a backport of the version in Vivid into
> > the -backports archive but it will not be possible to have the functionality
> > in the main archive.
> >
>
> Thanks for considering this but we are okay without the backport.
>

To be precise, we are fine not having this feature in trusty.

> > Please let me know if the trusty-backports is acceptable to you

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-08-03 17:34 EDT-------
Bug closed on IBM side. We don't need this feature at 14.04 at the moment.

Louis Bouchard (louis)
Changed in makedumpfile (Ubuntu):
status: Confirmed → Invalid
assignee: Louis Bouchard (louis-bouchard) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.