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? Thank you ------------------------------------------------------------------ 发件人：Mathieu Desnoyers 发送时间：2020年7月1日(星期三) 20:07 收件人：zhenyu.ren 抄　送：lttng-dev 主　题：Re: 回复：[lttng-dev] 回复： some tracepoints not exist in metadata? Hi, Make sure you use single quotes in your shell around wildcards, else the shell will try to expand them to 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 sometimes your events don't get enabled: if the wildcard matches files in the current directory. Thanks, Mathieu ----- On Jun 30, 2020, at 11:56 PM, zhenyu.ren wrote: 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 succeed in registring. ------------------------------------------------------------------ 发件人：zhenyu.ren via lttng-dev 发送时间：2020年7月1日(星期三) 11:44 收件人：lttng-dev ; mathieu.desnoyers 主　题：[lttng-dev] 回复： 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... ------------------------------------------------------------------ 发件人：zhenyu.ren via lttng-dev 发送时间：2020年7月1日(星期三) 11:05 收件人：lttng-dev ; mathieu.desnoyers 主　题：[lttng-dev] some tracepoints not exist in metadata? Hi, I find sometimes there 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 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 very appreciated if you can give me any advice about the bug info(I can cherry pick the correspond fix). Otherwise, maybe I have to give up my favoriate Lttng.... Thank you in advance! zhenyu.ren -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com