From: David Goulet <dgoulet@efficios.com>
Date: Wed, 19 Jun 2013 19:44:51 +0000 (-0400)
Subject: Fix: change an ERR message to a DBG
X-Git-Tag: v2.2.0-rc3~6
X-Git-Url: https://git.lttng.org./?a=commitdiff_plain;h=84cc9aa082cd6cdbdee83f881046e45ca9f37d97;p=lttng-tools.git

Fix: change an ERR message to a DBG

Signed-off-by: David Goulet <dgoulet@efficios.com>
---

diff --git a/src/common/ust-consumer/ust-consumer.c b/src/common/ust-consumer/ust-consumer.c
index cd6277f1a..780a601f6 100644
--- a/src/common/ust-consumer/ust-consumer.c
+++ b/src/common/ust-consumer/ust-consumer.c
@@ -624,7 +624,13 @@ static int close_metadata(uint64_t chan_key)
 
 	channel = consumer_find_channel(chan_key);
 	if (!channel) {
-		ERR("UST consumer close metadata %" PRIu64 " not found", chan_key);
+		/*
+		 * This is possible if the metadata thread has issue a delete because
+		 * the endpoint point of the stream hung up. There is no way the
+		 * session daemon can know about it thus use a DBG instead of an actual
+		 * error.
+		 */
+		DBG("UST consumer close metadata %" PRIu64 " not found", chan_key);
 		ret = LTTNG_ERR_UST_CHAN_NOT_FOUND;
 		goto error;
 	}