Bug #385: When relayd is killed on the remote side, consumer daemon gets [defunct] - LTTng-tools - LTTng bugs repository

Actions

Copy link

Bug #385

closed

When relayd is killed on the remote side, consumer daemon gets [defunct]

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

Status:

Resolved

Priority:

High

Assignee:

David Goulet

Target version:

LTTng - 2.1 stable

Start date:

10/24/2012

Due date:

% Done:

100%

Estimated time:

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by David Goulet about 12 years ago

Status changed from New to Confirmed
Assignee set to David Goulet
Priority changed from Normal to High
Target version set to 2.1 stable

So, when a trace write operation fails (mmap or splice), the associated thread in the consumer dies making the consumer virtually useless for more tracing.

Furthermore, I just discovered with the lttng-tools HEAD (dda67f6c1ffa2bd1bb106b21d1ee353a4c1245f8), when killing the relayd the lttng_data_available call (used by default by "lttng stop") blocks for a long time... and my guess it's because it's trying to communicate on a socket shutdown on one side.

This is pretty high severity and MUST be fixed before 2.1-stable

Thanks!

Actions

Copy link