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 12F4C454AA; Wed, 19 Jun 2024 16:37:31 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D701040291; Wed, 19 Jun 2024 16:37:30 +0200 (CEST) Received: from fhigh6-smtp.messagingengine.com (fhigh6-smtp.messagingengine.com [103.168.172.157]) by mails.dpdk.org (Postfix) with ESMTP id BD19940289; Wed, 19 Jun 2024 16:37:29 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 42E5511401FC; Wed, 19 Jun 2024 10:37:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 19 Jun 2024 10:37:29 -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=1718807849; x=1718894249; bh=Ll+ZyN3G08oIMB3K08c1ml1ysf7BU0fqS7HThOi/+ng=; b= kJe2I60rxfbXOALkPLyJLfJem+Gqh1sm2UgeiGYbqVS+4RFDaBhk55gn6PotS15a uQOgC0EWCwI/yYLu2sm2Qw0dp6pRXZ5c2BCq5DcV3WOUrcGMc3hZWahgbP/NkPL0 dCHT7WLku3+3jfp/q+FC79M02+G6buaqeOv9e+tT0SfuhxM100gloUh0ynA4maHM 2BI4XrJ4Se5I5bLwZ9iBLiA2aDxIG8xAyKFW+20S6vnEerwiT03Bj8t4Z5+EnTas x6qSPo8OqH2+14TcpJhELasB1zemTDxQvQFDZpE/dXOFe+Oo77hnhWsOJOHThOZS +/qXqNIM4VTrDsHTt+5RBg== 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=1718807849; x= 1718894249; bh=Ll+ZyN3G08oIMB3K08c1ml1ysf7BU0fqS7HThOi/+ng=; b=k iaQB7y2h9tGgOHYCE8N3q+B8XrjIMFl81I4LsEYZBJnAc/X3LFr1cnLpTETIcKkh 3aEm5IejA10mTFT6brVdpmhx7bwqVGyYKQmEQfjn58pgP/t2ByixWbhaj099Wnib cAO77n4Yva445pfMx3MyxZ8BHWTkNktiBsguigZ/BjJ1KjSUCaeEzMJVO5VXnOsE 6CBZ61uoES5e1yREaWb2BqHvXuk5/PiMiRH7YAtNG0UEJSfOOMaSKHqcOpQmZlDt UJZDemxPzLWiiu/SfQ1ERouplSjhoAsFR2jKlWJaIUzsgm0v69mI5yBmUPicECQx g32p5ZUPA40bXWt3+NLUg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfeeftddgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeegtddtleejjeegffekkeektdejvedtheevtdekiedvueeuvdei uddvleevjeeujeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 19 Jun 2024 10:37:26 -0400 (EDT) From: Thomas Monjalon To: Christian Ehrhardt Cc: David Marchand , dev@dpdk.org, stable@dpdk.org, Ciara Power , Chengwen Feng , Bruce Richardson , Shaowei Sun <1819846787@qq.com> Subject: Re: [PATCH] telemetry: lower log level on socket error Date: Wed, 19 Jun 2024 16:37:23 +0200 Message-ID: <9824270.uMvqGB8zbg@thomas> In-Reply-To: References: <20240606122654.2889214-1-david.marchand@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 06/06/2024 15:26, Christian Ehrhardt: > On Thu, Jun 6, 2024 at 2:27=E2=80=AFPM 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. >=20 > I agree, it is useful info in rare occasions, but not a "please > consider having a panic" error level. > Thank you for polishing all edges of this one issue that I raised origina= lly! >=20 > Signed-off-by: Christian Ehrhardt Where did you raise it? I don't find it in emails.