Project

General

Profile

Actions

Bug #452

closed

Starting a trace with an unready remote lttng-relayd leaves the trace in an odd state

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

Status:
Won't fix
Priority:
Normal
Assignee:
Target version:
Start date:
02/19/2013
Due date:
% Done:

0%

Estimated time:

Description

Here I'm running an lttng session with the intent of streaming the trace to another machine. But the other machine's lttng-relayd has not been started yet (or the IP is wrong, etc.).

$ sudo -H lttng create rsession -U net://131.132.32.77
Session rsession created.
Traces will be written in net://131.132.32.77
$ sudo -H lttng enable-event -k sched_switch
kernel event sched_switch created in channel channel0
$ sudo -H lttng start
Error: Unable to connect to lttng-relayd
$ sudo -H lttng start
Warning: Tracing already started for session rsession
$ sudo -H lttng stop
Error: Stoping kernel trace failed
$ sudo -H lttng destroy -a
Session rsession destroyed

The main bug here is we have an "already started" session which "cannot be stopped".

Also, the "Error: Unable to connect to lttng-relayd" message could be accompanied by a further message stating that the session was started anyway (or, for some other errors, that the start was aborted); as it currently stands the user is unsure whether his 'start' command succeeded or not.

"Error: Stoping kernel trace failed" includes an obvious typo. A separate bug will be filed shortly.
Actions

Also available in: Atom PDF