From Fedora Project Wiki

Line 3: Line 3:
 
|actions=
 
|actions=
 
{{admon/note|Syslog|This test abuses syslog a bit - don't forget to restart it at the end of the test case.}}
 
{{admon/note|Syslog|This test abuses syslog a bit - don't forget to restart it at the end of the test case.}}
 +
# Ensure you have the plugin installed with the command {{command|su -c 'yum install abrt-addon-kerneloops'}}
 
# Download files:
 
# Download files:
 
#* [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/git/?p=abrt.git;a=blob_plain;f=examples/oops1.test;h=e4f02d26c11cf613c522d577486ed9dfc597b1b7;hb=HEAD oops1.test]

Revision as of 16:54, 22 September 2011

Description

This test case tests the functionality of the ABRT kerneloops feature. We will check that the abrt-dump-oops works and provides correct amount of crashes detected.


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 command su -c 'yum install abrt-addon-kerneloops'
  2. Download files:
  3. For each file, run the following command: su -c 'abrt-dump-oops -d -o (filename)'
  4. Both times, pen abrt-gui and check if a crash report was created
  5. Make sure /etc/abrt/events.d/koops_events.conf contains EVENT=post-create analyzer=Kerneloops abrt-action-analyze-oops and EVENT=report_kerneloops.org analyzer=Kerneloops abrt-action-kerneloops, and /etc/abrt/abrt.conf contains abrt-dump-oops = abrt-dump-oops -drwx /var/log/messages. If you have to change anything, restart abrtd: su -c 'systemctl restart abrtd.service'
  6. Append oops1.test to /var/log/messages with the command su -c 'cat oops1.test >> /var/log/messages'
  7. Observe whether a crash notification appears

Expected Results

  1. After running abrt-dump-oops on oops1.test a crash report should be created and visible via abrt-gui and in the terminal
  2. Running abrt-dump-oops on not_oops3.test should not create a crash report
  3. ABRT should catch kernel oops appearing in /var/log/messages and create a crash report, and notify you via the notification area

Now restart rsyslog service so writing to /var/log/messages works correctly again.