<div dir="ltr"><div dir="ltr"><div>Thanks for response. <br></div><div>Please check console logs here: <a href="https://paste.debian.net/1054148">https://paste.debian.net/1054148</a></div><div><br></div><div>Thanks in advance for further support.</div><div>Szymon<br></div><div><table class="gmail-ajC" cellpadding="0"><tbody><tr class="gmail-ajv"><td colspan="2" class="gmail-gG"><span class="gmail-gI"></span><br></td><td colspan="2" class="gmail-gL"><span class="gmail-gI"><span></span></span><br></td></tr></tbody></table> </div></div></div><br><div class="gmail_quote"><div dir="ltr">sob., 1 gru 2018 o 01:05 Jonathan Rajotte-Julien <<a href="mailto:jonathan.rajotte-julien@efficios.com">jonathan.rajotte-julien@efficios.com</a>> napisał(a):<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Szymon,<br>
<br>
First thing to validate is if the modules compilation worked.<br>
<br>
Please give us the output of the following command:<br>
<br>
ls -la /lib/modules/`uname -r`/extra<br>
<br>
Since you installed lttng-tools via the package repo, a service was installed<br>
to spawn lttng-sessiond.<br>
<br>
You can control the service using systemctl:<br>
<br>
sudo systemctl stop lttng-sessiond.service<br>
sudo systemctl start lttng-sessiond.service<br>
sudo systemctl restart lttng-sessiond.service<br>
<br>
The output you gave us indicate that a sessiond is already running (the one<br>
started by the systemd service). Which is of no use.<br>
<br>
A colleague suggested that since you might have installed the modules package<br>
after the lttng-tools package, the modules were not present when lttng-sessiond<br>
service was started thus could not have been loaded.<br>
<br>
To test this hypothesis you can issue the following command followed by your<br>
test.<br>
<br>
sudo systemctl restart lttng-sessiond.service<br>
sleep 1<br>
sudo lttng list -k<br>
<br>
If it doesn't work, stop the service and start a sessiond in verbose mode<br>
manually.<br>
<br>
sudo systemctl stop lttng-sessiond.service<br>
sudo lttng-sessiond -vvv --verbose-consumer<br>
<br>
This should give us more information.<br>
<br>
You can use a service like <a href="https://paste.debian.net/" rel="noreferrer" target="_blank">https://paste.debian.net/</a> to give us any of the<br>
output if it ends up being more than ~20 lines.<br>
<br>
Thanks for using the mailing list instead of Stack Overflow. Once we find the<br>
problem we can update you SO thread with the solution.<br>
<br>
Cheers<br>
<br>
On Sat, Dec 01, 2018 at 12:22:05AM +0100, Szymon Rąpała wrote:<br>
> Hello,<br>
> <br>
> I'm new to lttng so I tried to follow the 'Quick Start' tutorial from<br>
> <a href="http://lttng.org" rel="noreferrer" target="_blank">lttng.org</a>.<br>
> <br>
> I have installed LTTng Stable 2.10 PPA (lttng-tools, lttng-modules-dkms,<br>
> liblttng-ust-dev). At very beginning I am facing a problem with kernel<br>
> tracking:<br>
> <br>
> ~/lttng_train$ sudo lttng create my<br>
> Session my created.<br>
> Traces will be written in /home/szymon/lttng-traces/my-20181130-222008<br>
> ~/lttng_train$ sudo lttng list --kernel<br>
> Error: Unable to list kernel events: Kernel tracer not available<br>
> Error: Command error<br>
> <br>
> Any ideas? Thanks for support!<br>
> <br>
> Additional info:<br>
> <br>
> ~/lttng_train$ dpkg -l | grep lttng<br>
> ii liblttng-ctl0:amd64<br>
> 2.10.5-1~ubuntu16.04.1 amd64 LTTng<br>
> control and utility library<br>
> ii liblttng-ust-ctl4:amd64<br>
> 2.10.2-1~ubuntu16.04.1 amd64 LTTng 2.0<br>
> Userspace Tracer (trace control library)<br>
> ii liblttng-ust-dev:amd64<br>
> 2.10.2-1~ubuntu16.04.1 amd64 LTTng 2.0<br>
> Userspace Tracer (development files)<br>
> ii liblttng-ust-python-agent0:amd64<br>
> 2.10.2-1~ubuntu16.04.1 amd64 LTTng 2.0<br>
> Userspace Tracer (Python agent native library)<br>
> ii liblttng-ust0:amd64<br>
> 2.10.2-1~ubuntu16.04.1 amd64 LTTng 2.0<br>
> Userspace Tracer (tracing libraries)<br>
> ii lttng-modules-dkms<br>
> 2.10.8-1~ubuntu16.04.1 all Linux Trace<br>
> Toolkit (LTTng) kernel modules (DKMS)<br>
> ii lttng-tools<br>
> 2.10.5-1~ubuntu16.04.1 amd64 LTTng<br>
> control and utility programs<br>
> <br>
> ~$ uname -a<br>
> Linux szymon 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC<br>
> 2017 x86_64 x86_64 x86_64 GNU/Linux<br>
> <br>
> ~$ lsb_release -a<br>
> No LSB modules are available.<br>
> Distributor ID: Ubuntu<br>
> Description: Ubuntu 16.04.5 LTS<br>
> Release: 16.04<br>
> Codename: xenial<br>
> <br>
> ~/lttng_train$ ps aux | grep lttng-sessiond<br>
> root 7862 0.0 0.3 859960 10880 ? Ssl 19:12 0:00<br>
> /usr/bin/lttng-sessiond<br>
> szymon 14853 0.0 0.0 15440 936 pts/1 S+ 22:21 0:00 grep<br>
> --color=auto lttng-sessiond<br>
> <br>
> ~/lttng_train$ lsmod | grep lttng<br>
> ~/<br>
> <br>
> ~/lttng_train$ sudo lttng-sessiond -vvv<br>
> DEBUG1 - 00:16:41.328643679 [16578/16578]: [sessiond configuration]<br>
> DEBUG1 - 00:16:41.328715142 [16578/16578]: verbose: 3<br>
> DEBUG1 - 00:16:41.328723618 [16578/16578]: verbose consumer: 0<br>
> DEBUG1 - 00:16:41.328729230 [16578/16578]: quiet mode: False<br>
> DEBUG1 - 00:16:41.328735428 [16578/16578]: agent_tcp_port:<br>
> [5345, 5354]<br>
> DEBUG1 - 00:16:41.328741084 [16578/16578]: application socket timeout: 5<br>
> DEBUG1 - 00:16:41.328761096 [16578/16578]: no-kernel: False<br>
> DEBUG1 - 00:16:41.328776829 [16578/16578]: background: False<br>
> DEBUG1 - 00:16:41.328788328 [16578/16578]: daemonize: False<br>
> DEBUG1 - 00:16:41.328800092 [16578/16578]: signal parent on start: False<br>
> DEBUG1 - 00:16:41.328812153 [16578/16578]: tracing group name:<br>
> tracing<br>
> DEBUG1 - 00:16:41.328823395 [16578/16578]: kmod_probe_list: None<br>
> DEBUG1 - 00:16:41.328834022 [16578/16578]: kmod_extra_probe_list: None<br>
> DEBUG1 - 00:16:41.328848328 [16578/16578]: rundir:<br>
> /var/run/lttng<br>
> DEBUG1 - 00:16:41.328857048 [16578/16578]: application socket path:<br>
> /var/run/lttng/lttng-ust-sock-7<br>
> DEBUG1 - 00:16:41.328866302 [16578/16578]: client socket path:<br>
> /var/run/lttng/client-lttng-sessiond<br>
> DEBUG1 - 00:16:41.328881494 [16578/16578]: wait shm path:<br>
> /lttng-ust-wait-7<br>
> DEBUG1 - 00:16:41.328890337 [16578/16578]: health socket path:<br>
> /var/run/lttng/sessiond-health<br>
> DEBUG1 - 00:16:41.328896087 [16578/16578]: LTTNG_UST_CLOCK_PLUGIN: None<br>
> DEBUG1 - 00:16:41.328902562 [16578/16578]: pid file path:<br>
> /var/run/lttng/lttng-sessiond.pid<br>
> DEBUG1 - 00:16:41.328909781 [16578/16578]: lock file path:<br>
> /var/run/lttng/lttng-sessiond.lck<br>
> DEBUG1 - 00:16:41.328916938 [16578/16578]: session load path: None<br>
> DEBUG1 - 00:16:41.328924592 [16578/16578]: agent port file path:<br>
> /var/run/lttng/agent.port<br>
> DEBUG1 - 00:16:41.328936395 [16578/16578]: consumerd32 path:<br>
> /var/run/lttng/ustconsumerd32<br>
> DEBUG1 - 00:16:41.328947517 [16578/16578]: consumerd32 bin path:<br>
> Unknown<br>
> DEBUG1 - 00:16:41.328961683 [16578/16578]: consumerd32 lib dir:<br>
> Unknown<br>
> DEBUG1 - 00:16:41.328970009 [16578/16578]: consumerd32 err unix sock<br>
> path:/var/run/lttng/ustconsumerd32/error<br>
> DEBUG1 - 00:16:41.328977730 [16578/16578]: consumerd32 cmd unix sock<br>
> path:/var/run/lttng/ustconsumerd32/command<br>
> DEBUG1 - 00:16:41.328985023 [16578/16578]: consumerd64 path:<br>
> /var/run/lttng/ustconsumerd64<br>
> DEBUG1 - 00:16:41.328992714 [16578/16578]: consumerd64 bin path:<br>
> /usr/lib/x86_64-linux-gnu/lttng/libexec/lttng-consumerd<br>
> DEBUG1 - 00:16:41.329005793 [16578/16578]: consumerd64 lib dir:<br>
> /usr/lib/x86_64-linux-gnu<br>
> DEBUG1 - 00:16:41.329017089 [16578/16578]: consumerd64 err unix sock<br>
> path:/var/run/lttng/ustconsumerd64/error<br>
> DEBUG1 - 00:16:41.329028919 [16578/16578]: consumerd64 cmd unix sock<br>
> path:/var/run/lttng/ustconsumerd64/command<br>
> DEBUG1 - 00:16:41.329040967 [16578/16578]: kconsumerd path:<br>
> /var/run/lttng/kconsumerd<br>
> DEBUG1 - 00:16:41.329053218 [16578/16578]: kconsumerd err unix sock<br>
> path: /var/run/lttng/kconsumerd/error<br>
> DEBUG1 - 00:16:41.329064330 [16578/16578]: kconsumerd cmd unix sock<br>
> path: /var/run/lttng/kconsumerd/command<br>
> DEBUG3 - 00:16:41.329076040 [16578/16578]: Creating LTTng run<br>
> directory: /var/run/lttng (in create_lttng_rundir() at main.c:5306)<br>
> Error: A session daemon is already running.<br>
> DEBUG1 - 00:16:41.329161207 [16578/16578]: Cleaning up options (in<br>
> sessiond_cleanup_options() at main.c:648)<br>
> DEBUG1 - 00:16:41.329178082 [16578/16578]: Destroying run_as worker<br>
> (in run_as_destroy_worker() at runas.c:709)<br>
> <br>
> Regards,<br>
> <br>
> Simon<br>
<br>
> _______________________________________________<br>
> lttng-dev mailing list<br>
> <a href="mailto:lttng-dev@lists.lttng.org" target="_blank">lttng-dev@lists.lttng.org</a><br>
> <a href="https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev" rel="noreferrer" target="_blank">https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a><br>
<br>
<br>
-- <br>
Jonathan Rajotte-Julien<br>
EfficiOS<br>
</blockquote></div>