1RETRACE-SERVER-WOR(1) Retrace Server Manual RETRACE-SERVER-WOR(1)
2
3
4
6 retrace-server-worker - Executes the retrace job.
7
9 retrace-server-worker [-h] [-v] [--restart] [--foreground] [--kernelver
10 KERNELVER] [--arch ARCH] task_id
11
13 The tool creates a worker process which does the bulk of the processing
14 of a retrace-server task. The worker process handles processing
15 slightly differently depending on the value of
16 CONFIG["RetraceEnvironment"], and may use mock, podman, or the native
17 environment to to prepare an environment for the processing of the
18 coredump or vmcore. The process then runs the debugger (gdb in the case
19 of a coredump, or crash in the case of a vmcore), saves the backtrace,
20 also calling hooks at various points in the processing, assuming hooks
21 is configured (see /etc/retrace-server-hooks.conf). Once all processing
22 is complete, the worker process then cleans up environment. Note that
23 the task_id argument is a number derived from the name of the directory
24 where crash data is saved, CONFIG["SaveDir"]/task_id.
25
27 -h, --help
28 Display help and exit.
29
30 -v, --verbose
31 Be verbose. Note this also turns on debug logging for create, batch
32 or restart operations.
33
34 --restart
35 Restart an existing task. Useful for vmcore tasks where kernelver
36 may not have been detected and thus the task failed. In such cases,
37 using this option along with --kernelver may allow a task to
38 succeed.
39
40 --foreground
41 Run the worker task in the foreground rather than forking to the
42 background.
43
44 --kernelver
45 For vmcore tasks, specify the version of the kernel rather than
46 attempting to detect it by scanning the vmcore file.
47
48 --arch
49 Architecture of the vmcore file. This option should be used with
50 the kernelver option.
51
53 • Michal Toman <_mtoman@redhat.com_[1]>
54
56 1. _mtoman@redhat.com_
57 mailto:_mtoman@redhat.com_
58
59
60
61retrace-server 1.24.2 10/18/2022 RETRACE-SERVER-WOR(1)