+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1533410 +++ ====================================================================== Description of problem: without setting MakeCompatCore=yes (although CreateCoreBacktrace=yes is set) in /etc/abrt/plugins/CCpp.conf the abrt crash report includes the following files: abrt_version cgroup count event_log hostname limits open_fds package pkg_epoch pkg_release proc_pid_status runlevel uid var_log_messages analyzer cmdline dso_list executable kernel machineid os_info pid pkg_fingerprint pkg_vendor pwd time username architecture component environ global_pid last_occurrence maps os_release pkg_arch pkg_name pkg_version reason type uuid with compact core config the output includes also the core_backtrace file with the following output: # cat core_backtrace { "signal": 11 , "executable": "/usr/libexec/qemu-kvm" , "stacktrace": [ { "crash_thread": true , "frames": [ { "address": 140000363764479 , "build_id": "c3f28802314af4ee866bf8d2e1b506b7bbf34cf6" , "build_id_offset": 973567 , "function_name": "ppoll" , "file_name": "/usr/lib64/libc-2.17.so" } , { "address": 93963107712921 , "build_id": "250731da86353c7dda890a58874c5eb9137f95fc" , "build_id_offset": 6033305 , "function_name": "qemu_poll_ns" , "file_name": "/usr/libexec/qemu-kvm" } , { "address": 93963107716520 , "build_id": "250731da86353c7dda890a58874c5eb9137f95fc" , "build_id_offset": 6036904 , "function_name": "main_loop_wait" , "file_name": "/usr/libexec/qemu-kvm" } , { "address": 93963104510348 , "build_id": "250731da86353c7dda890a58874c5eb9137f95fc" , "build_id_offset": 2830732 , "function_name": "main" , "file_name": "/usr/libexec/qemu-kvm" } ] } ] } Version-Release number of selected component (if applicable): vdsm-4-20-12 How reproducible: 100% Steps to Reproduce: 1.kill -SIGSEGV [vm-pid] 2.check /var/tmp/abrt/ output (Originally by Yaniv Bronheim)
After a discussion with qemu team even properly generated backtrace doesn't contain enough information about the crash. Also since RHEL 7.4 the generated crash dump doesn't contain guest memory dump, so the size should keep around 500MB. That's why we are going to change abrt configuration again to save complete core dump. (Originally by Martin Perina)
VDSM with default settings provided coredump during test: # ls -l */*core* -rw-r-----. 1 root abrt 8215 Mar 6 09:54 ccpp-2018-03-06-09:53:43-21973/core_backtrace -rw-r-----. 1 root abrt 298999808 Mar 6 09:53 ccpp-2018-03-06-09:53:43-21973/coredump # ls -l ccpp-2018-03-06-09\:53\:43-21973/ total 93888 -rw-r-----. 1 root abrt 6 Mar 6 09:53 abrt_version -rw-r-----. 1 root abrt 4 Mar 6 09:53 analyzer -rw-r-----. 1 root abrt 6 Mar 6 09:53 architecture -rw-r-----. 1 root abrt 606 Mar 6 09:53 cgroup -rw-r-----. 1 root abrt 3023 Mar 6 09:53 cmdline -rw-r-----. 1 root abrt 13 Mar 6 09:53 component -rw-r-----. 1 root abrt 8215 Mar 6 09:54 core_backtrace -rw-r-----. 1 root abrt 298999808 Mar 6 09:53 coredump -rw-r-----. 1 root abrt 1 Mar 6 09:54 count -rw-r-----. 1 root abrt 8265 Mar 6 09:54 dso_list -rw-r-----. 1 root abrt 85 Mar 6 09:53 environ -rw-r-----. 1 root abrt 0 Mar 6 09:54 event_log -rw-r-----. 1 root abrt 21 Mar 6 09:53 executable -rw-r-----. 1 root abrt 5 Mar 6 09:53 global_pid -rw-r-----. 1 root abrt 21 Mar 6 09:53 hostname -rw-r-----. 1 root abrt 21 Mar 6 09:53 kernel -rw-r-----. 1 root abrt 10 Mar 6 09:53 last_occurrence -rw-r-----. 1 root abrt 1323 Mar 6 09:53 limits -rw-r-----. 1 root abrt 135 Mar 6 09:54 machineid -rw-r-----. 1 root abrt 49942 Mar 6 09:53 maps -rw-r-----. 1 root abrt 3141 Mar 6 09:53 open_fds -rw-r-----. 1 root abrt 532 Mar 6 09:53 os_info -rw-r-----. 1 root abrt 51 Mar 6 09:53 os_release -rw-r-----. 1 root abrt 31 Mar 6 09:53 package -rw-r-----. 1 root abrt 5 Mar 6 09:53 pid -rw-r-----. 1 root abrt 6 Mar 6 09:53 pkg_arch -rw-r-----. 1 root abrt 2 Mar 6 09:53 pkg_epoch -rw-r-----. 1 root abrt 19 Mar 6 09:53 pkg_fingerprint -rw-r-----. 1 root abrt 13 Mar 6 09:53 pkg_name -rw-r-----. 1 root abrt 11 Mar 6 09:53 pkg_release -rw-r-----. 1 root abrt 13 Mar 6 09:53 pkg_vendor -rw-r-----. 1 root abrt 5 Mar 6 09:53 pkg_version -rw-r-----. 1 root abrt 1192 Mar 6 09:53 proc_pid_status -rw-r-----. 1 root abrt 1 Mar 6 09:53 pwd -rw-r-----. 1 root abrt 26 Mar 6 09:53 reason -rw-r-----. 1 root abrt 4 Mar 6 09:53 runlevel -rw-r-----. 1 root abrt 10453852 Mar 6 09:54 sosreport.tar.xz -rw-r-----. 1 root abrt 10 Mar 6 09:53 time -rw-r-----. 1 root abrt 4 Mar 6 09:53 type -rw-r-----. 1 root abrt 3 Mar 6 09:53 uid -rw-r-----. 1 root abrt 1 Mar 6 09:54 ureports_counter -rw-r-----. 1 root abrt 5 Mar 6 09:53 username -rw-r-----. 1 root abrt 40 Mar 6 09:54 uuid -rw-r-----. 1 root abrt 159 Mar 6 09:54 var_log_messages
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0563
BZ<2>Jira Resync