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>
Tue, 24 Apr 2018 20:33:55 +0000 (16:33 -0400)
commitf28f9e449e13d6a3495408e5329514fa5ca7150e
tree355cf99b4b5c0a79ea948334f09fca181696cb53
parent7eac78030ec056b149f110d156b855b1e7d2c00f
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.035565 seconds and 4 git commands to generate.