From: Yonghong Yan via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] LTTng sessiond daemon Assertion `buf' failed and killed
Date: Fri, 12 Jan 2024 08:12:21 -0500 [thread overview]
Message-ID: <CACJEY861mX+FerESW6O6pTU7CzadHGDSBF9HktNrXr_fGp-Hcw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2771 bytes --]
I am not sure whether this is my setting problem or a bug with a
more recent kernel. lttng-sessiond was killed when I tried to "enable
event" after a session was created. See below part of the verbose output of
the sessiond. It is observed on Ubuntu 22.04, kernel 6.5.0-14-generic
#14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC, lttng (LTTng Trace Control) 2.13.10
- Nordicité.
The same version of LTTng works on another Ubuntu 22.04 machine, but with
kernel 6.2.0-33-generic. Any suggestion on what I should try?
Thank you
Yonghong
c:1016)
DBG1 - 00:24:25.134138433 [Client management]: Getting session
auto-20240112-002417 by name (in process_client_msg() at client.c:1133)
DBG1 - 00:24:25.134148894 [Client management]: Creating UST session (in
create_ust_session() at client.c:510)
DBG1 - 00:24:25.134267958 [Client management]: Spawning consumerd (in
spawn_consumerd() at client.c:204)
DBG1 - 00:24:25.135155823 [Client management]: Waiting for consumer
management thread to be ready (in wait_until_thread_is_ready() at
manage-consumer.c:46)
DBG1 - 00:24:25.135247552 [Consumer management]: Entering thread entry
point (in launch_thread() at thread.c:65)
DBG1 - 00:24:25.135293542 [Consumer management]: [thread] Manage consumer
started (in thread_consumer_management() at manage-consumer.c:65)
DBG1 - 00:24:25.135335776 [Client management]: Using 64-bit UST consumer
at: /usr/lib/x86_64-linux-gnu/lttng/libexec/lttng-consumerd (in
spawn_consumerd() at client.c:284)
DBG1 - 00:24:25.240725883 [Consumer management]: Consumer command socket
ready (fd: 61) (in thread_consumer_management() at manage-consumer.c:204)
DBG1 - 00:24:25.240746802 [Consumer management]: Consumer metadata socket
ready (fd: 62) (in thread_consumer_management() at manage-consumer.c:205)
DBG1 - 00:24:25.240775318 [Consumer management]: Sending consumer
initialization command (in consumer_init() at consumer.c:1791)
DBG1 - 00:24:25.241066762 [Consumer management]: Marking consumer
management thread as ready (in mark_thread_as_ready() at
manage-consumer.c:31)
DBG1 - 00:24:25.241100481 [Client management]: Consumer management thread
is ready (in wait_until_thread_is_ready() at manage-consumer.c:48)
DBG1 - 00:24:25.241138386 [Client management]: Setting relayd for session
auto-20240112-002417 (in cmd_setup_relayd() at cmd.c:1004)
lttng-sessiond: unix.c:185: lttcomm_recv_unix_sock: Assertion `buf' failed.
Error: Events: No session daemon is available (channel channel0, session
auto-20240112-002417)
[1]+ Aborted (core dumped) lttng-sessiond --verbose
DBG1 - 00:24:26.357769106 [Run-as worker]: run_as worker exiting (ret = 0)
(in run_as_create_worker_no_lock() at runas.c:1526)
[-- Attachment #1.2: Type: text/html, Size: 8834 bytes --]
[-- Attachment #2: 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
next reply other threads:[~2024-01-12 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 13:12 Yonghong Yan via lttng-dev [this message]
2024-01-12 15:01 ` Kienan Stewart via lttng-dev
[not found] ` <CACJEY847OEguyrq2WYxKMLQ4sSf59fdFYKZZe4ZR16Wsaajeqw@mail.gmail.com>
2024-01-12 19:31 ` Kienan Stewart via lttng-dev
2024-01-12 20:38 ` Yonghong Yan via lttng-dev
2024-01-12 20:58 ` Kienan Stewart via lttng-dev
2024-01-13 3:04 ` Yonghong Yan via lttng-dev
2024-01-13 3:48 ` Yonghong Yan 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=CACJEY861mX+FerESW6O6pTU7CzadHGDSBF9HktNrXr_fGp-Hcw@mail.gmail.com \
--to=lttng-dev@lists.lttng.org \
--cc=yanyh15@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