-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Segmentation fault upon loading libjaegertracing_plugin.so #2856
Comments
+1 NGINX Ingress controller version: 0.17.1 Environment: What happened:
How to reproduce it:
|
Closing. Please reopen if the issue persists after testing the mentioned image |
I can confirm that the segfault is fixed in the latest image tag ( |
What's the timeline for getting this out of |
@jaredallard 0.18.0 contains the fix |
Is this a BUG REPORT or FEATURE REQUEST?: Bug report
NGINX Ingress controller version: 0.17.1
Kubernetes version: 1.10
Environment:
uname -a
): 3.10What happened:
This instruction in
nginx.conf
:Causes a segmentation fault and an Nginx crash at startup:
The instruction causing the crash is
opentracing_load_tracer
.I verified the contents of
/etc/nginx/opentracing.json
and it looks fine.How to reproduce it
I can reproduce this with a simple backed
nginx.conf
and the config test command:nginx -t
.Anything else we need to know:
This is similar to #2222 which was also a segfault caused by the tracing plugin, except it was for Zipkin instead of Jeager.
The text was updated successfully, but these errors were encountered: