Project

General

Profile

Actions
Copy link

Bug #1440

closed
SP KS

Lttng sessiond crashing with Invalid zero length identifier

Bug #1440: Lttng sessiond crashing with Invalid zero length identifier

Added by Srishaka Pilla about 1 month ago. Updated 7 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Kienan Stewart
Target version:
LTTng - 2.14
Start date:
05/08/2026
Due date:
% Done:

0%

Estimated time:

Description

Hi,

We are uplifting from Lttng 2.12 to Lttng 2.14. As both Lttng 2.12 and Lttng 2.14 are co installable we uplifted lttng to 2.14.1 and instrumented applications are still using lttng 2.12.
But we are facing issue of Invalid zero length identifier while lttng start process. This is randomly observed (4/6 times failed).
We observed this is fixed in Lttng 2.15.0.
Can this fix be backported to 2.14 as we cannot have the uplift from 2.12 to 2.15 due to incompatible internal communication protocol.

Thanks and Regards,
Srishaka Pilla

KS Updated by Kienan Stewart about 1 month ago Actions
Copy link
 #1

Hi Srishaka,

the fix for zero-length identifiers is planned for the next stable-2.14 bug-fix release. I don't have an estimated timeline for that right now.

My off-hand recollection is that the problem is provoked by traced applications that have a tracepoint with an empty identifier. If you know which of your traced applications has that tracepoint, re-compiling it with a non-empty identifier should work around the issue in the interim.

As a note, community support doesn't include issues specific to using 2.12 as part of the tracing environment (https://lttng.org/community/#supported-releases for more info).

thanks,
kienan

SP Updated by Srishaka Pilla 16 days ago Actions
Copy link
 #2

Hi Kienan,

By when can we expect the fix tentatively.
Due to this issue we are blocked from releasing Lttng uplift changes.

Issue with single CPU node on Lttng 2.15 ========================================
While we are checking on Lttng 2.15, we are facing lttng-sessiond crash for single CPU node.
We did not face this issue earlier we faced only during Lttng 2.15 testing.

Thanks and Regards,
Srishaka

KS Updated by Kienan Stewart 9 days ago Actions
Copy link
 #3

Hi Srishaka,

we're looking at making a bug-fix release this week. I'll let you know when it's available.

thanks,
kienan

KS Updated by Kienan Stewart 7 days ago Actions
Copy link
 #4

  • Status changed from New to Resolved

Hi Srishaka,

lttng-tools 2.14.2 is now available. Let me know if that helps.

thanks,
kienan

Actions
Copy link

Also available in: PDF Atom