abrt-retrace-client(1) [centos man page]
ABRT-RETRACE-CLIEN(1) ABRT Manual ABRT-RETRACE-CLIEN(1) NAME
abrt-retrace-client - Handles the communication with Retrace server. SYNOPSIS
abrt-retrace-client <operation> [options] DESCRIPTION
This tool is able to communicate with Retrace server: create a new task, ask about task's status, download log or backtrace of a finished task. Integration with libreport events abrt-retrace-client can be used as an analyzer for application crashes which dump core. Example usage in report_event.conf: EVENT=analyze analyzer=CCpp abrt-retrace-client OPERATIONS
create Creates a new task. Prints task ID and password to stdout. Either -d or -c is required. status Prints task's status to stdout. Both -t and -p are required. log Prints finished task's log to stdout. Both -t and -p are required. backtrace Print finished task's backtrace to stdout. Both -t and -p are required. batch Runs all operations in one step: creates a new task, periodically asks for status (the period is specified by --status-delay option) and downloads the result when finished. If the task was successful backtrace file is saved, otherwise log is printed to stdout. Either -c or -d is required. OPTIONS
-v, --verbose be verbose -s, --syslog log to syslog -k, --insecure allow insecure connection to retrace server --url URL retrace server URL --headers (debug) show received HTTP headers -d, --dir DIR read data from ABRT problem directory -c, --core COREDUMP read data from coredump -l, --status-delay delay for polling operations (seconds) --no-unlink (debug) do not delete temporary archive created in /tmp -t, --task ID ID of the task on server -p, --password PWD password of the task on server AUTHORS
o ABRT team abrt 2.1.11 06/18/2014 ABRT-RETRACE-CLIEN(1)
Check Out this Related Man Page
ABRT-AUTO-REPORTIN(1) ABRT Manual ABRT-AUTO-REPORTIN(1) NAME
abrt-auto-reporting - Get or modify a value of the auto reporting option SYNOPSIS
abrt-auto-reporting [-v] [ enabled | yes | 1 | disabled | no | 0 ] DESCRIPTION
Reads the configuration from abrt.conf and saves the changes to the same file. The changes will take effect immediately without necessity to restart any ABRT process and will be persistent. disabled User have to report the detect problems manually enabled ABRT uploads an uReport which was generated for a detected problem immediately after the detection phase. uReport description ABRT supports uReports for four types of crashes: crashes of C/C++ programs that result in a core dump, uncaught Python exceptions, uncaught Java exceptions and kernel oopses. Each uReport generally contains a stack trace, or multiple stack traces in the case of multi-threaded C/C++ and Java programs. The stack trace only describes the call stack of the program at the time of the crash and does not contain contents of any variables. Every uReport also contains identification of the operating system, versions of the RPM packages involved in the crash, and whether the program ran under a root user. There are also items specific to each crash type: C/C++ crashes these are path to the executable and signal delivered to the program, Python exceptions there is the type of the exception (without the error message, which may contain sensitive data), for kernel oopses these are list of loaded kernel modules, list of taint flags, and full text of the kernel oops. Warning: The full text of a kernel oops might contain information like the identification of the host hardware type. You should disable the autoreporting feature if you do not want to share this information with Red Hat. OPTIONS
-v, --verbose Be more verbose. Can be given multiple times. SEE ALSO
abrt.conf(5) AUTHORS
o ABRT team abrt 2.1.11 06/18/2014 ABRT-AUTO-REPORTIN(1)