Bug 690362

Summary: Kdump does not send vmcore to remote server
Product: Red Hat Enterprise Linux 6 Reporter: Guohua Ouyang <gouyang>
Component: kexec-toolsAssignee: Cong Wang <amwang>
Status: CLOSED DUPLICATE QA Contact: Kernel Dump QE <kernel-dump-qe>
Severity: high Docs Contact:
Priority: medium    
Version: 6.1CC: apevec, leiwang, moli, ovirt-maint, rkhan, syeghiay, ycui
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-01 02:32:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen output of kdump fail to work none

Description Guohua Ouyang 2011-03-24 04:19:44 UTC 
Created attachment 487187 [details]
screen output of kdump fail to work

Description of problem:
Configure kdump location properly and then trigger system crash, it does not send vmcore file to remote nfs server or send incomplete vmcore file to ssh location.

[root@localhost ~]# cat /etc/kdump.conf
default reboot
net 10.66.8.216:/var/crash
[root@localhost ~]# service kdump status
Kdump is operational
[root@localhost ~]# echo c > /proc/sysrq-trigger

Version-Release number of selected component (if applicable):
rhev-hypervisor-6.1-10

How reproducible:
Always.

Steps to Reproduce:
1.  setenforce 0 as bug 654565 exist.
2.  configure kdump nfs or ssh location.
3.  check kdump service is running
      # service kdump status
        Kdump is operational
3.  make system crash:  echo c > /proc/sysrq-trigger

Actual results:
it does not send vmcore file to remote nfs server or send incomplete vmcore file to ssh location.

Expect Results:
A complete vmcore file is generated at remote location.

Additional info:
1. Attach screen output via serial console.
2. It is regression as it's not happened on 6.1-9, but ovirt-config-kdump file is the same.
Comment 3 Alan Pevec 2011-03-24 22:33:18 UTC 
That looks like a kdump regression, not RHEV-H specific, can it be reproduced with plain RHEL 6.1?

Relevant package manifest diff 6.1-9 vs 6.1-10 is:
-kernel-2.6.32-122.el6
+kernel-2.6.32-124.el6
-kexec-tools-2.0.0-169.el6
+kexec-tools-2.0.0-173.el6
Comment 4 Guohua Ouyang 2011-03-25 10:54:25 UTC 
(In reply to comment #3)
> That looks like a kdump regression, not RHEV-H specific, can it be reproduced
> with plain RHEL 6.1?

It should be kexec-tools regression issue, test it on RHEL6.0 but with new kernel:
kernel-2.6.32-125.el6
kdump work on kexec-tools-2.0.0-169.el6
kdump fail on kexec-tools-2.0.0-174.el6
Comment 5 Cong Wang 2011-03-30 03:01:58 UTC 
Hmm, from your console log, I can't see any failure:

Saving to remote location 10.66.8.216:/var/crash                                
Free memory/Total memory (free %): 68400 / 115040 ( 59.4576 )                   
Excluding unnecessary pages     md: stopping all md devices.                    
   : [100 %] kvm: exiting hardware virtualization                               
sd 0:0:0:0: [sda] Synchronizing SCSI cache                                      
breth0: port 1(eth0) entering disabled state                                    
e1000e 0000:00:19.0: PCI INT A disabled                                         
Restarting system.                                                              
machine restart   

BTW, does -172 work?
Comment 6 Guohua Ouyang 2011-03-30 06:19:40 UTC 
kexec-tools-2.0.0-172.el6 fail also.
Comment 7 Cong Wang 2011-03-31 11:41:37 UTC 
Looks like a regression from -172. Could you try the latest -179?
https://brewweb.devel.redhat.com/buildinfo?buildID=161029

Thanks.
Comment 8 Guohua Ouyang 2011-04-01 02:27:22 UTC 
work on kexec-tools-2.0.0-179.el6,
it's succeed to generate vmcore file on local disk or remote disk.
Comment 9 Cong Wang 2011-04-01 02:32:41 UTC 

*** This bug has been marked as a duplicate of bug 691632 ***