From Fedora Project Wiki
No edit summary |
(minor cleanups) |
||
| Line 3: | Line 3: | ||
|actions= | |actions= | ||
# Ensure you have the plugin installed with the command {{command|su -c 'yum install abrt-plugin-logger'}} | # Ensure you have the plugin installed with the command {{command|su -c 'yum install abrt-plugin-logger'}} | ||
# Edit {{filename|/etc/abrt/abrt_event.conf}} and be sure you have there e.g. <tt>EVENT=report_Logger abrt-action-print -o "${Log_File:-/var/log/abrt.log}"</tt> | # Edit {{filename|/etc/abrt/abrt_event.conf}} and be sure you have there e.g. <tt>EVENT=report_Logger abrt-action-print -o "${Log_File:-/var/log/abrt.log}"</tt>. This is the default, so if you are running a clean live image or have not manually re-configured abrt, it should be there | ||
# If | # If you had to change the file, restart ABRT with the command {{command|su -c 'systemctl restart abrtd.service'}} | ||
# Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running | # Confirm that the ''abrtd'' and ''abrt-applet'' processes are both running | ||
# Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package | # Kill a running process with the command {{command|kill -SIGSEGV (pid)}}. It must be a process that is part of a signed Fedora package | ||
| Line 10: | Line 10: | ||
# Select the entry matching the recently crashed application, then click on '''Open''' | # Select the entry matching the recently crashed application, then click on '''Open''' | ||
# When you reach reporter selector page, select '''Logger''' | # When you reach reporter selector page, select '''Logger''' | ||
# Use "Configure Events" button in the same window to change log file path. The default path, /var/log/abrt.log, is usually not writable by | # Use "Configure Events" button in the same window to change log file path. The default path, {{filename|/var/log/abrt.log}}, is usually not writable by regular users, so pick somewhere inside your home directory. The file does not have to exist, it will be created | ||
# Click through to the last window of the wizard | # Click through to the last window of the wizard | ||
|results= | |results= | ||
# After you finish the steps in wizard at the last screen you should see ''"The report was stored to <FILENAME>"'' | # After you finish the steps in wizard at the last screen you should see ''"The report was stored to <FILENAME>"'' | ||
# Open the log file and see if crash information is in it and is well-formatted | # Open the log file and see if crash information is in it and is well-formatted | ||
}} | }} | ||
[[Category:Package_abrt_test_cases]] | [[Category:Package_abrt_test_cases]] | ||
Revision as of 17:24, 29 March 2011
Description
This test case tests the functionality of the ABRT feature using the Logger reporting plugin.
How to test
- Ensure you have the plugin installed with the command
su -c 'yum install abrt-plugin-logger' - Edit
/etc/abrt/abrt_event.confand be sure you have there e.g. EVENT=report_Logger abrt-action-print -o "${Log_File:-/var/log/abrt.log}". This is the default, so if you are running a clean live image or have not manually re-configured abrt, it should be there - If you had to change the file, restart ABRT with the command
su -c 'systemctl restart abrtd.service' - Confirm that the abrtd and abrt-applet processes are both running
- Kill a running process with the command
kill -SIGSEGV (pid). It must be a process that is part of a signed Fedora package - Click on the panel applet to start abrt-gui
- Select the entry matching the recently crashed application, then click on Open
- When you reach reporter selector page, select Logger
- Use "Configure Events" button in the same window to change log file path. The default path,
/var/log/abrt.log, is usually not writable by regular users, so pick somewhere inside your home directory. The file does not have to exist, it will be created - Click through to the last window of the wizard
Expected Results
- After you finish the steps in wizard at the last screen you should see "The report was stored to <FILENAME>"
- Open the log file and see if crash information is in it and is well-formatted