Hello,
A tentative fix for this bug is available for testing in the following
PPA :
ppa:louis-bouchard/makedumpfile-test
If you could kindly test and verify that it solves this issue on Xenial
as I am unable to reproduce the issue, it would help me a great deal.
If this is successful, I will upload it to Yakkety and proceed with the
SRU process.
Kind regards,
...Louis
** Changed in: makedumpfile (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1599561
Title:
Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name
after first dump during kdump over ssh.
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
In Progress
Bug description:
== Comment: #0 - PAVITHRA R. PRAKASH - 2016-06-30 07:12:40 ==
---Problem Description---
During kdump over ssh IP prefix will be present only in first dump,
subsequent dumps will not have IP in directory name.
---Steps to Reproduce---
1) apt-get install linux-crashdump
2) increase crashdump size:
sudo vim /etc/default/grub.d/kexec-tools.cfg
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
3) sudo update-grub ; reboot the machine
4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
5) kdump-config show # should show "ready to dump"
6) ssh-keygen -t rsa
7) Edit below parameters in /etc/default/kdump-tools
SSH="root@<server IP>"
SSH_KEY=/root/.ssh/id_rsa
8) kdump-config propagate
9) kdump-config show
10) reboot
11) echo "c" > /proc/sysrq-trigger
12) verify dump is created in ssh server.
13) trigger the crash again.
Logs
=====
root@ubuntu:/home/ubuntu# uname -a
Linux ubuntu 4.4.0-26-generic #45-Ubuntu SMP Mon Jun 20 17:27:01 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
dumps on ssh server when 3 crashes are triggered
------------------------------------------------------------------------
[root@ltc-fire5 crash]# ls
192.168.122.25-201606300523
[root@ltc-fire5 crash]# ls
192.168.122.25-201606300523 -201606300524
[root@ltc-fire5 crash]# ls
192.168.122.25-201606300523 -201606300524 -201606300525
[root@ltc-fire5 crash]# cd -201606300524
-bash: cd: -2: invalid option
cd: usage: cd [-L|[-P [-e]]] [dir]
[root@ltc-fire5 crash]# cd -- -201606300524
[root@ltc-fire5 -201606300524]# ls
dmesg.201606300524 dump.201606300524
== Comment: #8 - Kevin W. Rudd - 2016-07-05 18:23:01 ==
Canonical,
The behavior appears to be somewhat intermittent, and it looks as if
define_stampdir() might be getting called before the network init has
completed. If delaying this function is not practical, it might be
helpful to have define_stampdir() fall back to using just "hostname"
if "hostname -I" doesn't return any useful information for setting
THIS_HOST.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1599561/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
