From Fedora Project Wiki

(updated to match current abrt)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
|description=This test case tests the functionality of the ABRT kerneloops feature. We will check that the {{command|abrt-dump-oops}} works and provides correct amount of crashes detected.
+
|description=This test case tests the functionality of the ABRT kerneloops feature.
 
|actions=
 
|actions=
{{admon/note|Syslog|This test abuses syslog a bit - don't forget to restart it at the end of the test case.}}
+
 
# Download files:
+
 
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/oops1.test;h=e4f02d26c11cf613c522d577486ed9dfc597b1b7;hb=HEAD oops1.test]
+
# Ensure you have will-crash-0.5 installed
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/not_oops3.test;hb=HEAD not_oops3.test]
+
#* {{command|su -c 'yum install will-crash-0.5'}}
# For each file, run the following command: {{command|su -c 'abrt-dump-oops -d -o (filename)'}}
+
# Ensure you have the plugin installed with the following command:
# Both times, pen abrt-gui and check if a crash report was created
+
#* {{command|su -c 'yum install abrt-addon-kerneloops'}}
# Make sure {{filename|/etc/abrt/events.d/koops_events.conf}} contains <tt>EVENT=post-create analyzer=Kerneloops   abrt-action-analyze-oops</tt> and <tt>EVENT=report_kerneloops.org analyzer=Kerneloops  abrt-action-kerneloops</tt>, and {{filename|/etc/abrt/abrt.conf}} contains <tt>abrt-dump-oops = abrt-dump-oops -drwx /var/log/messages</tt>. If you have to change anything, restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}}
+
# Ensure you have kernel-devel package installed
# Append {{filename|oops1.test}} to {{filename|/var/log/messages}} with the command {{command|su -c 'cat oops1.test >> /var/log/messages'}}
+
#* {{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
 
# Observe whether a crash notification appears
 
|results=
 
|results=
# After running {{command|abrt-dump-oops}} on {{filename|oops1.test}} a crash report should be created and visible via abrt-gui and in the terminal
+
# ABRT should catch kernel oops appearing in {{filename|/var/log/messages}}, create a crash report and notify you via the notification area
# Running {{command|abrt-dump-oops}} on {{filename|not_oops3.test}} should not create a crash report
 
# ABRT should catch kernel oops appearing in {{filename|/var/log/messages}} and create a crash report, and notify you via the notification area
 
 
 
Now restart '''rsyslog''' service so writing to {{filename|/var/log/messages}} works correctly again.
 
 
 
 
}}
 
}}
 
[[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