From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8ED4C454AC; Wed, 19 Jun 2024 17:44:11 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 75561402E6; Wed, 19 Jun 2024 17:44:11 +0200 (CEST) Received: from fout1-smtp.messagingengine.com (fout1-smtp.messagingengine.com [103.168.172.144]) by mails.dpdk.org (Postfix) with ESMTP id 3A421402D3; Wed, 19 Jun 2024 17:44:10 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id ACD3F1380176; Wed, 19 Jun 2024 11:44:09 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 19 Jun 2024 11:44:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1718811849; x=1718898249; bh=B1rX/O2ulzpbFWTYNyWL+07gAyrC0EoJm6SbY6q4P9g=; b= mKr2rxiXwJfG8+247nsZ4AmF4f6dO2/QDCAL4l9p9M4WSMx9/p5CDSe0AjCA7rY8 2Y4J0y5cGUNRgzkFWXup29AYLiUTxCHBNxq6RSc/6zJzHMN5SIlZYqBfamGX20dl aivry98FMnnC7AMMTa6PI30kjZSOtZm6oI4vJ/Y50DSKCSpRQSWpqzZ6dKNSVUnk rzJt7KLCUDdAabEYAZK2Yfk9QjfFW4CpbZjq6TXMDvAFBquczWX0fBQKN5j1gFHS 8dqDTVSNsbz8dexcY6MPcWmY2JsCXpCfLhvzpvbogxR8Tr+JYws/D/E1T8izXFA4 6fjpftQpM5x8paCv57rvdw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1718811849; x= 1718898249; bh=B1rX/O2ulzpbFWTYNyWL+07gAyrC0EoJm6SbY6q4P9g=; b=d DpwJewoGsiwz/YUuDf6M72DGOs58B43XujD9ybZei4nrcQU0YG1dfAooFX4xSLsI qfNKw/UsaPpHDAioSRE5WFWvkW6SDSWZYR8HMozwjsrl5H2bufECyclqCPMhmE0r s0kf9iYEvRviytuXe4JEBbG4APSJHUge2sc50ouK/YzD4CVwUQww5rn6a8F0wRwx xUnuNPT1jhzMSKDb/4KhjI/NKBHzgnYlo0d9L8uXY8N85SLCO3aigL5o/KgsUszJ pHno1avam2du3ERFm3WT9l3otW8PMkMSahnCDtSIMMBQGvsrZYa6ChVYmBAD2LjH j3EoEJCPI9r+dQANm7oeA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfeeftddgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeejudevheeiveduuddtveffgfdtgeekueevjeffjeegtdeggeek gfdvuefgfeekjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 19 Jun 2024 11:44:06 -0400 (EDT) From: Thomas Monjalon To: David Marchand Cc: dev@dpdk.org, stable@dpdk.org, Ciara Power , Chengwen Feng , Shaowei Sun <1819846787@qq.com>, Bruce Richardson Subject: Re: [PATCH] telemetry: lower log level on socket error Date: Wed, 19 Jun 2024 17:44:04 +0200 Message-ID: <3023269.BQQF58Tnoo@thomas> In-Reply-To: References: <20240606122654.2889214-1-david.marchand@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 17/06/2024 16:28, Bruce Richardson: > On Thu, Jun 06, 2024 at 02:26:54PM +0200, David Marchand wrote: > > When starting two DPDK programs using the same DPDK prefix (like for > > example OVS and testpmd, both running as primary processes in > > --in-memory mode), the first DPDK process of the two spews some error > > log when the second starts: > > > > TELEMETRY: Socket write base info to client failed > > > > This is because telemetry init involves trying to connect on existing > > sockets to check if it can take over an existing socket file. > > > > On the other hand, this error log provides no helpful information. > > Lower this log to debug level. > > > > Fixes: e14bb5f10509 ("telemetry: fix connected clients count") > > Cc: stable@dpdk.org > > > > Signed-off-by: David Marchand > > Acked-by: Bruce Richardson Applied, thanks.