Comment 0 for bug 1571590

Revision history for this message
bugproxy (bugproxy) wrote :

Problem Description
============================
When dumping to ssh target , kdump failed:

         Starting Kernel crash dump capture service...
[ 18.542292] kdump-tools[2748]: Starting kdump-tools: ssh: connect to host 10.33.31.113 port 22: Network is unreachable
[ 18.542894] kdump-tools[2748]: * kdump-tools: Unable to reach remote server root@10.33.31.113. No reason to continue
[ 18.613376] kdump-tools[2748]: Mon, 11 Apr 2016 01:23:55 -0500
[ 19.310893] kdump-tools[2748]: Rebooting.
[ 19.652714] reboot: Restarting system

But the weired thing is that nfs target works on the same system.

---uname output---
Linux pinelp2 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:00:30 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

Steps to Reproduce
===================================
1. install latest ubuntu 16.04 on pinelp2
2. config kdump to use ssh:
SSH="root@10.33.31.113"
3. run "kdump-config propagate" as root
4. trigger kdump

Userspace tool common name: kdump-tools

The userspace tool has the following bit modes: 64-bit

Userspace rpm: version 1:1.5.9-5

== Comment: #8 - Ping Tian Han <email address hidden> - 2016-04-17 21:58:52 ==
(In reply to comment #6)
> I am able to reproduce this issue as well.
> Ping, what is you try to dump on some other machine with ssh ? Does it still
> complain the same ? Is the ssh failing to connect to the network ?

I saw the same problem when dumping to medlp4 with ssh:

         Starting Kernel crash dump capture service...
[ 17.293028] kdump-tools[2733]: Starting kdump-tools: ssh: connect to host 10.33.7.181 port 22: Network is unreachable
[ 17.293692] kdump-tools[2733]: * kdump-tools: Unable to reach remote server root@10.33.7.181. No reason to continue
[ 17.405333] kdump-tools[2733]: Sun, 17 Apr 2016 20:56:59 -0500
[ 18.536587] kdump-tools[2733]: Rebooting.
[ 18.903280] reboot: Restarting system

but I can ssh log noto medlp4 before triggering kdump.