53612: bind: address already in use

[JachMinen]

---

name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''

---

Describe the bug
Lambda will occasionally encounter this error during initialization of environment:
telemetryAPI.Listener
Unexpected stop on HTTP Server
listen tcp ---.---.---.---:53612: bind: address already in use
When this happens, the next invocation will run successfully at first, but then time out when trying to export metrics.
This only seems to happen on cold start of new environment and usually resolves itself after 1 or 2 invocations in that environment.

Steps to reproduce
Unknown

What did you expect to see?
Lambda runs and metrics are exported successfully

What did you see instead?
Lambda times out

What version of collector/language SDK version did you use?
Version: aws-otel-python-amd64-ver-1-20-0:3

What language layer did you use?
Config: Python3.9

Additional context
Lambda also has layers for Lambda Insights and Python libraries

[drobert]

We've been bumping into this, too. We're using a fastapi python app in a docker-based lambda also using aws-otel-python-amd64-ver-1-20-0:3

[Xaaris]

Same here on aws-otel-collector-arm64-ver-0-90-1:1

[jan-xyz]

@drobert and @JachMinen are you using otlptracegrpc.WithDialOption(grpc.WithBlock()) for your SDK client setup?