> 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
