[Kernel-packages] [Bug 1681909] Re: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone.
** Changed in: makedumpfile (Ubuntu) Status: New => Incomplete -- 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/1681909 Title: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: Incomplete Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to see some errors in syslog ; auxiliary Mar 7 04:57:44 ltc-firep3 systemd-resolved[3486]: DNSSEC validation failed for question
[Kernel-packages] [Bug 1681909] Re: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone.
** Changed in: makedumpfile (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) ** Changed in: ubuntu-power-systems Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) -- 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/1681909 Title: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to
[Kernel-packages] [Bug 1681909] Re: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone.
** Summary changed: - [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone. + [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone. -- 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/1681909 Title: [FEAT 18.10] dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH - 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to see some
[Kernel-packages] [Bug 1681909] Re: [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone.
** Tags added: kernel-da-key ppc64el-kdump triage-g -- 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/1681909 Title: [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH- 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to see some errors in syslog ; auxiliary Mar 7
[Kernel-packages] [Bug 1681909] Re: [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone.
** Tags removed: bugnameltc-152306 kernel-da-key ppc64el-kdump severity- high triage-g -- 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/1681909 Title: [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH- 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH - 2017-03-07 23:21:27 == == Comment: #8 - Urvashi Jawere - 2017-03-08 02:48:15 == I am able to see some errors
[Kernel-packages] [Bug 1681909] Re: [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone.
** Summary changed: - [Feat req18.10]dump is not captured in remote host when kdump over ssh is configured on firestone. + [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone. -- 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/1681909 Title: [Feat 18.10]dump is not captured in remote host when kdump over ssh is configured on firestone. Status in The Ubuntu-power-systems project: Incomplete Status in makedumpfile package in Ubuntu: New Bug description: == Comment: #0 - PAVITHRA R. PRAKASH- 2017-03-07 05:00:29 == ---Problem Description--- Ubuntu 17.04: dump is not captured in remote host when kdump over ssh is configured on firestone. ---Steps to Reproduce--- 1. Configure kdump. 2. Check whether kdump is operational using ?# kdump-config show?. 3. Install ?kernel-debuginfo? and ?kernel-debuginfo-common? rpms. 4. Setup password less ssh connection, generate rsa key. # ssh-keygen -t rsa 5. verify id_rsa and id_rsa.pub are created under /root/.ssh/ 6. Edit /etc/default/kdump-tools and add below entries. SSH="ubuntu@9.114.15.239" SSH_KEY=/root/.ssh/id_rsa 7. Propagate RSA key. # kdump-config propagate 8. Restart kdump service. # kdump-config load 9. Trigger Crash using below commands. # echo "1" > /proc/sys/kernel/sysrq # echo "c" > /proc/sysrq-trigger 10. Verify dump is available in remote server in configured path. Machine details === $ ipmitool -I lanplus -H 9.47.70.3 -U ADMIN -P admin sol activate $ ssh ubuntu@9.47.70.29 PW: shriya101 Attaching logs == Comment: #1 - PAVITHRA R. PRAKASH - 2017-03-07 05:01:42 == == Comment: #5 - PAVITHRA R. PRAKASH - 2017-03-07 23:19:46 == Hi, Attaching the logs. Network info: root@ltc-firep3:~# hwinfo --network 36: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown 37: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 2lHw.ndpeucax6V1 Parent ID: mIXc.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f2 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.2 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f2 HW Address: 98:be:94:03:18:4a Permanent HW Address: 98:be:94:03:18:4a Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #15 (Ethernet controller) 38: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 7Onn.ndpeucax6V1 Parent ID: sx0U.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f0 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f0 HW Address: 98:be:94:03:18:48 Permanent HW Address: 98:be:94:03:18:48 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (Ethernet controller) 39: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: VwX_.ndpeucax6V1 Parent ID: DUng.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f3 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.3 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f3 HW Address: 98:be:94:03:18:4b Permanent HW Address: 98:be:94:03:18:4b Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #25 (Ethernet controller) 40: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: bZ1s.ndpeucax6V1 Parent ID: J7HY.aXC4wIvegH8 SysFS ID: /class/net/enP33p3s0f1 SysFS Device Link: /devices/pci0021:00/0021:00:00.0/0021:01:00.0/0021:02:01.0/0021:03:00.1 Hardware Class: network interface Model: "Ethernet network interface" Driver: "tg3" Driver Modules: "tg3" Device File: enP33p3s0f1 HW Address: 98:be:94:03:18:49 Permanent HW Address: 98:be:94:03:18:49 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #4 (Ethernet controller) root@ltc-firep3:~# Thanks, Pavithra == Comment: #6 - PAVITHRA R. PRAKASH - 2017-03-07 23:20:47 == == Comment: #7 - PAVITHRA R. PRAKASH -