Project

General

Profile

Bug #1278

"Graph failed to complete successfully" error

Added by Seongab Kim 4 months ago. Updated 4 months ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
-
Start date:
08/06/2020
Due date:
% Done:

0%

Estimated time:

Description

Hi,

I have a trace which babeltrace shows the error as below, but I can open it with Trace Compass without the issue.

08-06 07:22:48.227 28777 28777 E PLUGIN/FLT.UTILS.MUXER muxer_msg_iter_do_next_one@muxer.c:1081 [muxer] Youngest upstream message iterator wrapper's timestamp is less than muxer's message iterator's last returned timestamp: muxer-msg-iter-addr=0x18f2ff0, ts=1596631386358365554, last-returned-ts=1596631386358599346
08-06 07:22:48.227 28777 28777 E PLUGIN/FLT.UTILS.MUXER muxer_msg_iter_next@muxer.c:1415 [muxer] Cannot get next message: comp-addr=0x18f1d10, muxer-comp-addr=0x18f2400, muxer-msg-iter-addr=0x18f2ff0, msg-iter-addr=0x18f2e80, status=ERROR
08-06 07:22:48.227 28777 28777 W LIB/MSG-ITER bt_message_iterator_next@iterator.c:864 Component input port message iterator's "next" method failed: iter-addr=0x18f2e80, iter-upstream-comp-name="muxer", iter-upstream-comp-log-level=WARNING, iter-upstream-comp-class-type=FILTER, iter-upstream-comp-class-name="muxer", iter-upstream-comp-class-partial-descr="Sort messages from multiple inpu", iter-upstream-port-type=OUTPUT, iter-upstream-port-name="out", status=ERROR
08-06 07:22:48.227 28777 28777 W LIB/GRAPH consume_graph_sink@graph.c:473 Component's "consume" method failed: status=ERROR, comp-addr=0x18f2610, comp-name="pretty", comp-log-level=WARNING, comp-class-type=SINK, comp-class-name="pretty", comp-class-partial-descr="Pretty-print messages (`text` fo", comp-class-is-frozen=0, comp-class-so-handle-addr=0x186def0, comp-class-so-handle-path="/usr/lib/x86_64-linux-gnu/babeltrace2/plugins/babeltrace-plugin-text.so", comp-input-port-count=1, comp-output-port-count=0
08-06 07:22:48.227 28777 28777 E CLI cmd_run@babeltrace2.c:2548 Graph failed to complete successfully

ERROR:    [Babeltrace CLI] (babeltrace2.c:2548)
  Graph failed to complete successfully
CAUSED BY [libbabeltrace2] (graph.c:473)
  Component's "consume" method failed: status=ERROR, comp-addr=0x18f2610,
  comp-name="pretty", comp-log-level=WARNING, comp-class-type=SINK,
  comp-class-name="pretty", comp-class-partial-descr="Pretty-print messages
  (`text` fo", comp-class-is-frozen=0, comp-class-so-handle-addr=0x186def0,
  comp-class-so-handle-path="/usr/lib/x86_64-linux-gnu/babeltrace2/plugins/babeltrace-plugin-text.so",
  comp-input-port-count=1, comp-output-port-count=0
CAUSED BY [libbabeltrace2] (iterator.c:864)
  Component input port message iterator's "next" method failed:
  iter-addr=0x18f2e80, iter-upstream-comp-name="muxer",
  iter-upstream-comp-log-level=WARNING, iter-upstream-comp-class-type=FILTER,
  iter-upstream-comp-class-name="muxer",
  iter-upstream-comp-class-partial-descr="Sort messages from multiple inpu",
  iter-upstream-port-type=OUTPUT, iter-upstream-port-name="out", status=ERROR
CAUSED BY [muxer: 'filter.utils.muxer'] (muxer.c:1081)
  Youngest upstream message iterator wrapper's timestamp is less than muxer's
  message iterator's last returned timestamp: muxer-msg-iter-addr=0x18f2ff0,
  ts=1596631386358365554, last-returned-ts=1596631386358599346

I'm using below version.

Babeltrace 2.0.4 "Amqui" 

Amqui (/_mkwi_/) is a town in eastern Qu_bec, Canada, at the base of the Gasp_ peninsula in Bas-Saint-Laurent. Located at the confluence of the Humqui and Matap_dia Rivers, its proximity to
woodlands makes it a great destination for outdoor activities such as camping, hiking, and mountain biking.

Please let me know if you need a run with additional arguments.

#1

Updated by Jonathan Rajotte Julien 4 months ago

  • Status changed from New to Feedback

Hi Seongab,

Please provide a trace that results in this error.

Cheers.

#2

Updated by Jonathan Rajotte Julien 4 months ago

Also please provide the complete command line used.

Cheers

#3

Updated by Seongab Kim 4 months ago

Hi Jonathan,

Unfortunately the trace size is almost 1 GB and it contains rather sensitive customer data.
Is there any other way for me to help you to debug this issue further?

#4

Updated by Seongab Kim 4 months ago

And I just used below command without any special option.

babeltrace2 ./trace | grep printk_console
#5

Updated by Jonathan Rajotte Julien 4 months ago

Hi Seongab,

Seongab Kim wrote in #note-3:

Hi Jonathan,

Unfortunately the trace size is almost 1 GB and it contains rather sensitive customer data.

EfficiOS [1] can provides commercial support for babeltrace2 and the lttng ecosystem.

[1] https://www.efficios.com/contact/

Is there any other way for me to help you to debug this issue further?

Can you provide the overall tracing scenario, all lttng commands involved and the tracer version (ust, modules, lttng)?

Cheers

Also available in: Atom PDF