Project

General

Profile

Actions
Copy link

Bug #575

closed

Apparent infinite loop in session daemon when enabling/disabling loglevel events

Added by Daniel U. Thibault over 11 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Target version:
LTTng - 2.2
Start date:
06/25/2013
Due date:
% Done:

100%

Estimated time:

Description

This bug was first identified by Avi Goren <>.

# lttng create loop
Session loop-20130625-145624 created.
Traces will be written in /root/lttng-traces/loop-20130625-145624
# lttng enable-event -a -u --loglevel TRACE_ALERT
All UST events are enabled in channel channel0 for loglevel TRACE_ALERT
# lttng disable-event -a -u
All UST events are disabled in channel channel0
# lttng enable-event -a -u --loglevel TRACE_CRIT
All UST events are enabled in channel channel0 for loglevel TRACE_CRIT
# lttng list loop
(...)
    Events:
      * (loglevel: TRACE_CRIT (2)) (type: tracepoint) [enabled]
      * (loglevel: TRACE_ALERT (1)) (type: tracepoint) [disabled]
# lttng disable-event -a -u
(LTTng hangs here)

Remarkably, the session daemon remains very busy after the sudo kill command is issued, even though the trace has not even been started! It refuses to die (I sent Ctrl-C a few times from the shell that was running lttng-sessiond) and the system must be restarted.

Attached is the session daemon's log. Note the "Trace UST event * NOT found" that should not have occurred.

Files

consumer.log (28.5 KB) consumer.log lttng-sessiond -vvv --verbose-consumer Daniel U. Thibault, 06/25/2013 03:11 PM
Actions
Copy link

Also available in: Atom PDF