Never mind. I figured out the problem. I was only passing the ust trace path up to /ust when I should have gone all the way to the actual subfolder that holds the metadata file.
Shehab Y. Elsayed, MSc. PhD Student The Edwards S. Rogers Sr. Dept. of Electrical and Computer Engineering University of Toronto E-mail: shehaby...@gmail.com <https://webmail.rice.edu/imp/message.php?mailbox=INBOX&index=11#> On Mon, Mar 5, 2018 at 9:07 PM, Shehab Elsayed <shehaby...@gmail.com> wrote: > Hello All, > > I am running into this problem where using babeltrace with python bindings > is unable to read a ust trace even though the trace can be processed > normally if I run babeltrace from the command line. > > I have tried the example given in the LTTng documentation for using > babeltrace with python bindings. It works normally with a kernel trace. > However, when I give it a ust trace (just to see if it can open it) I get > the following error: > > Unable to open metadata. > [warning] Unable to open trace metadata for path "/md1200/home/elsayed9/ > LTTng/lttng-traces/hello-test-session-20180219-184952/ust/". > [warning] [Context] Cannot open_trace of format ctf at path > /md1200/home/elsayed9/LTTng/lttng-traces/hello-test-session- > 20180219-184952/ust/. > Traceback (most recent call last): > File "test.py", line 70, in <module> > sys.exit(0 if top5proc() else 1) > File "test.py", line 18, in top5proc > raise RuntimeError('Cannot add trace') > RuntimeError: Cannot add trace > > Any ideas on how to solve this problem are greatly appreciated. > > Thanks, > Shehab >
_______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
