Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: David Aldrich via lttng-dev <lttng-dev@lists.lttng.org>
To: Kienan Stewart <kstewart@efficios.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: Not capturing ust events
Date: Thu, 8 May 2025 18:59:45 +0100	[thread overview]
Message-ID: <CAJK_iehC35W7LUWkR4b-+TEuJTOTngzJ_0sV7LSvBT6WcDPN4w@mail.gmail.com> (raw)
In-Reply-To: <0e6f9c3b-8daa-43ae-a3ee-6d7917b05b2e@efficios.com>

Hi Kienan

Thanks again for replying.

> Glad you caught that. I had assumed it was linked in :)

Yes, I should have spotted that earlier!

> Assuming the user you are running the `lttng` commands with is a member
> of the tracing group and a root lttng-sessiond is running, a complete
> example might look like:
>
> ```
> lttng create my_proj
> lttng enable-event --userspace 'lttng_ust_tracef:*' # this will
> automatically create a channel if one doesn't exist in the session
> lttng enable-channel --kernel --session my_proj kernel_channel # [1]
> lttng enable-event --kernel --all --channel kernel_channel --session
> my_proj # [2]
> lttng start
> ./my_app
> lttng stop
> lttng view
> ```

I now see:

$ lttng enable-channel --kernel --session my_proj kernel_channel
Error: Channel kernel_channel: Tracing the kernel requires a root
lttng-sessiond daemon, as well as "tracing" group membership or root
user ID for the lttng client (session my_proj)

I am a member of the tracing group, however I need to understand how
to configure the daemon. I'll have another look at the docs.

Best regards
David

      reply	other threads:[~2025-05-08 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 16:50 David Aldrich via lttng-dev
2025-05-08 13:51 ` Kienan Stewart via lttng-dev
2025-05-08 17:02   ` David Aldrich via lttng-dev
2025-05-08 17:25     ` Kienan Stewart via lttng-dev
2025-05-08 17:59       ` David Aldrich via lttng-dev [this message]

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=CAJK_iehC35W7LUWkR4b-+TEuJTOTngzJ_0sV7LSvBT6WcDPN4w@mail.gmail.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=david.aldrich.ntml@gmail.com \
    --cc=kstewart@efficios.com \
    /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