From: dgoulet@efficios.com (David Goulet)
Subject: [lttng-dev] Trace Streaming problem
Date: Tue, 11 Feb 2014 09:57:13 -0500 [thread overview]
Message-ID: <20140211145713.GA7091@thessa> (raw)
In-Reply-To: <CAO_ArvpaU2cGQ+9F=A+vHv9zNupXitvkSCr6RZh0LzTjLj9uMA@mail.gmail.com>
On 11 Feb (13:24:15), kumar s wrote:
> Hi,
>
> I am trying to start the trace on MIPS board and dump it remotely on PC.
>
> The steps i do
> On MIPS board:
> lttng create -U net://192.168.233.207 newsession
>
> lttng enable-event lttng_statedump_start -k
>
> Error: Event lttng_statedump_start: Unable to connect to lttng-relayd
> (channel channel0, session news)
> Warning: Some command(s) went wrong
>
> In lttng-sessiond -vvv log
>
> [...]
> DEBUG3 [1918/2019]: Consumer socket created (fd: 30) and added to output
> (in consumer_create_socket() at consumer.c:300)
> DEBUG1 [1918/2019]: Setting relayd for session news (in cmd_setup_relayd()
> at cmd.c:722)
> DEBUG3 [1918/2019]: Relayd connect ... (in relayd_connect() at relayd.c:466)
> PERROR [1918/2019]: connect: Connection refused (in
> lttcomm_connect_inet_sock() at inet.c:253)
> Error: Unable to reach lttng-relayd
> DEBUG1 [1918/2019]: Sending response (size: 16, retcode: Unable to connect
> to lttng-relayd) (in thread_manage_clients() at main.c:3973)
> DEBUG1 [1918/2019]: Clean command context structure (in clean_command_ctx()
> at main.c:672)
> DEBUG1 [1918/2019]: Accepting client command ... (in
> thread_manage_clients() at main.c:3837)
>
> On the linux pc
> i have started lttng-relayd
>
> lttng-relayd -vvv -C tcp://0.0.0.0:1234 -D tcp://0.0.0.0:5678 (as specified
> in doc folder of lttng-tools)
The relayd is started with different ports here so the session creation
should also specify those like so:
$ lttng create -U net://192.168.233.207:1234:5678
(or use -C/-D).
David
>
>
> Unfortunately i get error that lttng-relayd unable to connect. I also tried
> started lttng-relayd on mips board and running the same, still i get same
> error.
>
> Can someone explain steps for lttng trace streaming or how i can dump the
> trace live onto PC.
>
> Thank you
> Skumar
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: Digital signature
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20140211/48e5b9d7/attachment.pgp>
next prev parent reply other threads:[~2014-02-11 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 7:54 kumar s
2014-02-11 14:57 ` David Goulet [this message]
2014-02-12 11:55 ` kumar s
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=20140211145713.GA7091@thessa \
--to=dgoulet@efficios.com \
/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