From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Rajotte-Julien via lttng-dev Subject: Re: =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIOWbnuWkje+8miBz?= =?utf-8?q?ome_tracepoints_not_exist_in_metadata=3F?= Date: Thu, 2 Jul 2020 08:45:41 -0400 Message-ID: <20200702124541.GF4207@joraj-alpa> References: <5efd3314-04ed-4868-a0c9-408434d330f4.zhenyu.ren@aliyun.com> <49dab706-ab7e-4156-9163-b8d9105b173d.zhenyu.ren@aliyun.com> <65af8a29-4fd7-454c-a060-8f06cb7bc931.zhenyu.ren@aliyun.com> <1653271969.18771.1593605240536.JavaMail.zimbra@efficios.com> Reply-To: Jonathan Rajotte-Julien Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail.efficios.com (mail.efficios.com [167.114.26.124]) by lists.lttng.org (Postfix) with ESMTPS id 49yHrS1Ks0z18gK for ; Thu, 2 Jul 2020 08:45:44 -0400 (EDT) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" To: "zhenyu.ren" Cc: lttng-dev List-Id: lttng-dev@lists.lttng.org On Thu, Jul 02, 2020 at 08:38:57AM +0800, zhenyu.ren via lttng-dev wrote: > Thanks a lot. I will try single quotes but it may take hours get the result. > Yesterday, I enabled the verbose option ,and found the following message "UST > app reply event failed. Application died (in add_event_ust_registry() at > ust-app.c:5405)" and "UST app notify socket unregister 34 (in > ust_app_notify_sock_unregister() at ust-app.c:5562)". In fact ,the socket that > Lttng-sessiond send reply to my app return an error with EPIPE. It seems that > the pipe breaked.So do you have any hint for that? >From lttng master: ret = ustctl_reply_register_event(sock, event_id, ret_code); if (ret < 0) { if (ret != -EPIPE && ret != -LTTNG_UST_ERR_EXITING) { ERR("UST app reply event failed with ret %d", ret); } else { DBG3("UST app reply event failed. Application died"); } /* * No need to wipe the create event since the application socket will * get close on error hence cleaning up everything by itself. */ goto error; } EPIPE ifor this socket is considered as an expected scenario. This normally indicates a short-lived application or that your application crashed while lttng-ust and lttng-tools were performing an event registration. Considering that the path leading to the ustctl_reply_register_event call is preceded by a call fetching information from the same socket (ustctl_recv_register_event), I expect this to be a completely normal scenario unless you provide evidence that this application under tracing was acting normally and had a long lifetime. Cheers From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DAFDCC433DF for ; Thu, 2 Jul 2020 12:45:48 +0000 (UTC) Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 59C5A20885 for ; Thu, 2 Jul 2020 12:45:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.lttng.org header.i=@lists.lttng.org header.b="Wb5xpkIB" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 59C5A20885 Authentication-Results: mail.kernel.org; dmarc=pass (p=none dis=none) header.from=lists.lttng.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lttng-dev-bounces@lists.lttng.org Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 49yHrT6kmDz18q8; Thu, 2 Jul 2020 08:45:45 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1593693946; bh=s5sL2UYHMRFgtvW9kMObBjH3Pvt3jhu5UrDHdVhBwKc=; h=Date:To:References:In-Reply-To:Subject:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=Wb5xpkIB9bPKzLqs5az03CaIXs+VUGDyX2554pu+NfylZz3nr7NJTmulIHlkNl+5L 9Ja8apU0NekQqEs79H65es9v8WhtxO4EKD2hoBr1KLLun9N7y2C2ixNDxcXVXrS04K sOfrBSjlQ9xesAkEpVhFUtAroKRbEU6ebRZFa2niPhYtoYniJaZOLPfNabg2M7g+8W n64Q1FMPPlngAXSpNcD2g+Q5jD+hqmmwtDsEpmt7MQGQtpGtD7SJmxRUGyWdBMut7z H7tmgrMp0HuczR2hB5L2QLXYwjexJ3Ana+2mb5jXWBbvDR81ICmqq40mW0NIFLpPia I0RSAsuIczSag== Received: from mail.efficios.com (mail.efficios.com [167.114.26.124]) by lists.lttng.org (Postfix) with ESMTPS id 49yHrS1Ks0z18gK for ; Thu, 2 Jul 2020 08:45:44 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id C8CDE2D69A2; Thu, 2 Jul 2020 08:45:43 -0400 (EDT) Received: from mail.efficios.com ([127.0.0.1]) by localhost (mail03.efficios.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id a8fPtO5j0H9X; Thu, 2 Jul 2020 08:45:43 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id 83CE62D6854; Thu, 2 Jul 2020 08:45:43 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com 83CE62D6854 X-Virus-Scanned: amavisd-new at efficios.com Received: from mail.efficios.com ([127.0.0.1]) by localhost (mail03.efficios.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YZbuJcEdCDR2; Thu, 2 Jul 2020 08:45:43 -0400 (EDT) Received: from joraj-alpa (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) by mail.efficios.com (Postfix) with ESMTPSA id 23F832D6A1B; Thu, 2 Jul 2020 08:45:43 -0400 (EDT) Date: Thu, 2 Jul 2020 08:45:41 -0400 To: "zhenyu.ren" Message-ID: <20200702124541.GF4207@joraj-alpa> References: <5efd3314-04ed-4868-a0c9-408434d330f4.zhenyu.ren@aliyun.com> <49dab706-ab7e-4156-9163-b8d9105b173d.zhenyu.ren@aliyun.com> <65af8a29-4fd7-454c-a060-8f06cb7bc931.zhenyu.ren@aliyun.com> <1653271969.18771.1593605240536.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [lttng-dev] =?utf-8?b?5Zue5aSN77ya5Zue5aSN77yaIOWbnuWkje+8miBz?= =?utf-8?q?ome_tracepoints_not_exist_in_metadata=3F?= X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.31 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jonathan Rajotte-Julien via lttng-dev Reply-To: Jonathan Rajotte-Julien Cc: lttng-dev Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" Message-ID: <20200702124541.sGMYUwMyeL8PfOWOSLIX6X9kIP1o8ZTezPzZm0yYXVY@z> On Thu, Jul 02, 2020 at 08:38:57AM +0800, zhenyu.ren via lttng-dev wrote: > Thanks a lot. I will try single quotes but it may take hours get the result. > Yesterday, I enabled the verbose option ,and found the following message "UST > app reply event failed. Application died (in add_event_ust_registry() at > ust-app.c:5405)" and "UST app notify socket unregister 34 (in > ust_app_notify_sock_unregister() at ust-app.c:5562)". In fact ,the socket that > Lttng-sessiond send reply to my app return an error with EPIPE. It seems that > the pipe breaked.So do you have any hint for that? >From lttng master: ret = ustctl_reply_register_event(sock, event_id, ret_code); if (ret < 0) { if (ret != -EPIPE && ret != -LTTNG_UST_ERR_EXITING) { ERR("UST app reply event failed with ret %d", ret); } else { DBG3("UST app reply event failed. Application died"); } /* * No need to wipe the create event since the application socket will * get close on error hence cleaning up everything by itself. */ goto error; } EPIPE ifor this socket is considered as an expected scenario. This normally indicates a short-lived application or that your application crashed while lttng-ust and lttng-tools were performing an event registration. Considering that the path leading to the ustctl_reply_register_event call is preceded by a call fetching information from the same socket (ustctl_recv_register_event), I expect this to be a completely normal scenario unless you provide evidence that this application under tracing was acting normally and had a long lifetime. Cheers _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev