Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: tom.deneau@amd.com (Deneau, Tom)
Subject: [lttng-dev] Error: Kernel create channel failed
Date: Wed, 31 May 2017 23:18:07 +0000	[thread overview]
Message-ID: <CY4PR12MB19127ABD925A3E0EE70AED399BF10@CY4PR12MB1912.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20170531183000.vh5y266by4hmtmb3@psrcode-TP-X230>

Thanks, the new packages installed fine.
My original problem I solved by killing lttng-sessiond and restarting it...

-- Tom


-----Original Message-----
From: Jonathan Rajotte-Julien [mailto:jonathan.rajotte-julien@efficios.com] 
Sent: Wednesday, May 31, 2017 1:30 PM
To: Deneau, Tom <tom.deneau at amd.com>
Cc: lttng-dev at lists.lttng.org
Subject: Re: [lttng-dev] Error: Kernel create channel failed

Hi,

On Tue, May 30, 2017 at 02:15:47PM +0000, Deneau, Tom wrote:
> I seem to have gotten my lttng into a state where kernel tracing does not work.
> I have tried uninstalling and reinstalling packages with no luck and also building from source.
> Any suggestions welcome.
> 
> My distro is Ubuntu 16.04 but the kernel is 4.10.0-20-generic.

Are you using the hwe package? (linux-generic-hwe-16.04-edge)

> 
> I have installed 2.9 using
> apt install linux-tools-generic dkmso

If using the hwe package you probably want to use the equivalent linux-tool-generic hwe package.

> apt-add-repository ppa:lttng/stable-2.9 apt-get update apt install -y 
> lttng-tools liblttng-ust-dev  liblttng-ust-agent-java  
> python3-lttngust lttng-modules-dkms wget 
> http://ftp.us.debian.org/debian/pool/main/l/lttng-modules/lttng-module
> s-dkms_2.9.1-1_all.deb dpkg -i lttng-modules-dkms_2.9.1-1_all.deb

I guess that this was to "fix" the installation error you had with installing lttng-modules-dkms. Reporting the installation issue would have been more straightforward.

The ppa packages were updated yesterday to fix the issue on installation.
Please update (apt update/upgrade) all lttng related packages. Also make sure to install babeltrace (apt install babeltrace) with updated libbabeltrace* dependencies.

> apt install -y babeltrace python3-babeltrace

> 
> After lttng create test, I then try
> 
> # lttng -vvv enable-channel k -k --num-subbuf 64 --subbuf-size 512k
> DEBUG1 - 08:27:54.415995 [13972/13972]: Channel subbuf num set to 64 
> (in cmd_enable_channels() at commands/enable_channels.c:420)
> DEBUG1 - 08:27:54.416045 [13972/13972]: Channel subbuf size set to 
> 524288 (in cmd_enable_channels() at commands/enable_channels.c:384)
> DEBUG2 - 08:27:54.416080 [13972/13972]: Config file path found: /root 
> (in _get_session_name() at utils.c:63)
> DEBUG1 - 08:27:54.416087 [13972/13972]: Session name found: test (in 
> _get_session_name() at utils.c:64)
> DEBUG1 - 08:27:54.416099 [13972/13972]: Enabling channel k (in 
> enable_channel() at commands/enable_channels.c:225)
> DEBUG1 - 08:27:54.416129 [13972/13972]: LSM cmd type : 5 (in 
> send_session_msg() at lttng-ctl.c:135)
> Error: Channel k: Kernel create channel failed (session test)
> Error: Command error
> DEBUG1 - 08:27:54.416479 [13972/13972]: Clean exit (in clean_exit() at 
> lttng.c:149)

I tested ppa stable 2.9 installation on both vanilla 16.04 and 16.04 with the 4.10.0-21-generic kernel provided by linux-generic-hwe-16.04-edge. Both works with the updated ppa (update performed by Michael Jeanson).

Only had a minor dependency issue with babeltrace but it was fixed by reinstalling it.

Cheers

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

--
Jonathan Rajotte-Julien
EfficiOS


      reply	other threads:[~2017-05-31 23:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 14:15 Deneau, Tom
2017-05-31 18:30 ` Jonathan Rajotte-Julien
2017-05-31 23:18   ` Deneau, Tom [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=CY4PR12MB19127ABD925A3E0EE70AED399BF10@CY4PR12MB1912.namprd12.prod.outlook.com \
    --to=tom.deneau@amd.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