From Fedora Project Wiki

Line 7: Line 7:
 
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-oops.service}}
 
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-oops.service}}
 
# Download the following file:
 
# Download the following file:
#* [http://git.fedorahosted.org/git/?p=abrt.git;a=blob_plain;f=examples/oops1.test;h=e4f02d26c11cf613c522d577486ed9dfc597b1b7;hb=HEAD oops1.test]
+
#* [http://git.fedorahosted.org/cgit/abrt.git/plain/examples/oops1.test oops1.test]
 
# Make sure {{filename|/etc/libreport/events.d/koops_event.conf}} contains
 
# Make sure {{filename|/etc/libreport/events.d/koops_event.conf}} contains
 
#* <tt>EVENT=post-create analyzer=Kerneloops  abrt-action-analyze-oops</tt>
 
#* <tt>EVENT=post-create analyzer=Kerneloops  abrt-action-analyze-oops</tt>

Revision as of 08:44, 1 October 2012

Description

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


How to test

Note.png
Syslog
This test abuses syslog a bit - don't forget to restart it at the end of the test case.
  1. Ensure you have the plugin installed with the following command:
    • su -c 'yum install abrt-addon-kerneloops'
  2. Ensure that the system log watcher service is running - systemctl status abrt-oops.service
  3. Download the following file:
  4. Make sure /etc/libreport/events.d/koops_event.conf contains
    • EVENT=post-create analyzer=Kerneloops abrt-action-analyze-oops
    • EVENT=report_Kerneloops analyzer=Kerneloops reporter-kerneloops
    • If you have to change anything, restart abrtd: su -c 'systemctl restart abrtd.service'
  5. Append oops1.test to /var/log/messages with the following command:
    • su -c 'cat oops1.test >> /var/log/messages'
  6. 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

Now restart rsyslog service so writing to /var/log/messages works correctly again. Use the following command to restart the service: su -c 'systemctl restart rsyslog.service'.