From: veredz72@gmail.com (Zvi Vered)
Subject: [lttng-dev] lttng-tools-2.10.6: Spawning consumerd failed
Date: Wed, 15 May 2019 16:42:57 +0300 [thread overview]
Message-ID: <CABRndgxNtLbXZ0peWNm7qq_kxT4fY_PspgJ6hR=H82r3o8Nhmw@mail.gmail.com> (raw)
In-Reply-To: <20190514180433.GB10361@joraj-alpa>
Hi Jonathan,
I'm not using buildroot nor Yokto.
In order to build lttng-tools I ran:
./configure --prefix=/64_sw/git/zvi_vered/MY_PROJ/linux4.9.20/boot/rootfs
make
make install
This path contains a complete root file system (based on busybox) that is
later copied to my target.
On the target I ran:
lttng-sessiond -vvv --verbose-consumer
and got:
....
I/O warning : failed to load external entity
"/64_sw/git/zvi_vered/MY_PROJ/linux4.9.20/boot/rootfs/share/xml/lttng/session.xsd"
XML Error: Failed to locate the main schema resource at
'/64_sw/git/zvi_vered/MY_PROJ/linux4.9.20/boot/rootfs/share/xml/lttng/session.xsd'.
Error: XSD parsing failed
Error: Session load failed: Invalid session configuration
DEBUG1 - 00:10:36.746330272 [1476/1618]: Accepting client command ... (in
thread_manage_clients() at main.c:4374)
Then I ran:
lttng create my-kernel-session
and got:
....
DEBUG3 - 00:11:41.869875832 [1628/1628]: Looking for a kernel consumer at
these locations: (in spawn_consumerd() at main.c:2429)
DEBUG3 - 00:11:41.869901726 [1628/1628]: 1) NULL (in
spawn_consumerd() at main.c:2430)
DEBUG3 - 00:11:41.869908520 [1628/1628]: 2)
/64_sw/git/zvi_vered/MY_PROJ/linux4.9.20/boot/rootfs/lib/lttng/libexec/lttng-consumerd
(in spawn_consumerd() at main.c:2431)
DEBUG3 - 00:11:41.869915959 [1628/1628]: 3)
/64_sw/git/zvi_vered/MY_PROJ/linux4.9.20/boot/rootfs/lib/lttng/libexec/lttng-consumerd
(in spawn_consumerd() at main.c:2432)
DEBUG1 - 00:11:41.869971468 [1628/1628]: Could not find any valid consumerd
executable (in spawn_consumerd() at main.c:2444)
Error: Spawning consumerd failed
I double checked: The target has /lib/lttng-libexec/lttng-consumerd
But it looks for it in:
/64_sw/git/zvi_vered/MY_PROJ/linux4.9.20/boot/rootfs/lib/lttng/libexec ]
What is missing in my configuration ?
Thank you,
Zvika
On Tue, May 14, 2019 at 9:04 PM Jonathan Rajotte-Julien <
jonathan.rajotte-julien at efficios.com> wrote:
> >
> > >
> > >
> > > I'm running under a 32 bit (x86) vanilla, 4.9.20 kernel with busybox
> > > with the following lttng versions:
>
> I took some time to at least test on a 32 bit system (buildroot) just in
> case
> and everything seems to be working fine on a base installation.
>
> The log from lttng-sessiond should provides more information on why we
> fail to
> spawn the consumerd (wrong path, etc.).
>
> Cheers
>
> --
> Jonathan Rajotte-Julien
> EfficiOS
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20190515/88b036cc/attachment.html>
next parent reply other threads:[~2019-05-15 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABRndgyrxUfZqtcu=4Y7U8rvjpBa=0AqcDCkvU3UMxixRfQCoQ@mail.gmail.com>
[not found] ` <20190514142948.GA10361@joraj-alpa>
[not found] ` <20190514180433.GB10361@joraj-alpa>
2019-05-15 13:42 ` Zvi Vered [this message]
2019-05-15 14:33 ` Jonathan Rajotte-Julien
[not found] ` <CABRndgwxboyBQ_5pSXEV+S2687=9rUsPEtww29qAxAHEnSOMfw@mail.gmail.com>
2019-05-17 19:48 ` Jonathan Rajotte-Julien
2019-05-19 14:01 ` Zvi Vered
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='CABRndgxNtLbXZ0peWNm7qq_kxT4fY_PspgJ6hR=H82r3o8Nhmw@mail.gmail.com' \
--to=veredz72@gmail.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