From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Lakshmi Deverkonda <laksd@nvidia.com>,
"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] Crash in application due to watchdog timeout with python3 lttng
Date: Tue, 13 Feb 2024 10:20:35 -0500 [thread overview]
Message-ID: <3f05e93b-f57e-4d93-be45-c779cd209f44@efficios.com> (raw)
In-Reply-To: <MW3PR12MB4555D9C015549D882B1FE87BD94F2@MW3PR12MB4555.namprd12.prod.outlook.com>
Hi Lakshmi,
when the lttngust python agent starts, it attempts to connect to one or
more session daemons[1].
Each connection starts a thread that loops forever, retrying the
registration in case an exception occurs[2].
I don't think the it's designed to have `join()` called on those
threads, which I assume is happening in some of the code you or your
team have written.
My initial thought is that you should `join()` only the threads that
pertinent to your application, ignoring the lttngust agent threads and
then exit the application as normal.
[1]:
https://github.com/lttng/lttng-ust/blob/3287f48be61ef3491aff0a80b7185ac57b3d8a5d/src/python-lttngust/lttngust/agent.py#L334
[2]:
https://github.com/lttng/lttng-ust/blob/3287f48be61ef3491aff0a80b7185ac57b3d8a5d/src/python-lttngust/lttngust/agent.py#L83
thanks,
kienan
On 2/13/24 09:23, Lakshmi Deverkonda via lttng-dev wrote:
> Hi,
>
> We are able to integrate python3 lttng module in our application(python3
> based). However, we are seeing that whenever the application terminates,
> there is watchdog timeout due to timeout in joining the threads. What
> could be the reason for this ? Does lttng module hold any thread event
> locks ?
> We are completely blocked on this issue. Could you please help ?
>
> Here is the snippet of the core dump
>
> (gdb) py-bt
> Traceback (most recent call first):
> File "/usr/lib/python3.7/threading.py", line 1048, in
> _wait_for_tstate_lock
> elif lock.acquire(block, timeout):
> File "/usr/lib/python3.7/threading.py", line 1032, in join
> self._wait_for_tstate_lock()
> File "/usr/lib/python3/dist-packages/h.py", line 231, in JoinThreads
> self.TT.join()
> File "/usr/sbin/c", line 1466, in do_exit
> H.JoinThreads()
> File "/usr/sbin/c", line 7201, in main
> do_exit(nlm, status)
> File "/usr/sbin/c", line 7233, in <module>
> main()
> (gdb)
>
> On a parallel note, thanks to Kienan who has been trying to provide
> pointers on various issues reported so far.
>
> Need help on this issue as well.
> Thanks in advance,
>
> Regards,
> Lakshmi
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2024-02-13 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 14:23 Lakshmi Deverkonda via lttng-dev
2024-02-13 15:20 ` Kienan Stewart via lttng-dev [this message]
2024-02-13 15:35 ` Lakshmi Deverkonda via lttng-dev
2024-02-13 16:03 ` Kienan Stewart via lttng-dev
2024-02-16 14:33 ` Lakshmi Deverkonda via lttng-dev
2024-02-16 16:41 ` Kienan Stewart via lttng-dev
2024-02-20 15:24 ` Lakshmi Deverkonda via lttng-dev
2024-02-23 15:09 ` Kienan Stewart 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=3f05e93b-f57e-4d93-be45-c779cd209f44@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=kstewart@efficios.com \
--cc=laksd@nvidia.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