CODEWITHSUNDEEP
performancegonewrelicnewrelic-platform
Bondhan Novandy
Bondhan Novandy

Reputation: 402

Client timeout exceeded while awaiting headers

I got below error, I am using go v1.10.4 linux/amd64.

I am not behind any firewall or whatsoever. New Relic in java server (same network segment) that we have runs fine.

We have tried:

Below is our code:

    config := newrelic.NewConfig(os.Getenv("NEW_RELIC_APP_NAME"), os.Getenv("NEW_RELIC_KEY"))

    config.Logger = newrelic.NewDebugLogger(os.Stdout)

    app, err := newrelic.NewApplication(config)
    if err != nil {
        fmt.Println("Failed to create newrelic application", err)
        os.Exit(1)
    }

.................

        httpListener, err := net.Listen("tcp", *httpAddr)
        if err != nil {
            oldlog.Print("Error: ", err)
            logger.Log("transport", "HTTP", "during", "Listen", "err", err)
            os.Exit(1)
        }
        g.Add(func() error {
            logger.Log("transport", "HTTP", "addr", *httpAddr)
            return http.Serve(httpListener, nrgorilla.InstrumentRoutes(httpHandler, app))
        }, func(error) {
            httpListener.Close()
        })
    }

However this what we got,note some_key was removed:

(28422) 2019/07/29 18:08:50.058559 {"level":"warn","msg":"application connect failure","context":{"error":"Post https://collector-001.eu01.nr-data.net/agent_listener/invoke_raw_method?license_key=some_key\u0026marshal_format=json\u0026method=connect\u0026protocol_version=17: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"}}

Upvotes: 14

Views: 95737

Answers (2)

Sasi Kumar M
Sasi Kumar M

Reputation: 2630

On Windows OS, Running Linux Containers with WSL2, i followed the following steps,

  1. Ran the command docker logout
  2. Ran the command, docker network prune, so as to remove all the preconfigured settings of the network.
  3. From Docker Settings, Enabled the DNS server configuration with 8.8.8.8
  4. Restarted the Docker
  5. Now executed login command with registry to login, docker login {registry}

Upvotes: 0

Joshua Kan
Joshua Kan

Reputation: 395

I think it is due to DNS network timeout.

You can easily test this out by using the following steps (in Ubuntu)

  1. Select the IPv4 Settings tab.

  2. Disable the “Automatic” toggle switch and enter the DNS resolvers' IP addresses, separated by a comma. We’ll use the Google DNS nameservers:

    8.8.8.8,8.8.4.4

If it works, then you may be able to reset the DNS to "Automatic"

Upvotes: 6

Related Questions