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=-1.1 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE, 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 2CFCBC433E2 for ; Wed, 1 Jul 2020 12:07:34 +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 A9F4820780 for ; Wed, 1 Jul 2020 12:07:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.lttng.org header.i=@lists.lttng.org header.b="iZCRx033" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A9F4820780 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 49xg2p297yz18w0; Wed, 1 Jul 2020 08:07:30 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1593605250; bh=2yMDFxbM5mJXhjV6ZZglSXINH551Nit/aUdGYo498Fg=; h=Date:To:Cc:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=iZCRx033hP0BJ1Vf+g9u1KIk/xclcOv2O0QFxv/UwlYlSYs5b122O4/CQqWUjfUqc +PuBg/uQ5SxkmUGSCnUylfbA433H+8Q5ahjGcQWADtzIQRtnCtyaopuFP3AvnfVvrh 2+5z3OxgYRyg2ZwHeNAf4h+61of44/7zYlm1ivQ+iliwajrtIYb57TNvn88xHg5Sji HRdr/UZlP17UOH/uQyh03ne/R/mS7YHOqbphW+gkqoPzMKmEkSqx0SJnM/uY5Fj+BD HaS9Jd9fIV6wezzDpNQ4nt7wACLcRyX5R/dWavnDZ0xltyNRszsMKvBrQ3FEya6Vn0 gwmABEBSyLHhw== Received: from mail.efficios.com (mail.efficios.com [167.114.26.124]) by lists.lttng.org (Postfix) with ESMTPS id 49xg2l4KSXz18bK for ; Wed, 1 Jul 2020 08:07:27 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id 231722CD433 for ; Wed, 1 Jul 2020 08:07:21 -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 RPnkVjyea688; Wed, 1 Jul 2020 08:07:20 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.efficios.com (Postfix) with ESMTP id B3AFF2CD6A4; Wed, 1 Jul 2020 08:07:20 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com B3AFF2CD6A4 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 57NF7BOXFC2H; Wed, 1 Jul 2020 08:07:20 -0400 (EDT) Received: from mail03.efficios.com (mail03.efficios.com [167.114.26.124]) by mail.efficios.com (Postfix) with ESMTP id A1AD32CD178; Wed, 1 Jul 2020 08:07:20 -0400 (EDT) Date: Wed, 1 Jul 2020 08:07:20 -0400 (EDT) To: "zhenyu.ren" Cc: lttng-dev Message-ID: <1653271969.18771.1593605240536.JavaMail.zimbra@efficios.com> In-Reply-To: <65af8a29-4fd7-454c-a060-8f06cb7bc931.zhenyu.ren@aliyun.com> 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> MIME-Version: 1.0 X-Originating-IP: [167.114.26.124] X-Mailer: Zimbra 8.8.15_GA_3945 (ZimbraWebClient - FF77 (Linux)/8.8.15_GA_3928) Thread-Topic: =?utf-8?B?5Zue5aSN77yaW2x0dG5nLWRldl0g5Zue5aSN77ya?= some tracepoints not exist in metadata? Thread-Index: sjYQzRo0R2AaKx62pMbnYpllMcun4A== Subject: Re: [lttng-dev] =?utf-8?b?5Zue5aSN77yaIOWbnuWkje+8miBzb21lIHRyYWNl?= =?utf-8?q?points_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: Mathieu Desnoyers via lttng-dev Reply-To: Mathieu Desnoyers Content-Type: multipart/mixed; boundary="===============2207948523515276267==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" Message-ID: <20200701120720.k9LcyqShVlCOVNI_pMS3DkQLsdB5Qwt5dpp1kt-zcr0@z> --===============2207948523515276267== Content-Type: multipart/alternative; boundary="=_9aee5e4e-09e3-4c71-b579-6a3595c149fb" --=_9aee5e4e-09e3-4c71-b579-6a3595c149fb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,=20 Make sure you use single quotes in your shell around wildcards, else the=20 shell will try to expand them to files in the current directory, e.g., you = need to do:=20 lttng enable-event -u 'system_event*' -c channel0 -s misc_data=20 This could very well explain why sometimes your events don't get enabled: i= f the=20 wildcard matches files in the current directory.=20 Thanks,=20 Mathieu=20 ----- On Jun 30, 2020, at 11:56 PM, zhenyu.ren wrot= e:=20 > Ah, I have to say that I use the wildcard in tracepoint name when enable-= event > to the channel, i.e. ./lttng enable-event -u system_event* -c channel0 -s > misc_data. Of course, there are the other tracepoints with wildcard succe= ed in > registring. >> ------------------------------------------------------------------ >> =E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9Azhenyu.ren via lttng-dev >> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A2020=E5=B9=B47=E6=9C=881=E6= =97=A5(=E6=98=9F=E6=9C=9F=E4=B8=89) 11:44 >> =E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9Alttng-dev ; mathieu.desnoyers >> >> =E4=B8=BB =E9=A2=98=EF=BC=9A[lttng-dev] =E5=9B=9E=E5=A4=8D=EF=BC=9A some= tracepoints not exist in metadata? >> I'd like to add that both "lttng list -u" and "lttng list $session_name"= can get >> those tracepoints' names... >> ------------------------------------------------------------------ >> =E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9Azhenyu.ren via lttng-dev >> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A2020=E5=B9=B47=E6=9C=881=E6= =97=A5(=E6=98=9F=E6=9C=9F=E4=B8=89) 11:05 >> =E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9Alttng-dev ; mathieu.desnoyers >> >> =E4=B8=BB =E9=A2=98=EF=BC=9A[lttng-dev] some tracepoints not exist in me= tadata? >> Hi, >> I find sometimes there are some tracepoints not exist in metadata file(b= ut they >> are in the list of lttng list -u) and the end result is they can NOT be = logged. >> I can not always reproduce it. It bothered me for 2 days. >> The lttng version is 2.7, I know it is not the latest version but there = are some >> reasons I can't update it. So, is this a known bug? If yes, It will be v= ery >> appreciated if you can give me any advice about the bug info(I can cherr= y pick >> the correspond fix). Otherwise, maybe I have to give up my favoriate Ltt= ng.... >> Thank you in advance! >> zhenyu.ren --=20 Mathieu Desnoyers=20 EfficiOS Inc.=20 http://www.efficios.com=20 --=_9aee5e4e-09e3-4c71-b579-6a3595c149fb Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi,

=
Make sure you use single quotes in your shell around wildcards, = else the
shell will try to expand them t= o files in the current directory, e.g., you need to do:

lttng enable-event -u= 'system_event*' -c channel0 -s misc_data

This could very well explain why some= times your events don't get enabled: if the
<= div>wildcard matches files in the current directory.

Thanks,

Mathieu
----- On Jun 30, 2020, at 11:56 PM, zhenyu.ren <zhenyu.ren@aliyun.c= om> wrote:
Ah, I have to say that I use = the wildcard in tracepoint name when enable-event to the channel, i.e. ./lt= tng enable-event -u system_event* -c channel0 -s m= isc_data. Of course, there are the other tracepoints with wildcard succeed = in registring.
----------------------------= --------------------------------------
=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9Azhenyu.ren via lttng-dev <lttng= -dev@lists.lttng.org>
=E5=8F=91= =E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A2020=E5=B9=B47=E6=9C=881=E6=97=A5(=E6= =98=9F=E6=9C=9F=E4=B8=89) 11:44
= =E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9Alttng-dev <lttng-dev@lists.lttng.org= >; mathieu.desnoyers <mathieu.desnoyers@efficios.com>
=
=E4=B8=BB=E3=80=80=E9=A2=98=EF=BC=9A[lttng-dev= ] =E5=9B=9E=E5=A4=8D=EF=BC=9A some tracepoints not exist in metadata?

I'd like to add that both "lttng list -u" and "= lttng list $session_name" can get those tracepoints' names... <= /div>
------= ------------------------------------------------------------
=E5=8F=91=E4= =BB=B6=E4=BA=BA=EF=BC=9Azhenyu.ren via lttng-dev <lttng-dev@lists.lttng.= org>
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A2020=E5=B9=B47=E6=9C= =881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=B8=89) 11:05
=E6=94=B6=E4=BB=B6=E4=BA= =BA=EF=BC=9Alttng-dev <lttng-dev@lists.lttng.org>; mathieu.desnoyers = <mathieu.desnoyers@efficios.com>
=E4=B8=BB=E3=80=80=E9=A2=98=EF=BC= =9A[lttng-dev] some tracepoints not exist in metadata?

Hi,
   I find sometimes the= re are some tracepoints not exist in metadata file(but they are in the list= of lttng list -u) and the end result is  they can NOT be logged. I ca= n not always reproduce it. It bothered me for 2 days. 
   The lttng version is 2.7, I know it is not th= e latest version but there are some reasons I can't update it. So, is this = a known bug?  If yes, It will be very appreciated if you can give me a= ny advice about the bug info(I can cherry pick the correspond fix). Otherwi= se, maybe I have to give up my favoriate Lttng....

Thank you = in advance!
zhenyu.ren

<= /div>

--
Mat= hieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
--=_9aee5e4e-09e3-4c71-b579-6a3595c149fb-- --===============2207948523515276267== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev --===============2207948523515276267==--