https://bugs.lttng.org/https://bugs.lttng.org/themes/lttng/favicon/a.ico?14249722912013-03-27T16:14:35ZLTTng bugs repositoryLTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12182013-03-27T16:14:35ZDavid Goulet
<ul></ul><p>This works well here. After the stop, you should get your data.</p>
<p>Note that in your case you use "*" as a wild card but with double quotes. That may cause your shell to replace the star with some unwanted input.</p>
<p>$ lttng enable-event -s $TC "com*" -u -c chan1</p>
<p>That would explain why the trace is valid but does not have anything in it. If not, let me know.</p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12192013-03-27T16:27:30ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<ul></ul><p>The proper usage for wildcard is to use single quote, not double,<br />indeed.</p>
<p>'*' rather than "*".</p>
<p>Thanks,</p>
<p>Mathieu</p>
<p>-- <br />Mathieu Desnoyers<br />EfficiOS Inc.<br /><a class="external" href="http://www.efficios.com">http://www.efficios.com</a></p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12202013-03-27T16:58:59ZTan le trantan.dung.le.tran@ericsson.com
<ul></ul><p>Negative !</p>
<p>The reason I used "com*" is to get a quick file size increase.<br />The problem has been spotted when using a single specific tracepoint:<br /> com_ericsson_cba_trace_testapp_lowtraf:OnePerSecB</p>
<p>Can we safely assume that "com*" has been interpreted properly<br />by lttng because the corresponding tracepoints are shown in the<br />metadata file ? Otherwise, none of the tracepoints should be <br />present in that file, isn't it ?</p>
<p>I tried with 'com*' anyway and same problem. no Data .</p>
<p>Will try to run again with verbose mode... will update later.</p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12212013-03-27T17:23:49ZDavid Goulet
<ul></ul><p>Can I have the TestApp (tarball) so I can test the same exact use case because I'm unable to have an empty trace here with the exact command you are using.</p>
<p>Thanks!</p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12222013-03-27T19:20:02ZTan le trantan.dung.le.tran@ericsson.com
<ul><li><strong>File</strong> <a href="/attachments/162">ses9_terminal_log.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/162/ses9_terminal_log.log">ses9_terminal_log.log</a> added</li><li><strong>File</strong> <a href="/attachments/163">ses9_sessionD_verbose.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/163/ses9_sessionD_verbose.log">ses9_sessionD_verbose.log</a> added</li><li><strong>File</strong> <a href="/attachments/164">TestApp_type1.tar</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/164/TestApp_type1.tar">TestApp_type1.tar</a> added</li></ul><p>We have rerun the scenario with "sessionD -vvv".</p>
<p>The following files are attached:<br /> "ses9_terminal_log.log" <br /> Terminal log file when session "ses9" is being created, start, stop, destroy.<br /> "ses9_sessionD_verbose.log" <br /> Corresponding sessiond -vvv output<br /> "TestApp_type1.tar" the requested tarball of TestApp_type1 used in the test.</p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12252013-03-27T20:16:40ZTan le trantan.dung.le.tran@ericsson.com
<ul></ul><p>I have rerun the case using the "hello" program under "lttng-ust/tests/hello-static-lib" <br />with the instructions steps below and the problem is still the same. I could not get<br />any log data. Only metadata.</p>
<pre><code>export TC=ses102</code></pre>
<pre><code>ps -ef |egrep 'lttng'<br /> lttng-relayd -C tcp://0.0.0.0:53000 -D tcp://0.0.0.0:53001 -o /cluster/temp/log/$TC &</code></pre>
<pre><code>lttng create $TC -U net://192.168.0.1:53000:53001/./<br /> lttng list<br /> sleep 1<br /> lttng enable-channel chan1 -u --buffers-uid <br /> sleep 1<br /> lttng enable-event -s $TC -u -c chan1 ust_tests_hello:tptest_sighandler<br /> sleep 1<br /> lttng list $TC<br /> sleep 1<br /> lttng start; <br /> sleep 1<br /> lttng list $TC<br /> sleep 1<br /> netstat -etanp | head -n 2 ; netstat -etanp |egrep 'lttng'<br /> sleep 1<br /> lttng list -u<br /> sleep 1<br /> /cluster/temp/tdlt/hello 20 &<br /> sleep 1<br /> lttng list -u<br /> dir -R /cluster/temp/log/$TC<br /> sleep 22<br /> dir -R /cluster/temp/log/$TC <br /> lttng stop<br /> sleep 1<br /> dir -R $TC/SC-1/ust/uid/0/64-bit <br /> lttng destroy $TC<br /> sleep 1<br /> dir -R $TC/SC-1/ust/uid/0/64-bit <br /> pkill relayd<br /> ps -ef |egrep 'lttng'<br /> pkill TestApp<br /> lttng list -u<br /> babeltrace $TC/SC-1/ust/uid/0/64-bit</code></pre>
<p>I am still using the same set of lttng commits indicated at the beginning of this report.</p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12262013-03-27T20:23:46ZDavid Goulet
<ul></ul><p>I can't get an empty trace here... I used "com*" and after only "com_ericsson_cba_trace_testapp_lowtraf:OnePerSecB:" with the application started before and after the lttng commands and I'm unable to get an empty trace. (at the same commit as you are in all projects).</p>
<p>Is your system 32 bit?</p>
<p>Second thing, can you set the application in debug mode using LTTNG_UST_DEBUG=1 ./TestApp_type1 .... (or simply hello). Also, add "--verbose-consumer" to the session daemon logs so we can look if the consumer is the problem.</p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12272013-03-27T21:44:23ZTan le trantan.dung.le.tran@ericsson.com
<ul><li><strong>File</strong> <a href="/attachments/165">ses13_withUST_DEBUG.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/165/ses13_withUST_DEBUG.log">ses13_withUST_DEBUG.log</a> added</li><li><strong>File</strong> <a href="/attachments/166">ses13_sessionD_consumerD_verbose.log</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/166/ses13_sessionD_consumerD_verbose.log">ses13_sessionD_consumerD_verbose.log</a> added</li></ul><p>We are using a 64 bit system.</p>
<p>I have run a new session with the info you requested (ses13).<br />Logs are attached.</p>
<p>From the consumer output, there are plenty of complaints about:<br /> Reserving sub buffer failed (everything is normal, it is due to concurrency) [ret: -11] (in lttng_ustconsumer_read_subbuffer() at ust-consumer.c:1188)</p> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12282013-03-28T18:41:46ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<ul><li><strong>Project</strong> changed from <i>LTTng-tools</i> to <i>LTTng-UST</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Confirmed</i></li><li><strong>Assignee</strong> set to <i>Mathieu Desnoyers</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Critical</i></li></ul> LTTng-UST - Bug #487: Per UID buffer: Can not see any data being loggedhttps://bugs.lttng.org/issues/487?journal_id=12292013-03-28T18:52:17ZMathieu Desnoyersmathieu.desnoyers@efficios.com
<ul><li><strong>Status</strong> changed from <i>Confirmed</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Fix: tracepoint instrumentation constructor order issue If the linker decides to run a construct..." href="https://bugs.lttng.org/projects/lttng-ust/repository/lttng-ust/revisions/46c881a7d6839761e3371a93ba29e7a0202bcd03">46c881a7d6839761e3371a93ba29e7a0202bcd03</a>.</p>