From Fedora Project Wiki
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|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= | ||
{{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.}} |
Revision as of 17:39, 22 September 2011
Description
This test case tests the functionality of the ABRT kerneloops feature.
How to test
- Ensure you have the plugin installed with the following command:
su -c 'yum install abrt-addon-kerneloops'
- Ensure that the system log watcher service is running -
systemctl status abrt-oops.service
- Download the following file:
- 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'
- Append
oops1.test
to/var/log/messages
with the following command:su -c 'cat oops1.test >> /var/log/messages'
- Observe whether a crash notification appears
Expected Results
- 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'
.