Project

General

Profile

Actions
Copy link

Bug #365

closed

Consumerd can't be killed if unable to connect to the error socket

Added by David Goulet about 12 years ago. Updated about 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
David Goulet
Target version:
LTTng - 2.1 stable
Start date:
10/10/2012
Due date:
% Done:

0%

Estimated time:

Description

When killing the session daemon, a consumerd, that was unable to connect to the error socket, does not quit.

Related issues 1 (0 open — 1 closed)

Related to LTTng-tools - Bug #367: After "pkill -9 lttng-sessiond", unable to launch sessiond again unless all instrumented app exitResolvedDavid Goulet10/10/2012

Actions
Actions
Copy link
 #1

Updated by David Goulet about 12 years ago

Related to bug 387 because the metadata thread does not quit if the consumer_thread_sessiond_poll thread dies.

It's related because there is a behavior issue.

Actions
Copy link
 #2

Updated by David Goulet about 12 years ago

  • Status changed from Confirmed to Resolved

This is fixed. Unable to reproduce the issue.

If the sessiond thread dies in the consumer daemon, everything goes down as well after every streams has hang up (if any existing). Considering that if the consumer error socket is bad for some reason, the sessiond thread will stop and notifies the other threads as well to gracefully quit.

Actions
Copy link

Also available in: Atom PDF