In the last release of ABRT we’ve introduced tons of new features. The most
interesting ones are going to be summarized in this document.
The new releases introduced a new reporter “reporter-systemd-journal” (
The reporter is run in notify event what means it’s run after all necessary
event are run and reports the detected problems to systemd-journal in the form of
catalogue messages that contains essential problem details. The messages are
SYSLOG_IDENTIFIER=abrt-notification and are mainly designated for
developers and administrator.
For more information about systemd-journal catalog messages see github.com/abrt/abrt/wiki/systemd-journal-catalog-messages.
Example how the catalog report looks in systemd-journal:
Anyway, the main reason why the reporter was introduced is better integration with Cockpit. Cockpit shows all Error messages catched in systemd-journal in its “Logs” tab. Reports created by reporter-systemd-journal are marked with “abrt-notification” label. Those logs contain information about particular problems.
The next image shows how a abrt-notification log looks like in Cockpit:
Another feature which was requested by user a lot – possibility to
report not reportable problems – is introduced in the new release as well.
It’s done by a new global configuration option
controlled by the
ABRT_STOP_ON_NOT_REPORTABLE environment variable.
This enables clients to force libreport to always report problems regardless of
possible sensitive data leaks and report usability concerns. See abrt’s and
abrt report --help or
abrt-cli report --help)
We also improved ABRT’s security. Now, ABRT runs the core dump time backtrace
generator under the user of the crashed process not under root. This change
makes ABRT more secure to deploy as ABRT no longer runs elfutils functions in
superuser context and ABRT asks users to do security review of several more files.
Saving of core dumps to disk is now faster becase ABRT’s core_pattern hook
using low level kernel functions. ABRT also started limiting the dumped core
file size and set the default limit to 5GiB.
The limit can be changed through the
MaxCoreFileSize configuration option in
The new release improves Kernel vmcore plugin as well. It extends the ability
to parse the
kdump.conf file at any location, so the plugin can be used from a