[lttng-dev] Sessions are disconnected when disk is full on remote host

Mikael Beckius mikael.beckius at ericsson.com
Wed Oct 7 09:50:49 EDT 2015

After trying with 2.6.1 and 2.7.0 releases of lttng-tools I cannot say that it makes much of a difference compared with the older versions previously tried. Once the file size for a CPU is reached Babeltrace will output:
[error] get_next_index: error
[error] get_next_index failed

and Babeltrace output from that CPU will cease. Restarting Babeltrace will output some traces again before output  ceases almost immediately and the problem remains until the session has been recreated.

This was with --tracefile-count set to "1" and --tracefile-size of various sizes up to a megabyte BUT if I increase the trace file count to "2" it actually appears to be working.

"LTTng currently doesn't support these recovery modes."
Are there any plans for LTTng to support these "recovery modes" or similar in a future release? Or is there perhaps a way using the LTTng API to detect that a session has lost its connection?


More information about the lttng-dev mailing list