[lttng-dev] Lttng state dump traces not present in 13.04 Ubuntu server distribution
alexmonthy at voxpopuli.im
Thu Jan 23 13:38:32 EST 2014
Can you confirm if the updated "lttng-modules-dkms" package really
installed successfully? (You can uninstall/reinstall it and check in the
output.) The problem with DKMS packages is that the .deb can build fine
on the builder, but it fails to install on the user's machine depending
on the kernel version, etc.
What may happen is that the package failed to install, and you are still
using the old version of the lttng-modules that come with the default
Ubuntu kernel, which may not have statedump events. In that case I would
suggest installing the modules manually from source.
Unfortunately, there is no easy way to query which version of the
modules are running with the "lttng" command.
On 14-01-23 05:30 AM, Krishanth TJ wrote:
> Dear All,
> Recently when I tried to use lttng on Ubuntu 13.04 server distribution, I
> noticed that statedump traces were not present.
> Installed lttng-tools, lttng-modules-dkms, babeltrace from
> deb http://ppa.launchpad.net/lttng/ppa/ubuntu raring main
> deb-src http://ppa.launchpad.net/lttng/ppa/ubuntu raring main
> lttng version 2.3.0
> babeltrace 1.0.3
> The procedure followed was
> # lttng create newsession
> # lttng enable-event -a -k
> # lttng start
> # Do something
> # lttng stop
> # lttng destroy
> # babeltrace <session>
> Any help would be appreciated.
> Noticed that 3.2.0-39-generic has statedump traces.
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
More information about the lttng-dev