From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: "François Belias" <beliasossim@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Error: Unable to list kernel events: Kernel tracer not available
Date: Fri, 12 Jul 2024 16:01:38 -0400 [thread overview]
Message-ID: <870f6359-c0aa-48bb-9964-710bd0ea9cb0@efficios.com> (raw)
In-Reply-To: <CAHD10UjhpBQdXm5wDxSDdjYojBKXwbLKaom+EmeqNrWheLkQJg@mail.gmail.com>
Hi François,
On 7/12/24 3:52 PM, François Belias wrote:
> Hi Kienan,
> Yes, `lttng-sessiond` is being run by the root user. I have shared a
> screenshot of the result when I ran the `lttng-sessiond -vvv` command,
> but I don't think the kernel modules are loaded.
> thanks
>
>
There are two issues in the screenshot you attached:
1. You are not starting lttng-sessiond as the root user, you are
running it as the user 'philippe'
2. The error in the screenshot indicates that there is already
another lttng-sessiond running.
Could you please stop all of the lttng-sessionds, then run
`lttng-sessiond -vvv` as the root user?
thanks,
kienan
> Le ven. 12 juill. 2024, à 15 h 24, Kienan Stewart <kstewart@efficios.com
> <mailto:kstewart@efficios.com>> a écrit :
>
> Hi François,
>
> On 7/12/24 2:53 PM, François Belias via lttng-dev wrote:
> > Hello,
> >
> > When I run the command `sudo lttng list -k`, I get the following
> error:
>
> To check a few things:
>
> * Is lttng-sessiond being run by the root user?
> * If you run lttng-session with the "-vvv" option, are there
> messages
> related to loading the kernel modules?
> * Once the lttng-sessiond is started, you can check to see if the
> kernel modules have been loaded by running the following command:
>
> ```
> lsmod | grep lttng
> ```
>
> thanks,
> kienan
>
> >
> > ```
> > Error: Unable to list kernel events: Kernel tracer not available.
> > ```
> >
> > I am trying to build LTTng-modules from the source. I followed
> the steps
> > from this website: [LTTng
> >
> Documentation](https://lttng.org/docs/v2.13/#doc-building-from-source <https://lttng.org/docs/v2.13/#doc-building-from-source>
> > <https://lttng.org/docs/v2.13/#doc-building-from-source
> <https://lttng.org/docs/v2.13/#doc-building-from-source>>), but I still
> > encounter this error. Can someone help me resolve this issue?
> >
> > Thanks.
> >
> > _______________________________________________
> > lttng-dev mailing list
> > lttng-dev@lists.lttng.org <mailto:lttng-dev@lists.lttng.org>
> > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
> <https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev>
>
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2024-07-12 20:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 18:53 François Belias via lttng-dev
2024-07-12 19:24 ` Kienan Stewart via lttng-dev
2024-07-12 19:52 ` François Belias via lttng-dev
2024-07-12 19:57 ` François Belias via lttng-dev
2024-07-12 20:01 ` Kienan Stewart via lttng-dev [this message]
2024-07-12 20:25 ` François Belias 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=870f6359-c0aa-48bb-9964-710bd0ea9cb0@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=beliasossim@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