This test case tests the functionality of the ABRT kerneloops feature.
How to test
Warning: This test abuses syslog a bit - don't forget to restart it at the end of the test case.
- We will check that the
abrt-dump-oopsworks and provides correct amount of crashes detected.
- Download files:
- Test that stand-alone detector tool works properly; Do as a root for both files:
- $ abrt-dump-oops -d -o oops1.test
- abrt-dump-oops: Found oopses: 1
- Version: 22.214.171.124-159.fc10.i686 #1
- BUG: unable to handle kernel NULL pointer dereference at 00000000
- EIP: [<f88dec25>] radeon_cp_init_ring_buffer+0x90/0x302 [radeon] SS:ESP 0068:f0a0cf08
- abrt-dump-oops: Creating dump directories
- Open abrt-gui and look for the crash.
- And now test if ABRT's scanning of /var/log/messages works, you'll need a root privs for this
- Make sure
/etc/abrt/abrt_event.confcontains EVENT=post-create analyzer=Kerneloops abrt-action-analyze-oops and EVENT=report analyzer=Kerneloops abrt-action-kerneloops. If changed anything, restart abrtd: service abrtd restart.
- cat the downloaded file to
cat oops1.test >> /var/log/messages
- If you are logged as a root: Wait for abrt-applet (make sure it's running) and notification to popup to show the notification about the detected kerneloops. Otherwise open abrt-gui as a root instead.
- After running
oops1.testcrash should be craeted and visible via abrt-gui and in the terminal. Running the same command on
not_oops3.testshould not create crash case.
- After finishing the second part: oops was detected and is visible in abrt-gui.
Now restart rsyslog service so writing to
/var/log/messages works correctly again.