Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: "François Belias via lttng-dev" <lttng-dev@lists.lttng.org>
To: Kienan Stewart <kstewart@efficios.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 15:57:43 -0400	[thread overview]
Message-ID: <CAHD10UjwgvHhMBDCqi4YHEzMec-SL=xCfU=scLnB60_S8C4KkA@mail.gmail.com> (raw)
In-Reply-To: <CAHD10UjhpBQdXm5wDxSDdjYojBKXwbLKaom+EmeqNrWheLkQJg@mail.gmail.com>


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

sorry I forgot the last part of your previous email. This is the result of
the command lsmod | grep lttng.

Le ven. 12 juill. 2024, à 15 h 52, François Belias <beliasossim@gmail.com>
a écrit :

> 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
>
>
> Le ven. 12 juill. 2024, à 15 h 24, Kienan Stewart <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>), but I still
>> > encounter this error. Can someone help me resolve this issue?
>> >
>> > Thanks.
>> >
>> > _______________________________________________
>> > lttng-dev mailing list
>> > lttng-dev@lists.lttng.org
>> > https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>>
>

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

[-- Attachment #2: Screenshot from 2024-07-12 15-57-15.png --]
[-- Type: image/png, Size: 20071 bytes --]

[-- Attachment #3: 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:[~2024-07-12 20:28 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 [this message]
2024-07-12 20:01     ` Kienan Stewart via lttng-dev
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='CAHD10UjwgvHhMBDCqi4YHEzMec-SL=xCfU=scLnB60_S8C4KkA@mail.gmail.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