From Fedora Project Wiki
No edit summary |
No edit summary |
||
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/ | #* [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
- 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'
.