From Fedora Project Wiki

(abrt 2 changes)
(updated to match current abrt)
 
(14 intermediate revisions by 5 users not shown)
Line 2: Line 2:
 
|description=This test case tests the functionality of the ABRT kerneloops feature.
 
|description=This test case tests the functionality of the ABRT kerneloops feature.
 
|actions=
 
|actions=
# We will check that the {{command|abrt-dump-oops}} works and provides correct amount of crashes detected.
 
# Download files:
 
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/cut_here.test;hb=HEAD cut_here.test]
 
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/not_oops3.test;hb=HEAD not_oops3.test]
 
# Test that stand-alone detector tool works properly; Do as a root for both files:
 
#: $ abrt-dump-oops -d -o cut_here.test
 
#: Version: 2.6.32-19.el6.x86_64
 
#: WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467
 
#: generic_get_mtrr+0x11e/0x140() (Not tainted)
 
#: ...
 
#: [<ffffffff810abcff>] sys_init_module+0xdf/0x250
 
#: [<ffffffff81013172>] system_call_fastpath+0x16/0x1b
 
#: abrt-dump-oops: Creating dump directories
 
# Open abrt-gui and look for the crash.
 
# And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
 
# Make sure {{filename|/etc/abrt/abrt_event.conf}} contains <tt>EVENT=post-create analyzer=Kerneloops  abrt-action-analyze-oops</tt> and <tt>EVENT=report          analyzer=Kerneloops  abrt-action-kerneloops</tt>. If changed anything, restart abrtd:<tt> service abrtd restart</tt>.
 
# cat the downloaded file to {{filename|/var/log/messages}} e.g.:<pre>cat cut_here.test >> /var/log/messages</pre>
 
# If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to popup to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.
 
  
 +
 +
# Ensure you have will-crash-0.5 installed
 +
#* {{command|su -c 'yum install will-crash-0.5'}}
 +
# Ensure you have the plugin installed with the following command:
 +
#* {{command|su -c 'yum install abrt-addon-kerneloops'}}
 +
# Ensure you have kernel-devel package installed
 +
#* {{command|su -c 'yum install kernel-devel-`uname -r`'}}
 +
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-oops.service}}
 +
# Make sure {{filename|/etc/libreport/events.d/koops_event.conf}} contains
 +
<pre>EVENT=post-create analyzer=Kerneloops
 +
        # >> instead of > is due to bugzilla.redhat.com/show_bug.cgi?id=854266
 +
        abrt-action-analyze-oops &&
 +
        dmesg >>dmesg &&
 +
        abrt-action-generate-core-backtrace
 +
        abrt-action-save-kernel-data
 +
</pre>
 +
# Run the following command:
 +
#* {{command|su -c 'will_oops'}}
 +
# Observe whether a crash notification appears
 
|results=
 
|results=
# After running {{command|abrt-dump-oops}} on {{filename|cut_here.test}} crash should be craeted nad visible via abrt-gui and in the terminal. Running the same command on {{filename|not_oops3.test}} should not create crash case.
+
# ABRT should catch kernel oops appearing in {{filename|/var/log/messages}}, create a crash report and notify you via the notification area
# After finishing the second part: oops was detected and is visible in abrt-gui.
 
 
}}
 
}}
 
[[Category:Package_abrt_test_cases]]
 
[[Category:Package_abrt_test_cases]]

Latest revision as of 12:21, 3 May 2013

Description

This test case tests the functionality of the ABRT kerneloops feature.


How to test

  1. Ensure you have will-crash-0.5 installed
    • su -c 'yum install will-crash-0.5'
  2. Ensure you have the plugin installed with the following command:
    • su -c 'yum install abrt-addon-kerneloops'
  3. Ensure you have kernel-devel package installed
    • su -c 'yum install kernel-devel-uname -r'
  4. Ensure that the system log watcher service is running - systemctl status abrt-oops.service
  5. Make sure /etc/libreport/events.d/koops_event.conf contains
EVENT=post-create analyzer=Kerneloops
        # >> instead of > is due to bugzilla.redhat.com/show_bug.cgi?id=854266
        abrt-action-analyze-oops &&
        dmesg >>dmesg &&
        abrt-action-generate-core-backtrace
        abrt-action-save-kernel-data
  1. Run the following command:
    • su -c 'will_oops'
  2. Observe whether a crash notification appears

Expected Results

  1. ABRT should catch kernel oops appearing in /var/log/messages, create a crash report and notify you via the notification area