dfinity / dfinity/sdk

Too many open files & failed to lookup address information: nodename nor servname provided, or not known

Open
#3,366 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs-triage
Dominant language
Rust
Stars
204
Forks
98
PR merge metrics
No merged PRs in 30d

Description

I tried the following:

  1. deploy the canister
  2. call update method of canister

I expected to see this happen: call method success

Instead, this happened:

 Sep 15 07:19:40.068 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "tcp open error",
        Os {
            code: 24,
            kind: Uncategorized,
            message: "Too many open files",
        },
    ),
)
 Sep 15 07:19:40.068 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "dns error",
        Custom {
            kind: Uncategorized,
            error: "failed to lookup address information: nodename nor servname provided, or not known",
        },
    ),
)
Meta

dfx --version:

0.14.4
Further log output

version: 0.8.1
 Sep 15 07:19:39.192 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "dns error",
        Custom {
            kind: Uncategorized,
            error: "failed to lookup address information: nodename nor servname provided, or not known",
        },
    ),
)
 Sep 15 07:19:39.194 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "dns error",
        Custom {
            kind: Uncategorized,
            error: "failed to lookup address information: nodename nor servname provided, or not known",
        },
    ),
)
 Sep 15 07:19:39.194 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "tcp open error",
        Os {
            code: 24,
            kind: Uncategorized,
            message: "Too many open files",
        },
    ),
)
 Sep 15 07:19:39.194 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "tcp open error",
        Os {
            code: 24,
            kind: Uncategorized,
            message: "Too many open files",
        },
    ),
)
 Sep 15 07:19:39.194 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "tcp open error",
        Os {
            code: 24,
            kind: Uncategorized,
            message: "Too many open files",
        },
    ),
)
 Sep 15 07:19:39.194 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "tcp open error",
        Os {
            code: 24,
            kind: Uncategorized,
            message: "Too many open files",
        },
    ),
)
 Sep 15 07:19:39.194 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "tcp open error",
        Os {
            code: 24,
            kind: Uncategorized,
            message: "Too many open files",
        },
    ),
)
 Sep 15 07:19:39.216 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "dns error",
        Custom {
            kind: Uncategorized,
            error: "failed to lookup address information: nodename nor servname provided, or not known",
        },
    ),
)
 Sep 15 07:19:39.216 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "tcp open error",
        Os {
            code: 24,
            kind: Uncategorized,
            message: "Too many open files",
        },
    ),
)
 Sep 15 07:19:39.217 WARN Internal Error during request:
hyper::Error(
    Connect,
    ConnectError(
        "dns error",
        Custom {
            kind: Uncategorized,
            error: "failed to lookup address information: nodename nor servname provided, or not known",
        },
    ),
)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the deployment and canister update call described in the issue with dfx 0.14.4, then collect the verbose logs around the Hyper connection errors. Done means the update call succeeds without the reported “Too many open files” or DNS lookup failures; the issue does not name a source file or test to inspect.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.