Skip to content

gbproxy container crashes because of a timeout issue on fetch #89

@GitHelge

Description

@GitHelge

It seems that our gbproxy container crashes (and restarts) when there is an issue from undici.

We first saw the issue May 10 15:02:48Z in our logs and since then it happened 28 times that the proxy crashed.

repo-gbproxy-1  | Node.js v18.20.4
repo-gbproxy-1  | error Command failed with exit code 1.
repo-gbproxy-1  | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
repo-gbproxy-1  | `yarn start` failed with exit code 1
repo-gbproxy-1 error Command failed with exit code 1.
repo-gbproxy-1 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
repo-gbproxy-1  | node:internal/deps/undici/undici:12618
repo-gbproxy-1  |     Error.captureStackTrace(err, this);
repo-gbproxy-1  |           ^
repo-gbproxy-1  | 
repo-gbproxy-1  | TypeError: fetch failed
repo-gbproxy-1  |     at node:internal/deps/undici/undici:12618:11
repo-gbproxy-1  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
repo-gbproxy-1  |   cause: ConnectTimeoutError: Connect Timeout Error
repo-gbproxy-1  |       at onConnectTimeout (node:internal/deps/undici/undici:7760:28)
repo-gbproxy-1  |       at node:internal/deps/undici/undici:7716:50
repo-gbproxy-1  |       at Immediate._onImmediate (node:internal/deps/undici/undici:7748:13)
repo-gbproxy-1  |       at process.processImmediate (node:internal/timers:476:21) {
repo-gbproxy-1  |     code: 'UND_ERR_CONNECT_TIMEOUT'
repo-gbproxy-1  |   }
repo-gbproxy-1  | }

I found this (maybe) related issue but i dont think we can change something on our side regarding this.
nodejs/undici#4215

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions