Fix: failure to launch agent thread is not reported
authorJérémie Galarneau <jeremie.galarneau@efficios.com>
Mon, 23 Apr 2018 23:03:16 +0000 (19:03 -0400)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Wed, 25 Apr 2018 16:08:02 +0000 (12:08 -0400)
commit09a88287202e1cb7bcc984f65237bee33e6c5b93
treefa3721e38c430b3966a9350a040334c127385f59
parentb86685ef513314b56785e3d6c457e321dc8a9d1c
Fix: failure to launch agent thread is not reported

A session daemon may fail to launch its agent thread. In such
a case, the tracing of agent domains fails silently as events
never get enabled through the agent.

The problem that was reported was caused by a second session
daemon being already bound on the agent TCP socket port, which
prevented the launch of the agent thread.

While in this situation tracing is still not possible, the user
will at least get an error indicating as such when enabling
an event in those domains.

Reported-by: Deborah Barnard <starfallprojects@gmail.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
include/lttng/lttng-error.h
src/bin/lttng-sessiond/agent-thread.c
src/bin/lttng-sessiond/agent-thread.h
src/bin/lttng-sessiond/cmd.c
src/bin/lttng-sessiond/main.c
src/common/error.c
This page took 0.034504 seconds and 4 git commands to generate.