> Are you using the latest lttng-agent code (dated 2011-08-12)? This one has a
> fix for corrupted traces when streaming through the network in overload
> conditions. And it is very possible that the kernel traces produce more
> events than the network connection can handle. Even without corruption
Date: Mon, 17 Oct 2011 12:46:37 -0400
From: Patrick Tasse
> Are you using the latest lttng-agent code (dated 2011-08-12)? This one has a
> fix for corrupted traces when streaming through the network in overload
> conditions. And it is very possible that the kernel traces produce more
> events tha
Hi Daniel,
Are you using the latest lttng-agent code (dated 2011-08-12)? This one has a
fix for corrupted traces when streaming through the network in overload
conditions. And it is very possible that the kernel traces produce more
events than the network connection can handle. Even without corrup
New problem.
I've tried various combinations of traces between two machines, using
writeTraceLocal and writeTraceNetwork. All of the network traces, when
imported into LTTV or the Eclipse LTTng perspective, cause the viewer to crash
without any warning. Eclipse's log(s) is(are) empty, i
Hi Daniel,
> Proposed procedure to reach channel configuration dialog:
> 1') Obtain contextual menu of the target, select New Trace
> 2') Fill out trace name and path
> 3') Click Next
>
> On step 3', Eclipse would redeploy the Remote Systems view down to the
newly-created trace and select it.
--
Date: Tue, 11 Oct 2011 14:01:40 -0400
From: Patrick Tasse
> For the Files subsystem, I see the same behavior. This is untouched
> functionality provided by the Target Management / Remote Systems Explorer
> plugins. I tried to
Hi Daniel,
For the Files subsystem, I see the same behavior. This is untouched
functionality provided by the Target Management / Remote Systems Explorer
plugins. I tried to debug a little to see what is happening, it seems that
when you expand the "Home" filter, the filter string is "." which gets
I'm trying, without success, to get the Eclipse LTTng LinuxTools to work.
First I'll describe my setup, next the symptoms.
The traced machine is running Ubuntu 11 32-bits and the tcf agent (20110811
version) with the liblttng-agent and -client plugins (7a8767c version).
The tracing ma
