Connection problem after gb build all?

[roel4d]

Not sure if this is a problem with my code, the SDK or AWS.

When I build a Go program and run it the first time, I always get the error below.
If I run the same program for a second time it works.
What could case this?

I'm using 'gb build all', but I don't think that should make a difference?

RequestError: send request failed
caused by: Get https://s3-eu-west-1.amazonaws.com/somefakebucket: dial tcp 54.231.140.88:443: ConnectEx tcp: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

[jasdel]

Hi @r03 are you able to reproduce this with any other endpoint, or simple Go program? This sounds like a local connection issues, since the connection failure is not consistent. I doubt gb is causing any issue, but it may be helpful to try the program using the standard Go build environment.

It may be helpful to take a look at the wirelog produced by the SDK. A simple request to experiment with this is:

svc := s3.New(&aws.Config{Region:  "eu-west-1", LogLevel: 1})
result, err := svc.ListBuckets(&s3.ListBucketsInput{})

[roel4d]

I had the same problem with the code below.
Using go or gb didn't matter.
After disabling the antivirus (bitdefender) it seemed to be solved.
I guess the antivirus checks new exe's or something.

svc := s3.New(&aws.Config{Region: "eu-central-1", LogLevel: 1})
result, err := svc.ListBuckets(&s3.ListBucketsInput{})
if err != nil {
    fmt.Printf("ERROR %v", err)
}
for _, bucket := range result.Buckets {
    fmt.Printf("%s \n", *bucket.Name)
}

[roel4d]

It worked a couple of times after disabling the auto pilot mode in bitdefender, but now I have the same problem again. But I will leave this ticket closed because this seems like a local problem.