LTTng bugs repository: Issueshttps://bugs.lttng.org/https://bugs.lttng.org/themes/lttng/favicon/a.ico?14249722912020-05-11T08:07:22ZLTTng bugs repository
Redmine LTTng-tools - Bug #1266 (Resolved): 2.12 fails to compile with C++ code when using session clear ...https://bugs.lttng.org/issues/12662020-05-11T08:07:22ZShuo Yang
<p>The below newly introduced header files:</p>
<ul>
<li><a class="external" href="https://github.com/lttng/lttng-tools/blob/stable-2.12/include/lttng/clear.h">https://github.com/lttng/lttng-tools/blob/stable-2.12/include/lttng/clear.h</a></li>
<li><a class="external" href="https://github.com/lttng/lttng-tools/blob/stable-2.12/include/lttng/clear-handle.h">https://github.com/lttng/lttng-tools/blob/stable-2.12/include/lttng/clear-handle.h</a></li>
</ul>
<p>miss the closing:</p>
<pre><code class="c syntaxhl" data-language="c"><span class="cp">#ifdef __cplusplus
</span><span class="err">}</span>
<span class="cp">#endif
</span></code></pre>
<p>section such that 2.12 fails to compile with C++ code when using session clear feature.</p>
<p>There might be some other headers also without the closing section that I didn't spot, please fix them altogether. Thanks!</p> LTTng-tools - Bug #1241 (Resolved): lttng_destroy_session_no_wait always return LTTNG_ERR_INVALID...https://bugs.lttng.org/issues/12412020-03-03T20:14:46ZShuo Yang
<p>The implementation of "lttng_destroy_session_no_wait" (<a class="external" href="https://github.com/lttng/lttng-tools/blob/stable-2.11/src/lib/lttng-ctl/lttng-ctl.c#L2051">https://github.com/lttng/lttng-tools/blob/stable-2.11/src/lib/lttng-ctl/lttng-ctl.c#L2051</a>) always returns "LTTNG_ERR_INVALID" in 2.11.</p>
<pre><code class="c syntaxhl" data-language="c"><span class="kt">int</span> <span class="nf">lttng_destroy_session_no_wait</span><span class="p">(</span><span class="k">const</span> <span class="kt">char</span> <span class="o">*</span><span class="n">session_name</span><span class="p">)</span>
<span class="p">{</span>
<span class="k">enum</span> <span class="n">lttng_error_code</span> <span class="n">ret_code</span><span class="p">;</span>
<span class="n">ret_code</span> <span class="o">=</span> <span class="n">lttng_destroy_session_ext</span><span class="p">(</span><span class="n">session_name</span><span class="p">,</span> <span class="nb">NULL</span><span class="p">);</span>
<span class="k">return</span> <span class="n">ret_code</span> <span class="o">==</span> <span class="n">LTTNG_OK</span> <span class="o">?</span> <span class="n">ret_code</span> <span class="o">:</span> <span class="o">-</span><span class="n">ret_code</span><span class="p">;</span>
<span class="p">}</span>
</code></pre>
<p>It calls "lttng_destroy_session_ext" with the second argument "_handle" as NULL, which causes LTTNG_ERR_INVALID to be returned. (<a class="external" href="https://github.com/lttng/lttng-tools/blob/stable-2.11/src/lib/lttng-ctl/destruction-handle.c#L407">https://github.com/lttng/lttng-tools/blob/stable-2.11/src/lib/lttng-ctl/destruction-handle.c#L407</a>)</p>
<pre><code class="c syntaxhl" data-language="c"> <span class="k">if</span> <span class="p">(</span><span class="o">!</span><span class="n">session_name</span> <span class="o">||</span> <span class="o">!</span><span class="n">_handle</span><span class="p">)</span> <span class="p">{</span>
<span class="n">ret_code</span> <span class="o">=</span> <span class="n">LTTNG_ERR_INVALID</span><span class="p">;</span>
<span class="k">goto</span> <span class="n">error</span><span class="p">;</span>
<span class="p">}</span>
</code></pre>
<p>Thus calling to "lttng_destroy_session_no_wait" won't actually destroy the session.</p> LTTng-tools - Bug #1119 (Resolved): Channel blocking timer is not saved (and loaded) by the lttng...https://bugs.lttng.org/issues/11192017-06-13T01:31:54ZJérémie Galarneaujeremie.galarneau@efficios.comLTTng-tools - Bug #1101 (Resolved): Channel position sampling should be disabled for lttng-module...https://bugs.lttng.org/issues/11012017-05-11T22:41:55ZJérémie Galarneaujeremie.galarneau@efficios.com
<p>The <code>RING_BUFFER_SNAPSHOT_SAMPLE_POSITIONS</code> kernctl command was introduced as part of the LTTng 2.10 release. It should not be used with older kernel tracer modules.</p> LTTng-tools - Bug #1099 (Resolved): Channel monitoring timer is not saved by the lttng save commandhttps://bugs.lttng.org/issues/10992017-05-05T20:06:28ZJérémie Galarneaujeremie.galarneau@efficios.comLTTng-tools - Bug #1071 (Resolved): lttng-mi XSD does not take new 2.9 override options into accounthttps://bugs.lttng.org/issues/10712016-10-26T16:38:35ZJérémie Galarneaujeremie.galarneau@efficios.com
<p>The machine interface schema of the lttng client has not been updated to reflect the new options introduced to the save/load commands.</p> LTTng-tools - Bug #1044 (Resolved): Listing the snapshot output after deleting an outputhttps://bugs.lttng.org/issues/10442016-07-11T19:35:19ZBruno Roybruno.roy@ericsson.com
<p>LTTng version : lttng (LTTng Trace Control) 2.9.0-pre - Codename TBD (I don't have the commit, but this error is present in 2.8.1 and 2.7.2 also).<br />urcu version : 0.10~pre+bzr1197+pack28+201606291832~ubuntu16.04.1</p>
<p>Here are the command I did (started with no tracing session) :<br /><code>$ lttng create foo --snapshot<br />Default snapshot output set to: /home/bruno/lttng-traces/foo-20160711-152523<br />Snapshot mode set. Every channel enabled for that session will be set to mmap output, and default to overwrite mode.<br />$ lttng snapshot list-output<br />Snapshot output list for session foo<br /> [1] snapshot-1: /home/bruno/lttng-traces/foo-20160711-152523 (max-size: 0)<br />$ lttng snapshot del-output 1<br />Snapshot output id 1 successfully deleted for session foo<br />$ lttng snapshot list-output<br />Snapshot output list for session foo<br /> None<br />$ lttng list<br />Error: No session daemon is available<br />Error: Command error</code></p>
<p>On the 2.8.1 version I also got this error message : <code>lttng-sessiond: main.c:4180: process_client_msg: Assertion `!rcu_read_ongoing()' failed.</code><br />End result : No session daemon, and the session(s) are destroyed.</p> LTTng-tools - Bug #1006 (Resolved): Enabling an application context (both JUL and log4j) results ...https://bugs.lttng.org/issues/10062016-03-17T18:52:05ZJérémie Galarneaujeremie.galarneau@efficios.com
<p>Enabling an application context in both the log4j and jul domains results in a confirmation message of the form<br /><pre>
UST context $app.myprovider:myshortcontext added to all channels
</pre></p>
<p>The domain is printed by checking opt_kernel, while the exact domain should be checked.</p> LTTng-tools - Bug #988 (Resolved): lttng -q option not functionalhttps://bugs.lttng.org/issues/9882016-01-10T19:45:44Zjohn smithwhalajam@yahoo.com
<p>lttng -q (quiet) option doesn't work for stop, destroy, view commands (didn't test the rest of commands):<br />$ lttng -V<br />lttng (LTTng Trace Control) 2.7.0 - Herbe à Détourne</p>
<p>$ lttng stop x<br />Error: Session name not found<br />$ lttng -q stop x<br />Error: Session name not found</p>
<p>$ lttng destroy x<br />Error: Session name x not found<br />$ lttng -q destroy x<br />Error: Session name x not found</p>
<p>$ lttng create<br />Session auto-20160110-113725 created.<br />Traces will be written in /home/john/lttng-traces/auto-20160110-113725</p>
<p>$ lttng enable-event -a -u<br />All UST events are enabled in channel channel0<br />$ lttng start<br />Tracing started for session auto-20160110-113725<br />$ lttng stop<br />Waiting for data availability<br />Tracing stopped for session auto-20160110-113725<br />$ lttng view<br />Trace directory: /home/john/lttng-traces/auto-20160110-113725<br />[error] Cannot open any trace for reading.<br />[error] opening trace "/home/john/lttng-traces/auto-20160110-113725" for reading.<br />[error] none of the specified trace paths could be opened.</p>
<p>$ lttng -q view<br />[error] Cannot open any trace for reading.<br />[error] opening trace "/home/john/lttng-traces/auto-20160110-113725" for reading.<br />[error] none of the specified trace paths could be opened.</p> LTTng-tools - Bug #936 (Resolved): Disable all event usthttps://bugs.lttng.org/issues/9362015-09-09T21:21:52ZJonathan Rajotte Julienjonathan.rajotte-julien@efficios.com
<p>Disable all events on ust does not work.</p>
<pre>
lttng create mysession
lttng enable-event test -u
lttng enable-event test2 -u
lttng disable-event -u -a
lttng list mysession
killall lttng-sessiond
</pre>
<p>Result:</p>
<pre>
Spawning a session daemon
Session mysession created.
Traces will be written in /home/jonathan/lttng-traces/mysession-20150909-171434
UST event test created in channel channel0
UST event test2 created in channel channel0
Error: UST event not found
Tracing session mysession: [inactive]
Trace path: /home/jonathan/lttng-traces/mysession-20150909-171434
=== Domain: UST global ===
Buffer type: per UID
Channels:
-------------
- channel0: [enabled]
Attributes:
overwrite mode: 0
subbufers size: 131072
number of subbufers: 4
switch timer interval: 0
read timer interval: 0
trace file count: 0
trace file size (bytes): 0
output: mmap()
Events:
test2 (type: tracepoint) [enabled]
test (type: tracepoint) [enabled]
</pre><br />Looks like it works when using enable-event -u -a:<br /><pre>
Traces will be written in /home/jonathan/lttng-traces/mysession-20150909-171544
All UST events are enabled in channel channel0
All UST events are disabled in channel channel0
Tracing session mysession: [inactive]
Trace path: /home/jonathan/lttng-traces/mysession-20150909-171544
=== Domain: UST global ===
Buffer type: per UID
Channels:
-------------
- channel0: [enabled]
Attributes:
overwrite mode: 0
subbufers size: 131072
number of subbufers: 4
switch timer interval: 0
read timer interval: 0
trace file count: 0
trace file size (bytes): 0
output: mmap()
Events:
* (type: tracepoint) [disabled]
</pre><br />The behaviour on kernel/python/jul/log4j is to disable all event.
<pre>
Session mysession created.
Traces will be written in /home/jonathan/lttng-traces/mysession-20150909-171705
Kernel event test created in channel channel0
All Kernel events are disabled in channel channel0
Tracing session mysession: [inactive]
Trace path: /home/jonathan/lttng-traces/mysession-20150909-171705
=== Domain: Kernel ===
Channels:
-------------
- channel0: [enabled]
Attributes:
overwrite mode: 0
subbufers size: 262144
number of subbufers: 4
switch timer interval: 0
read timer interval: 200000
trace file count: 0
trace file size (bytes): 0
output: splice()
Events:
test (loglevel: TRACE_EMERG (0)) (type: tracepoint) [disabled]
</pre> LTTng-tools - Bug #925 (Resolved): Disabling a kernel event disables all kernel eventshttps://bugs.lttng.org/issues/9252015-09-01T19:41:49ZJérémie Galarneaujeremie.galarneau@efficios.comLTTng-tools - Feature #916 (Resolved): Add tests for shm_pathhttps://bugs.lttng.org/issues/9162015-09-01T17:59:33ZJérémie Galarneaujeremie.galarneau@efficios.comLTTng-tools - Bug #882 (Resolved): destroying one session stops tracing on all other sessionshttps://bugs.lttng.org/issues/8822015-03-02T19:01:10ZAnand Neelianand.neeli@gmail.com
<p>With lttng 2.6.0 with 0.8.6 liburcu see following issue: <br />On a multisession setup with relayd, Destroying one session is showing errors on the console and tracing of all other sessions is stopped.</p>
<p>steps to recreate are as follows<br />1) Create multiple sessions with relayd. (in below logs i have created 2 sessions)<br />2) Destroy one session and then tracing on all the sessions stops</p>
<p>(Have not check this with single session, could be happening with single session also)</p>
<p>logs<br />---------<br />node-a # lttng list<br />Available tracing sessions:<br /> 1) mys5 (tcp4://128.0.0.4:5342/ [data: 5343]) [active]<br /> Trace path: tcp4://128.0.0.4:5342/ [data: 5343]<br /> Live timer interval (usec): 2000000</p>
<pre><code>2) mysession (tcp4://128.0.0.4:5342/ [data: 5343]) [active]<br /> Trace path: tcp4://128.0.0.4:5342/ [data: 5343]<br /> Live timer interval (usec): 2000000</code></pre>
<p>Use lttng list <session_name> for more details</p>
<p>node-a # lttng list mys5<br />Tracing session mys5: [active]<br /> Trace path: tcp4://128.0.0.4:5342/ [data: 5343]</p>
<p>=== Domain: UST global ===</p>
<p>Buffer type: per PID</p>
<p>Channels:<br />-------------<br />- myc5: [enabled]</p>
<pre><code>Attributes:<br /> overwrite mode: 0<br /> subbufers size: 4096<br /> number of subbufers: 4<br /> switch timer interval: 0<br /> read timer interval: 0<br /> trace file count: 2<br /> trace file size (bytes): 2000000<br /> output: mmap()</code></pre>
<pre><code>Events:
* (type: tracepoint) [enabled] [has exclusions]</code></pre>
<p>node-a # lttng list mysession<br />Tracing session mysession: [active]<br /> Trace path: tcp4://128.0.0.4:5342/ [data: 5343]</p>
<p>=== Domain: UST global ===</p>
<p>Buffer type: per PID</p>
<p>Channels:<br />-------------<br />- mychannel: [enabled]</p>
<pre><code>Attributes:<br /> overwrite mode: 0<br /> subbufers size: 4096<br /> number of subbufers: 4<br /> switch timer interval: 0<br /> read timer interval: 0<br /> trace file count: 2<br /> trace file size (bytes): 2000000<br /> output: mmap()</code></pre>
<pre><code>Events:
* (type: tracepoint) [enabled] [has exclusions]</code></pre>
<p>node-a # lttng destroy mys5 <<<<<<<<<<<<<<<<<<<< destroying session here<br />Error: Pushing metadata<br />Error: Handling metadata request<br />Error: Health error occurred in thread_manage_consumer<br />Error: Pushing metadata<br />Error: Handling metadata request<br />Error: Health error occurred in thread_manage_consumer<br />PERROR - 04:36:15.258880 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />PERROR - 04:36:15.259520 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.260076 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />Session mys5 destroyed<br />node-a # PERROR - 04:36:15.106369 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106410 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106437 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106474 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106490 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106500 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106509 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106519 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106528 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106537 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106546 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106555 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106564 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106573 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106581 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106590 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106599 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106608 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106616 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106625 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106636 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106645 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106654 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106663 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106672 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106681 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106690 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106699 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106708 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond<br />PERROR - 04:36:15.106717 [1651/1656]: sendmsg: Broken pipe (in lttcomm_send_unix_sock() at unix.c:218)<br />Error: Asking metadata to sessiond</p>
<p>node-a # ps aux | grep lttng<br />root 1622 0.1 0.0 495020 1160 ? Ssl 04:34 0:00 lttng-relayd -o /var/tmp/lttng-traces -d<br />root 1631 0.0 0.1 854020 6360 ? Ssl 04:34 0:00 lttng-sessiond --consumerd32-path /usr/lib/lttng/libexec/lttng-consumerd --consumerd32-libdir /usr/lib/ --consumerd64-path /usr/lib64/lttng/libexec/lttng-consumerd --consumerd64-libdir /usr/lib64/ -b --no-kernel<br />root 1643 0.0 0.0 546356 3424 ? Sl 04:34 0:00 lttng-consumerd -u --consumerd-cmd-sock /var/run/lttng/ustconsumerd64/command --consumerd-err-sock /var/run/lttng/ustconsumerd64/error --group tracing<br />root 1651 0.0 0.0 64068 1852 ? Sl 04:34 0:00 lttng-consumerd -u --consumerd-cmd-sock /var/run/lttng/ustconsumerd32/command --consumerd-err-sock /var/run/lttng/ustconsumerd32/error --group tracing</p> LTTng-tools - Bug #878 (Resolved): lttng-sessiond cannot unload lttng-modules when live session e...https://bugs.lttng.org/issues/8782015-02-03T02:59:16ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<p>After the following set of commands:</p>
<p>lttng-sessiond (as root)</p>
<p>lttng create --live; lttng enable-channel -k test; lttng start</p>
<p>If we CTRL-C lttng-sessiond, this appears:</p>
<p>^CError: Unable to remove module lttng-ring-buffer-client-discard<br />Error: Unable to remove module lttng-lib-ring-buffer<br />Error: Unable to remove module lttng-tracer</p>
<p>It appears there is still a refcount held by sessiond when we try to remove the modules in this scenario. It could be a file that should have been closed but has not.</p> LTTng-tools - Feature #808 (Won't fix): Add --all to start command.https://bugs.lttng.org/issues/8082014-06-19T19:57:16ZJonathan Rajottejoraj@efficios.com
<p>Could be nice to be able to start all created session at once.</p>