[BUG] failed to send, dropping xxx traces to intake at xxx after 3 retries ([Errno 111] Connection refused)

[sachams]

Agent Environment

• Agent version 3.30.8
• Python ddtrace version 1.12.6

	"sourceLocation": {
		"file": "/usr/local/lib/python3.10/site-packages/ddtrace/internal/writer.py",
		"line": 464,
		"function": "flush_queue"
	}

Describe what happened:

We frequently see this error in all our environments, for example:

failed to send, dropping 23 traces to intake at http://10.154.0.10:8126/v0.5/traces after 3 retries ([Errno 111] Connection refused)

DataDog is otherwise functioning fine. Would like to stop these errors being generated though.

Describe what you expected:

No errors.

Steps to reproduce the issue:

• Deploy datadog helm 3.30.8
• Use ddtrace in a Python application

Additional environment details (Operating System, Cloud provider, etc):

• Running on python:3.10.10-slim-bullseye on GKE

[darkwind-noveo]

U should see happening datadog agent logs at this time. Highly likely your agent is rapidly restarting, because each time it exits for some reason

[ricardodani]

I'm having the same, would like to stop it too

[vkaracic]

Same issue here, @sachams have you found a fix for this?

[luciidlou]

bump

[miguelgf]

Do we have any ETA for this to be solved or a workaround?

[jmborsani]

+1

[domino14]

please fix