You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Receiver binary path is not executable: /usr/local/lib/python3.11/site-packages/ddtrace/internal/datadog/profiling/crashtracker/crashtracker_exe
#10901
def tracer_injection(logger, log_method, event_dict):
"""Integrate tracing and logging for Datadog."""
# get correlation ids from current tracer context
span = tracer.current_span()
trace_id, span_id = (span.trace_id, span.span_id) if span else (None, None)
# add ids to structlog event dictionary
event_dict["dd.trace_id"] = str(trace_id or 0)
event_dict["dd.span_id"] = str(span_id or 0)
# add the env, service, and version configured for the tracer
event_dict["dd.env"] = "dev"
event_dict["dd.service"] = "rhino-api"
event_dict["dd.version"] = ddtrace.config.version or ""
return event_dict
structlog.configure(processors=[tracer_injection, structlog.processors.JSONRenderer()])
logger = structlog.get_logger("app_logger")
logger.level = logging.INFO
and standard logging will produce above trace, even though the env is on ubuntu
What is the result that you get?
Receiver binary path is not executable: /usr/local/lib/python3.11/site-packages/ddtrace/internal/datadog/profiling/crashtracker/crashtracker_exe in logs
What is the result that you expected?
i am not seeing any datadog logs from my application without any app code update recently, except upgrading ddtrace. Expectation is seeing the logs in datadog logs
The text was updated successfully, but these errors were encountered:
👋 thank you for the report! crashtracker_exe is a utility binary we ship in ddtrace in order to provide better diagnostics around errors. The error you observe occurs when this utility cannot be executed. Typically, this would happen if we made a mistake in how we packaged the ddtrace wheel for pypi, since this is the most common way end-users acquire ddtrace. However, I checked the 3.11 wheels we have for 2.14.1, and:
every architecture that ships a crashtracker_exe utility has it marked executable
every architecture that ships a crashtracker_exe utility has an appropriate version for the given architecture (the same error may arise e.g., if an x86_64 binary was run on an arm machine)
similarly, all the crashtracker_exe appear to have a valid interpreter (usually some platform-specific path to ld.so) for the given architecture
This could mean that the error message is achievable some other way, or there is something interesting about your setup.
Could you write a few words about how you install ddtrace (e.g., you install through pip, you build from sources, etc)
Could you describe your platform (e.g., alpine linux on aarch64, ubuntu 18.04 on i686, macos on an m1 laptop, etc)
Thanks again! This is an unusual error and it may take a little sleuthing to figure out how it appears.
Summary of problem
Which version of dd-trace-py are you using?
2.14.1
Which version of pip are you using?
24.0
Which libraries and their versions are you using?
datadog = "^0.45.0"
How can we reproduce your problem?
There are 2 relevant code snippets that we are using ddtrace
patch the python logging
using the structlog example:
and standard logging will produce above trace, even though the env is on ubuntu
What is the result that you get?
Receiver binary path is not executable: /usr/local/lib/python3.11/site-packages/ddtrace/internal/datadog/profiling/crashtracker/crashtracker_exe in logs
What is the result that you expected?
i am not seeing any datadog logs from my application without any app code update recently, except upgrading ddtrace. Expectation is seeing the logs in datadog logs
The text was updated successfully, but these errors were encountered: