REPORTER-KERNELOOPS(1) LIBREPORT MANUAL REPORTER-KERNELOOPS(1)NAME
reporter-kerneloops - Reports kernel oops to kerneloops.org (or similar) site.
SYNOPSIS
reporter-kerneloops [-v] [-c CONFFILE]... [-d DIR]
DESCRIPTION
The tool is used to report the crash to the Kerneloops tracker.
Configuration file
Configuration file contains entries in a format "Option = Value".
The options are:
SubmitURL
The URL of the kerneloops tracker, the default is "http://submit.kerneloops.org/submitoops.php".
Integration with ABRT events
reporter-kerneloops can be used as a reporter, to allow users to report problems to the Kerneloops tracker. This usage is pre-configured in
/etc/libreport/events.d/koops_event.conf:
EVENT=report_Kerneloops analyzer=Kerneloops reporter-kerneloops
It can be also used automatically and immediately without user interaction. When this is desired, modify the event configuration file to
run the tool on the post-create event:
EVENT=post-create analyzer=Kerneloops reporter-kerneloops
OPTIONS -v
Be more verbose. Can be given multiple times.
-d DIR
Path to problem directory.
-c CONFFILE
Path to configuration file. When used in ABRT event system, the file contains site-wide configuration. Users can change the values via
environment variables.
ENVIRONMENT VARIABLES
Environment variables take precedence over values provided in the configuration file.
KerneloopsReporter_SubmitURL
The URL of the kerneloops tracker.
AUTHORS
o ABRT team
LIBREPORT 2.1.11 06/18/2014 REPORTER-KERNELOOPS(1)
Check Out this Related Man Page
ABRT-ACTION-SAVE-(1) ABRT Manual ABRT-ACTION-SAVE-(1)NAME
abrt-action-save-package-data - Query package database and save package and component name.
SYNOPSIS
abrt-action-save-package-data [-v] [-c CONFFILE] -d DIR
DESCRIPTION
The tool reads problem directory DIR. It analyzes contents of analyzer, executable, cmdline and remote elements, checks database of
installed packages, and creates new elements package and component.
This data is usually necessary if the problem will be reported to a bug tracking database.
Integration with ABRT events
This tool can be used as an ABRT reporter. Example fragment for /etc/libreport/report_event.conf:
# Determine in which package/component the crash happened (if not yet done):
EVENT=post-create component=
abrt-action-save-package-data
OPTIONS -v, --verbose
Be verbose
-c CONFFILE
Path to configuration file.
-d DIR
Path to problem directory.
SEE ALSO abrt_event.conf(5), abrt-action-save-package-data.conf(5)AUTHORS
o ABRT team
abrt 2.1.11 06/18/2014 ABRT-ACTION-SAVE-(1)
Hello everybody,
I've been using Debian stable (currently Lenny) for more than one year, this is my first Linux. Never experienced any problems like this: when I logged in this morning, I got a message that said my kernel had had a failure and prompted me to send a report to www.kerneloops.org.... (2 Replies)
Hi, this is my first post...:p
Hello Admin :)
Can I have an ask for something with my configuration ?
I have finished some kind of the tutorial to build ipsec site to site, and the "step" has finished completely.
I have a simulation with a local design topology with two PC's (FreeBSD ... (0 Replies)
my sample file is like this
$cat onefile
05/21/18 13:10:07 ABRT US1CPDAY Status 1
05/21/18 21:18:54 ABRT DailyBackup_VFFPRDAPENTL01 Status 6
05/21/18 21:26:24 ABRT DailyBackup_VFFPRDAPENTL02 Status 6
05/21/18 21:57:36 ABRT DailyBackup_vm-ea1ffpreng01 Status 6... (7 Replies)