Skip to content

TCP Socket errors - Transport endpoint is already connected #40

Closed
@oini

Description

@oini

Hi there! We're using this module to log metrics for a high-frequency ETL service that is running on ECS where we have been noticing TCP socket 106 errors. A CloudWatch Agent container is setup as a sidecar alongside the application server in the ECS Task Definition that is responsible for publishing the metrics.

I'm trying to understand the root cause of these errors and how to avoid them. Any help is appreciated. Thanks!

Exact error:

[ERROR][tcp_client] Failed to connect to the socket. [Errno 106] Transport endpoint is already connected

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingin progressSomeone is actively working on this issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions