Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: suchakrapani.sharma@polymtl.ca (Suchakrapani Datt Sharma)
Subject: [lttng-dev] error in generation of trace files
Date: Thu, 27 Feb 2014 15:37:02 -0500	[thread overview]
Message-ID: <1393533422.530fa1ee38bd7@www.imp.polymtl.ca> (raw)
In-Reply-To: <CAB7sTjgY9OpaQG-Cs2gnHA6s3+hHuutkP=6wPPVq5TkfdY-hng@mail.gmail.com>

Hi,

>  I'm new to lttng. I use ubuntu 13.10. While performing basic operations,
> on command lttng view, i get the following error.
> [error] Cannot open any trace for reading.
>
> [error] opening trace "/home/mariya/lttng-traces/mysession-20140227-163353"
> for reading.
>
> [error] none of the specified trace paths could be opened.

Have a look at the directory and see if trace events have actually been written
or not. You should see something like
/home/mariya/lttng-traces/mysession-20140227-163353/kernel/metadata (if it was
a kernel tracing session)

> the o/p of the command "lttng-sessiond --verbose" is as follows
>
> DEBUG3: Creating LTTng run directory: /home/mariya/.lttng [in
> create_lttng_rundir() at main.c:3692]
> DEBUG1: Client socket path /home/mariya/.lttng/client-lttng-sessiond [in
> main() at main.c:3995]
> DEBUG1: Application socket path /home/mariya/.lttng/apps-lttng-sessiond [in
> main() at main.c:3996]
> DEBUG1: LTTng run directory path: /home/mariya/.lttng [in main() at
> main.c:3997]
> Error: Already running daemon.

You probably did this again while the previous instance of lttng-sessiond was
already running and hence the last error. Kill currently running sessiond and
then start afresh using the verbose mode. Then proceed with usual lttng
commands and observe the debug output (more lines of debug output would be
definitely better). Please show it on the list if you need help in that.

I would also recommend you to have a look at the lttng manual as well as at the
Quickstart doc at [1] for detailed info of what the commands are doing.

[1] https://bugs.lttng.org/projects/lttng-tools/wiki

--
Suchakra



      parent reply	other threads:[~2014-02-27 20:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 11:06 Mariya Rampurawala
2014-02-27 13:42 ` David Goulet
     [not found]   ` <CAB7sTjjHMizJVJOYCpqED=rzt=+KJB_2Nxjf7X2C2y2+G=E_sA@mail.gmail.com>
2014-02-27 13:57     ` David Goulet
2014-02-27 20:44       ` Suchakrapani Datt Sharma
2014-02-27 20:37 ` Suchakrapani Datt Sharma [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1393533422.530fa1ee38bd7@www.imp.polymtl.ca \
    --to=suchakrapani.sharma@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox