[lttng-dev] Probleme with live session on LTTng 2.7.0
Jonathan Rajotte-Julien
jonathan.rajotte-julien at efficios.com
Fri Jun 8 10:27:44 EDT 2018
Hi Thierry,
I also forgot to mention that there might some confusion on your end regarding the "live" mode.
LTTng have two "main" network streaming mode, normal streaming and live streaming.
The normal streaming is useful in scenario where you perform analysis after all tracing is done.
This is the mode you are currently using in your example.
The "live" mode is mostly used when you are interesting in consuming trace events as soon as possible as they are produced using Babeltrace.
Which mode do you plan on using?
Cheers
----- Original Message -----
> From: "Jonathan Rajotte-Julien" <jonathan.rajotte-julien at efficios.com>
> To: "BADEUIL Thierry" <thierry.badeuil at thalesgroup.com>
> Cc: "lttng-dev" <lttng-dev at lists.lttng.org>
> Sent: Friday, June 8, 2018 10:10:44 AM
> Subject: Re: [lttng-dev] Probleme with live session on LTTng 2.7.0
> Hi Thierry,
>
> ----- Original Message -----
>> From: "BADEUIL Thierry" <thierry.badeuil at thalesgroup.com>
>> To: lttng-dev at lists.lttng.org
>> Sent: Friday, June 8, 2018 9:45:44 AM
>> Subject: [lttng-dev] Probleme with live session on LTTng 2.7.0
>
>> Dear all,
>>
>>
>>
>> I have problem with LTTng in live mode : I would like to send trace with TCP
>> from my target to a Linux Computer. I will use babletrace on the Linux
>> Computer.
>
> LTTng 2.7 is not officially supported by the opensource community anymore.
> Please upgrade if possible.
>
>>
>>
>>
>> Here is what I try to do on my target with LTTng 2.7.0 :
>>
>> o Lttng create test –U net://192.168.0.1:5151
>
> Did you start a lttng-relayd process on the 192.168.0.1 host? How was it
> started?
>
>>
>> o Lttng enable-event –k sched_switch
>>
>> o I got an error : “Error: sched_switch: Unable to connect to lttng-relayd
>> (channel channel0, session test)”
>>
>>
>>
>> Then I tried :
>>
>> o Lttng-relayd –d
>
> Was this done on the same machine where you run "lttng create" or on the
> 192.168.0.1 host?
>
>>
>> o Lttng create test –U net://192.168.0.1:5151
>
> 5151 is not the default port for lttng-relayd. Unless you specified custom port
> at lttng-relayd start, the default port are 5342:5343:5344.
> See the lttng-relayd man page for more information.
>
>>
>> o Lttng enable-event –k sched_switch
>>
>> o I got the same error
>>
>>
>>
>> The IP address of the Linux Computer is 192.168.0.1 and the port 5151 is
>> open.
>>
>>
>>
>> Why ?
>>
>>
>>
>> Thierry BADEUIL
>>
>> THALES COMMUNICATIONS
>>
>> ( : +33 1 46 133 591
>>
>> È : +33 6 85 51 28 16
>>
>> * : <mailto:thierry.badeuil at fr.thalesgroup.com>
>> thierry.badeuil at thalesgroup.com
>>
>>
>>
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev at lists.lttng.org
>> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
More information about the lttng-dev
mailing list