-
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
nginx: [error] Failed to load tracing library /usr/local/lib/libjaegertracing.so #2738
Comments
Related to #2676? |
Added a minimal reproduction using the image, and an example here: https://github.com/opentracing-contrib/nginx-opentracing/tree/master/example/trivial/ubuntu-x86_64 |
Following https://github.com/opentracing-contrib/nginx-opentracing/tree/master/example/trivial/ubuntu-x86_64 more closely, and downloading the binary releases explicitly ( |
Looks like the built version of /usr/local/lib/libjaegertracing.so in the ingress-nginx docker image is the problem |
@mikebryant apologies for this issue. This weekend I will take a look at the generated library in the nginx image |
FYI I'm currently working on a fix, I'll hopefully have a PR for this tomorrow. I believe the issue is we need the plugin version of jaeger instead of the shared library, which is a different build option. I'm just waiting for it to build and I can test it later tonight |
Closing. Fixed in #2744 |
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see https://kubernetes.io/docs/tasks/debug-application-cluster/troubleshooting/.): No
What keywords did you search in NGINX Ingress controller issues before filing this one? (If you have found any duplicates, you should instead reply there.): Failed to load tracing library
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
NGINX Ingress controller version: 0.16.2
Kubernetes version (use
kubectl version
):Environment:
uname -a
):What happened:
Tried to upgrade to 0.16.2 from 0.15.0. Have opentracing with the jaeger backend configured. It fails to load, with the following output
What you expected to happen:
To be able to load the config
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
The text was updated successfully, but these errors were encountered: