From Fedora Project Wiki

No edit summary
No edit summary
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'}}
# Ensure you have the plugin installed with the following command:
# Download files:
#* {{command|su -c 'yum install abrt-addon-kerneloops'}}
# Ensure that the system log watcher service is running - {{command|systemctl status abrt-oops.service}}
# 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/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/not_oops3.test;hb=HEAD not_oops3.test]
# Make sure {{filename|/etc/libreport/events.d/koops_event.conf}} contains
# For each file, run the following command: {{command|su -c 'abrt-dump-oops -d -o (filename)'}}
#* <tt>EVENT=post-create analyzer=Kerneloops  abrt-action-analyze-oops</tt>
# Both times, pen abrt-gui and check if a crash report was created
#* <tt>EVENT=report_Kerneloops analyzer=Kerneloops reporter-kerneloops</tt>
# 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'}}
#* If you have to change anything, restart abrtd: {{command|su -c 'systemctl restart abrtd.service'}}
# Append {{filename|oops1.test}} to {{filename|/var/log/messages}} with the command {{command|su -c 'cat oops1.test >> /var/log/messages'}}
# Append {{filename|oops1.test}} to {{filename|/var/log/messages}} with the following command:
#* {{command|su -c 'cat oops1.test >> /var/log/messages'}}
# 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.
Now restart '''rsyslog''' service so writing to {{filename|/var/log/messages}} works correctly again. Use the following command to restart the service: {{command|su -c 'systemctl restart rsyslog.service'}}.


}}
}}
[[Category:Package_abrt_test_cases]]
[[Category:Package_abrt_test_cases]]

Revision as of 17:39, 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

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'.

Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_ABRT_kernel_addon&oldid=254251"