Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jaeger Native Tracing broken with envoy proxy 1.13.0 #9849

Closed
pol-leleux opened this issue Jan 28, 2020 · 5 comments
Closed

Jaeger Native Tracing broken with envoy proxy 1.13.0 #9849

pol-leleux opened this issue Jan 28, 2020 · 5 comments
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@pol-leleux
Copy link

Jaeger Native Tracing doesn't seem to work anymore with the latest 1.13.0 envoy proxy version. The container keeps crashing.

Please see the logs below :

[2020-01-28 15:45:28.139][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:83] Caught Segmentation fault, suspect faulting address 0x30,
[2020-01-28 15:45:28.139][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:70] Backtrace (use tools/stack_decode.py to get line numbers):,
[2020-01-28 15:45:28.139][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:71] Envoy version: bb7ceff/1.13.0/Clean/RELEASE/BoringSSL,
[2020-01-28 15:45:28.140][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:77] #0: [0x7f8bfa68c420],
[2020-01-28 15:45:28.140][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:77] #1: [0x560dd56d3e5a],
[2020-01-28 15:45:28.140][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:77] #2: [0x560dd50f58ed],
[2020-01-28 15:45:28.140][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #3: jaegertracing::propagation::Propagator<>::extract() [0x7f8bf807bffe],
[2020-01-28 15:45:28.141][30][critical][backtrace] [bazel-out/k8-opt/bin/source/server/_virtual_includes/backtrace_lib/server/backtrace.h:75] #4: jaegertracing::Tracer::Extract() [0x7f8bf807c31a],

@lizan
Copy link
Member

lizan commented Jan 28, 2020

This is due to the standard C++ library change, assuming you're using official docker image of Envoy and pre-built Jaeger OpenTracing binary.

See https://groups.google.com/forum/#!topic/envoy-announce/GvoxIMSpt8A

@mattklein123 mattklein123 added the question Questions that are neither investigations, bugs, nor enhancements label Feb 5, 2020
@stale
Copy link

stale bot commented Mar 6, 2020

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Mar 6, 2020
@prahaladramji
Copy link

rebuilding the jaeger-client-cpp worked with the latest image
Patch Build, to build with libc++ tested and working with envoyproxy/envoy:v1.13.1 ubuntu image.
jaegertracing/jaeger-client-cpp#183 (comment)

@stale
Copy link

stale bot commented Apr 6, 2020

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Apr 6, 2020
@stale
Copy link

stale bot commented Apr 13, 2020

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

4 participants