LTTng bugs repository: Issueshttps://bugs.lttng.org/https://bugs.lttng.org/themes/lttng/favicon/a.ico?14249722912015-07-07T14:09:29ZLTTng bugs repository
Redmine LTTng-tools - Bug #892 (Resolved): lttng commands stuck when option --set-url is used to send the...https://bugs.lttng.org/issues/8922015-07-07T14:09:29Zvinay kambamvinaykambam@gmail.com
<p>lttng commands stuck when option --set-url is used to send the traces over network ,Suspecting if the relay daemon is unable to process the request from session daemon.When we restarted the relay daemon ,we haven't seen this problem again</p>
<p>I have few questions in regard to this <br />-Does the relay daemon started on the remote machine has the limitation to handle the number of connections ?<br />-Does relay daemon cleans up the connection if there happens an unordered crash of the target on which session daemon is started ?<br />-The netstat's output has the queued packets at the relay daemon side , interestingly there are no lttng sessions on the target</p>
<p>The netstat output is as</p>
<p>tcp 0 0 0.0.0.0:5342 0.0.0.0:* LISTEN <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:36740 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:40543 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:43537 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:43347 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:45642 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:45433 ESTABLISHED <br />tcp 33 0 137.58.215.17:5342 10.74.58.20:57832 CLOSE_WAIT <br />tcp 32 0 137.58.215.17:5342 10.67.29.116:53648 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:54402 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:55397 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:34960 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:37913 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:43167 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:51673 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:48492 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 172.31.98.221:39518 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:47521 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:51916 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.58.20:48219 ESTABLISHED <br />tcp 33 0 137.58.215.17:5342 10.74.58.20:44167 CLOSE_WAIT <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:47477 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 137.58.191.89:34615 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.67.30.52:50288 ESTABLISHED <br />tcp 32 0 137.58.215.17:5342 10.74.59.170:55543 ESTABLISHED <br />tcp 89 0 137.58.215.17:5342 10.74.58.20:37882 CLOSE_WAIT</p>
<p>-when the relay daemon is in this state , we are unable to create new sessions to send the traces to the same daemon and lttng commands stuck</p>
<p>In our case , relay daemon was started few days ago, It was working fine collecting traces from sessions on different machines and some how it went to this "bad" state.</p>
<p>-Is it due to the reason that the relay daemon was started and being run for few days?</p>
<p>we are using lttng 2.6 version</p>
<ol>
<li>which lttng<br />/usr/bin/lttng</li>
</ol>
<ol>
<li>lttng --version<br />lttng (LTTng Trace Control) 2.6.0 - Gaia - v2.6.0</li>
</ol>
<p>Could you please find the root cause for this issue and a workaround ?</p>