Project

General

Profile

Actions
Copy link

Bug #731

closed

lttng (re)start emits error when session created with --no-output or --snapshot

Added by Tony Jones almost 11 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
David Goulet
Target version:
LTTng - 2.3
Start date:
02/12/2014
Due date:
% Done:

100%

Estimated time:

Description

Verified with latest stable-2.3

  1. lttng create test --no-output
    Session test created.
  1. lttng enable-channel --overwrite -k test-chan
    Kernel channel test-chan enabled for session test
  1. lttng enable-event -k -c test-chan signal_generate
    kernel event signal_generate created in channel test-chan
  1. lttng start
    Tracing started for session test
  1. lttng stop
    Waiting for data availability
    Tracing stopped for session test
  1. lttng start
    Error: Consumer add channel key 33 already exists!
    Tracing started for session test

I'm not sure if this can be safely ignored? I'm trying to measure lttng syscall overhead, hence the --no-output but it's not clear if tracing is actually being restarted.

Actions
Copy link
 #1

Updated by Mathieu Desnoyers over 10 years ago

  • Project changed from LTTng to LTTng-tools
  • Assignee set to David Goulet
Actions
Copy link
 #2

Updated by David Goulet over 10 years ago

  • Status changed from New to Confirmed
  • Priority changed from High to Normal

To answer your question, yes the tracing has been started. This error is an issue for the kernel tracing. I'll look into it.

Actions
Copy link
 #3

Updated by David Goulet over 10 years ago

  • Status changed from Confirmed to Resolved
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF