From 53eb691c0c1d42e5b3f70697d8295ca4014e1dbc Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=A9r=C3=A9mie=20Galarneau?= Date: Fri, 20 Dec 2019 00:59:56 -0500 Subject: [PATCH 1/1] Fix: relayd: fail to create session when trace chunk is not found MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit When a session is created by a peer with a trace chunk id already set, it means that the session daemon has already created that trace chunk at some point in the past. Hence, it should be found in the sessiond trace chunk registry. Signed-off-by: Jérémie Galarneau Change-Id: I8c6d19371d322cf7079d7a01c4c24b585b4b3ea1 --- src/bin/lttng-relayd/session.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/bin/lttng-relayd/session.c b/src/bin/lttng-relayd/session.c index 00dfbd7d2..1a1cadfdf 100644 --- a/src/bin/lttng-relayd/session.c +++ b/src/bin/lttng-relayd/session.c @@ -366,6 +366,7 @@ struct relay_session *session_create(const char *session_name, ERR("Could not find trace chunk: sessiond = {%s}, sessiond session id = %" PRIu64 ", trace chunk id = %" PRIu64, uuid_str, *id_sessiond, *current_chunk_id); + goto error; } } else if (!id_sessiond) { /* -- 2.34.1