lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: MONTET Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Issues on basic LTTng trace userspace (tutorial)
Date: Wed, 24 Mar 2021 15:53:14 +0000	[thread overview]
Message-ID: <PR3PR02MB620209CCED35CC62E1C8550FD1639@PR3PR02MB6202.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <20210324153255.GC344120@joraj-alpa>


[-- Attachment #1.1: Type: text/plain, Size: 3596 bytes --]

Hi Jonathan,

After having written 'sudo systemctl stop lttng-sessiond.service', the command 'sudo lttng-sessiond -vvv > /tmp/lttng-sessiond.log 2>&1' gives me nothing.

ls -la /var/run/lttng/ : Ubuntu Pastebin<https://paste.ubuntu.com/p/gjbqKkCrZK/>
groups : Ubuntu Pastebin<https://paste.ubuntu.com/p/pjVFHk7kFZ/>
lttng-sessiond -vvv > /tmp/lttng-sessiond-local.log 2>&1 : nothing
/tmp/lttng-sessiond-local.log : Ubuntu Pastebin<https://paste.ubuntu.com/p/bj38FhhVpc/>

The issue persist with the 'lttng list' command.

Best regards,

Sorry it was indeed :
The command lines entered to compile are quite the same, I just had to modify :
> this :     gcc -o hello hello.o hello-tp.o -llttng-ust -ldl
> to this : gcc -o hello hello.o hello-tp.o -L/usr/local/lib -llttng-ust -ldl
(I just wanted to focus the importance of  -L/usr/local/lib)

________________________________
De : Jonathan Rajotte-Julien <jonathan.rajotte-julien@efficios.com>
Envoyé : mercredi 24 mars 2021 16:32
À : MONTET Julien <julien.montet@reseau.eseo.fr>
Cc : lttng-dev <lttng-dev@lists.lttng.org>
Objet : Re: [lttng-dev] Issues on basic LTTng trace userspace (tutorial)

Hi Julien,

Please always keep the mailing list in CC.

> I am running 'lttng list --userspace' with the application running in another terminal (like the tutorial, and also with a while that loop on tracepoint(...).

ok.

>
> You can find here the Ubuntu paste : Ubuntu Pastebin<https://paste.ubuntu.com/p/bWw25kmSTq/>

Based on this, it seems like lttng-ust is unable to find the socket for a sessiond either
locally (for your user) [1] or a global one (root lttng-sessiond) [2].

[1] 43:  libust[207688/207690]: Info: sessiond not accepting connections to local apps socket (in ust_listener_thread() at lttng-ust-comm.c:1822)
[2] 45:  libust[207688/207689]: Info: sessiond not accepting connections to global apps socket (in ust_listener_thread() at lttng-ust-comm.c:1822)

Since you installed via the PPA, a systemd service control service is installed
that control a global (root) lttng-sessiond.

First let's stop it.
   sudo systemctl stop lttng-sessiond.service

Then in a console, again use a paste service to share the content of /tmp/lttng-sessiond.log with us

   sudo lttng-sessiond -vvv > /tmp/lttng-sessiond.log 2>&1

In another console, while the lttng-sessiond process is running, please have a look at the /var/run/lttng directory:

 ls -la /var/run/lttng/

Again use a paste service to share this with us.

Also can you provide the output of the following while using the user you are
normally using to play with lttng:

 groups

You can also try to spawn a local lttng-sessiond for the user.
  Note that a global and many local lttng-sessiond can coexist but for the sake of debugging
  we will only have one of each at a time.

Kill the root lttng-sessiond we started earlier and start a local one:

 lttng-sessiond -vvv > /tmp/lttng-sessiond-local.log 2>&1

 Note the absence of `sudo` here.

Again please share the content of /tmp/lttng-sessiond-local.log via a paste
service.

From there you can retry your experiment with the `lttng list` command.

Cheers


> The command lines entered to compile are quite the same, I just had to modify :
> this :     gcc -o hello hello.o hello-tp.o
> to this : gcc -o hello hello.o hello-tp.o -L/usr/local/lib -llttng-ust -ldl

As per the doc [3]:
    gcc -o hello hello.o hello-tp.o -llttng-ust -ldl

[3] https://lttng.org/docs/v2.12/#doc-tracing-your-own-user-application Bullet point #6

Cheers

[-- Attachment #1.2: Type: text/html, Size: 11555 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2021-03-24 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 11:29 [lttng-dev] Issues on basic LTTng trace userspace (tutorial) MONTET Julien via lttng-dev
2021-03-24 14:25 ` Jonathan Rajotte-Julien via lttng-dev
     [not found]   ` <PR3PR02MB6202F969540C279A6A171F83D1639@PR3PR02MB6202.eurprd02.prod.outlook.com>
2021-03-24 15:32     ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 15:53       ` MONTET Julien via lttng-dev [this message]
2021-03-24 16:06         ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 16:36           ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 18:55             ` MONTET Julien via lttng-dev
2021-03-24 19:00               ` Jonathan Rajotte-Julien via lttng-dev
2021-03-24 19:08                 ` MONTET Julien via lttng-dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PR3PR02MB620209CCED35CC62E1C8550FD1639@PR3PR02MB6202.eurprd02.prod.outlook.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=jonathan.rajotte-julien@efficios.com \
    --cc=julien.montet@reseau.eseo.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).