1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
lttng-regenerate(1)
===================
:revdate: 14 June 2021
NAME
----
lttng-regenerate - Regenerate specific data of an LTTng recording session
SYNOPSIS
--------
Regenerate the metadata of a recording session:
[verse]
*lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *regenerate metadata* [option:--session='SESSION']
Regenerate the state dump event records of a recording session:
[verse]
*lttng* ['linkgenoptions:(GENERAL OPTIONS)'] *regenerate statedump* [option:--session='SESSION']
DESCRIPTION
-----------
The `lttng regenerate` command regenerates specific data of:
With the option:--session='SESSION' option::
The recording session named 'SESSION'.
Without the option:--session option::
The current recording session (see man:lttng-concepts(7) to learn
more about the current recording session).
See man:lttng-concepts(7) to learn more about recording sessions.
As of this version, the `metadata` and `statedump` targets are
available.
See the ``<<examples,EXAMPLES>>'' section below for usage examples.
Regenerate the metadata of a recording session
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Use the `metadata` target to resample the offset between the monotonic
clock and the wall time of the system, and then regenerate the metadata
stream files.
More specifically, you may want to resample the wall time following a
major link:https://en.wikipedia.org/wiki/Network_Time_Protocol[NTP]
correction. As such, LTTng can trace a system booting with an incorrect
wall time before its wall time is NTP-corrected. Regenerating the
metadata of the selected recording session ensures that trace readers
can accurately determine the event record timestamps relative to the
Unix epoch.
Note that if you plan to rotate (see man:lttng-concepts(7) to learn
more) the selected recording session, this target only regenerates the
metadata stream files of the current and next trace chunks.
[IMPORTANT]
====
You can only use the `metadata` target when the selected
recording session:
* Is not in live mode (nloption:--live option of
man:lttng-create(1)).
* If it has user space channels, they're configured to use a
per-user buffering scheme (nloption:--buffers-uid option of
man:lttng-enable-channel(1)).
+
See man:lttng-concepts(7) to learn more about channels.
====
Regenerate the state dump event records of a recording session
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Use the `statedump` target to collect up-to-date state dump information
and create corresponding event records.
This is particularly useful if the selected recording session is in
snapshot mode (nloption:--snapshot option of the man:lttng-create(1)
command) or if LTTng rotates trace files for one of its channels (see
man:lttng-concepts(7)): in both cases, the state dump information may be
lost.
include::common-lttng-cmd-options-head.txt[]
option:-s 'SESSION', option:--session='SESSION'::
Regenerate specific data of the recording session named 'SESSION'
instead of the current recording session.
include::common-lttng-cmd-help-options.txt[]
include::common-lttng-cmd-after-options.txt[]
[[examples]]
EXAMPLES
--------
.Regenerate the metadata of the current recording session.
====
[role="term"]
----
$ lttng regenerate metadata
----
====
.Regenerate the state dump event records of a specific recording session.
====
See the option:--session option.
[role="term"]
----
$ lttng regenerate statedump --session=my-session
----
====
include::common-footer.txt[]
SEE ALSO
--------
man:lttng(1),
man:lttng-concepts(7)
|
