[lttng-dev] No trace files are generated

[Jérémie Galarneau]

CC'ing lttng-dev.

Looking at your logfile:

DEBUG3 [21408/21408]: Looking for a kernel consumer at these
locations: (in spawn_consumerd() at main.c:2105)
DEBUG3 [21408/21408]:   1)
/prj/x86/test/mainctrl-image-dev/packages/tools/lttng/lttng-build-root/lib/lttng/libexec/lttng-consumerd
(in spawn_consumerd() at main.c:2106)
DEBUG3 [21408/21408]:   2)
/prj/x86/test/mainctrl-image-dev/packages/tools/lttng/lttng-build-root/lib/lttng/libexec/lttng-consumerd
(in spawn_consumerd() at main.c:2107)
DEBUG3 [21408/21408]:   3)  (in spawn_consumerd() at main.c:2108)
DEBUG1 [20605/21409]: [thread] Manage consumer started (in
thread_manage_consumer() at main.c:922)
DEBUG1 [21408/21408]: Could not find any valid consumerd executable
(in spawn_consumerd() at main.c:2119)
PERROR [21408/21408]: kernel start consumer exec: No such file or
directory (in spawn_consumerd() at main.c:2224)
Error: Condition timed out. The consumer thread was never ready. Killing it

The session daemon can't find the consumer daemon executables. You
will have to point the session daemon to them manually using the
--consumerd32-path or --consumerd64-path options (depending on your
architecture).

Regards,
Jérémie

On Tue, Dec 3, 2013 at 12:11 AM, Manikandan Govindaswamy
<magov at vestas.com> wrote:
> Hi Jérémie,
>
>
>
> Thanks for your mail.
>
>
>
> Please find the attached log for the same.
>
>
>
> And I’m not putting the lttng-sessiond into background task so it’s just
> hang in the terminal, so I’ll use the other terminal to run the following
> commands
>
>
>
> #lttng list –k
>
>
>
> #lttng enable-event –k –a
>
>
>
> #lttng start
>
>
>
> #lttng stop
>
>
>
> :demsg dump
>
> [42866.350645] ring buffer relay-metadata: 0 records written, 0 records
> overrun
>
> [42866.350649] ring buffer relay-metadata, cpu -1: non-consumed data
>
> [42866.350649]   [ 8192 bytes written, 0 bytes read ]
>
> [42866.350651] ring buffer: relay-metadata, cpu -1: 4096 bytes committed
>
> [42866.350652] ring buffer: relay-metadata, cpu -1: 4096 bytes committed
>
> [42866.376269] ring buffer relay-discard, cpu 0: 48658 records written, 0
> records overrun
>
> [42866.376272] ring buffer relay-discard, cpu 0: records were lost. Caused
> by:
>
> [42866.376272]   [ 1087084 buffer full, 0 nest buffer wrap-around, 0 event
> too big ]
>
> [42866.390657] ring buffer relay-discard, cpu 0: non-consumed data
>
> [42866.390657]   [ 1048576 bytes written, 0 bytes read ]
>
> [42866.390659] ring buffer: relay-discard, cpu 0: 262144 bytes committed
>
> [42866.390660] ring buffer: relay-discard, cpu 0: 262144 bytes committed
>
> [42866.390662] ring buffer: relay-discard, cpu 0: 262144 bytes committed
>
> [42866.390663] ring buffer: relay-discard, cpu 0: 262144 bytes committed
>
> [42866.390708] ring buffer relay-discard, cpu 1: 34595 records written, 0
> records overrun
>
> [42866.390709] ring buffer relay-discard, cpu 1: records were lost. Caused
> by:
>
> [42866.390709]   [ 466072 buffer full, 0 nest buffer wrap-around, 0 event
> too big ]
>
> [42866.405004] ring buffer relay-discard, cpu 1: non-consumed data
>
> [42866.405004]   [ 1048576 bytes written, 0 bytes read ]
>
> [42866.405006] ring buffer: relay-discard, cpu 1: 262144 bytes committed
>
> [42866.405007] ring buffer: relay-discard, cpu 1: 262144 bytes committed
>
> [42866.405009] ring buffer: relay-discard, cpu 1: 262144 bytes committed
>
> [42866.405010] ring buffer: relay-discard, cpu 1: 262144 bytes committed
>
>
>
> Regards,
>
> GMK
>
>
>
> On Mon, Dec 2, 2013 at 10:32 PM, Jérémie Galarneau
> <jeremie.galarneau at efficios.com> wrote:
>
> Very interesting. Could you give me more information about your platform?
>
> I see that you loaded the kernel modules manually. Launching the
> session-daemon as root will take care of it automatically. In fact,
> this is the recommended approach since it takes care of loading the
> modules in the correct order.
>
> Could you retry to trace the kernel, but this time don't load the
> modules manually and launch the session daemon using this command:
>
> lttng-sessiond -vvv --verbose-consumer >sessiond.log 2>&1
>
> and send me the resulting sessiond.log file along with the output of
> lttng list -k and the dmesg output after stopping tracing.
>
> Please do not edit the logs as it may hide important information.
>
> Thanks,
> Jérémie
>
>
> On Mon, Dec 2, 2013 at 7:00 AM, Manikandan G <email at manikandan.co.in> wrote:
>> Hi !,
>>
>> I'm using the "Dominus Vobiscum" version of Lttng project and building for
>> my custom Linux x86_64 embedded platform.
>>
>>
>> we are using Linux 3.10.20 venila kernel for our custom Linux image.
>>
>>
>>
>> We able to build the kernel modules and tools for the same and able to
>> port
>> it on target but we dont see any trace file is generated between lttng
>> start
>> and stop.
>>
>> Please find the attached document for the detailed log of all commands and
>> system response.
>>
>> I tried giving with consumerd path and without the same to lttng-sessiond
>> but the behavior is the same.
>>
>> Please let me know what is the issue in it.
>>
>> Regards,
>> GMK
>
>
> --
> Jérémie Galarneau
> EfficiOS Inc.
> http://www.efficios.com
>
>



-- 
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com