Waypont deploy fails: ! transport is closing

Waypoint
1

Hi,
I am new to waypoint and I am using it with gitlab on aws to deploy a simple web-application. I followed the instruction (Integrating Waypoint with GitLab CI/CD | Waypoint by HashiCorp) and everything worked fine in the beginning. After developing the application further, I am facing now the issue that every running pipeline fails.

$ waypoint deploy
Deploying...
Found existing ECS cluster: waypoint
Found existing IAM role to use: ecr-xyz-core
! transport is closing
Cleaning up file based variables
ERROR: Job failed: exit code 1

Does anyone have a hint for me what exactly goes wrong and how I can fix that?

2

Welcome! If you’re running 0.2.2 and using aws-ecs, this is likely a known bug that we’ll be doing a release today to correct. In the meantime, you can use v0.2.1 or try adding an empty logging {} block to your deploy, for example:
use “aws-ecs” {
region = “us-east-1”
memory = “512”
logging {}
}

If this is doesn’t fix it, please share your waypoint hcl for more troubleshooting.

1 Like
3

Thanks for the feedback, the workaround logging {} worked.
thank you! :+1:

1 Like
4

We just released 0.2.3 which includes this fix. Glad the workaround did the trick as well!
https://discuss.hashicorp.com/t/waypoint-0-2-3-released/21323/2

1 Like
5

Hi
I just update to 0.2.3 and still get the error, even with the logging {} trick.

Deploying…

  • Found existing ECS cluster: waypoint
  • Found existing IAM role to use: ecr-example-nodejs
  • Using default subnets for Service networking
    ! transport is closing

as you can see I am just trying the AWS tutorial.

6

@fmiche did you update both your local CLI and remote server versions?

7

I was able to successfully install a 0.2.3 server both locally on Docker and remotely on EKS, and successfully run waypoint up on each installation with the below hcl file. Let me know if you are able to verify your server version and we’ll go from there!

project = "example-nodejs"

app "example-nodejs" {
  labels = {
    "service" = "example-nodejs",
    "env" = "dev"
  }

  build {
    use "pack" {}
    registry {
      use "aws-ecr" {
        region = "us-east-1"
        repository = "waypoint-example"
        tag = "latest"
      }
    }
  }

  deploy {
    use "aws-ecs" {
      region = "us-east-1"
      memory = "512"
    }
  }
}
8

@krantzinator I checked local CLI and docker Waypoint server. they are both 0.2.3.
© 2021 HashiCorp

  • Waypoint v0.2.3
  • API: v1
  • Entrypoint: v1

Still getting

» Deploying…

  • Found existing ECS cluster: waypoint
  • Found existing IAM role to use: ecr-example-nodejs
  • Using default subnets for Service networking
    ! transport is closing
9

@fmiche are you able to run the up command with -vvv and see if any useful ERROR messages come through?

10

@krantzinator : Here it is:
» Deploying…

  • Found existing ECS cluster: waypoint
  • Found existing IAM role to use: ecr-example-nodejs
  • Using default subnets for Service networking
    ! transport is closing
    2021-03-05T09:34:12.841+0100 [ERROR] waypoint.runner.config_recv: error receiving configuration, exiting: err=“rpc error: code = Unknown desc = context canceled”
    2021-03-05T09:34:12.841+0100 [TRACE] waypoint.runner.config_recv: exiting receive goroutine
    2021-03-05T09:34:12.841+0100 [TRACE] waypoint: stopping signal listeners and cancelling the context
    2021-03-05T09:34:12.841+0100 [WARN] waypoint: context cancelled, stopping interrupt listener loop
11

We need to figure out if the error is bubbling up as part of attempting to create the default subnets, or as part of creating the ALB after the subnet step completes.
Do you have useful logs on your AWS side?

12

I also have the same issue. I am running the project waypoint-examples/aws/aws-ecs/nodejs

levent@Levents-MBP waypoint-examples % waypoint --version
CLI: v0.4.0 (3b3dd831)
Server: v0.4.0
levent@Levents-MBP waypoint-examples %

and getting the error

2021-06-24T22:30:24.789+0200 [WARN]  waypoint.runner.app.example-nodejs.deploy: error during local operation: id=01F8ZVESS5GWQND406W2D44PQW job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy err="rpc error: code = Unavailable desc = transport is closing"
 + Found existing ECS cluster: waypoint
 + Found existing IAM role to use: ecr-example-nodejs
 + Using default subnets for Service networking2021-06-24T22:30:25.189+0200 [DEBUG] waypoint.runner.app.example-nodejs.deploy: metadata marked as complete: id=01F8ZVESS5GWQND406W2D44PQW job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy
2021-06-24T22:30:25.189+0200 [DEBUG] waypoint.runner.app.example-nodejs.platform: plugin exited: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy
2021-06-24T22:30:25.189+0200 [DEBUG] waypoint.runner: closing project: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy
2021-06-24T22:30:25.189+0200 [TRACE] waypoint.runner: closing app: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy app=example-nodejs
2021-06-24T22:30:25.190+0200 [WARN]  waypoint.runner.app.example-nodejs.mapper.stdio: received EOF, stopping recv loop: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy err="rpc error: code = Unavailable desc = transport is closing"
2021-06-24T22:30:25.192+0200 [DEBUG] waypoint.runner.app.example-nodejs.mapper: plugin process exited: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy path=/usr/local/bin/waypoint pid=41618
2021-06-24T22:30:25.193+0200 [DEBUG] waypoint.runner.app.example-nodejs.mapper: plugin exited: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy
2021-06-24T22:30:25.193+0200 [WARN]  waypoint.runner.app.example-nodejs.mapper.stdio: received EOF, stopping recv loop: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy err="rpc error: code = Unavailable desc = transport is closing"
2021-06-24T22:30:25.195+0200 [DEBUG] waypoint.runner.app.example-nodejs.mapper: plugin process exited: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy path=/usr/local/bin/waypoint pid=41619
2021-06-24T22:30:25.195+0200 [DEBUG] waypoint.runner.app.example-nodejs.mapper: plugin exited: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy
2021-06-24T22:30:25.195+0200 [DEBUG] waypoint.runner: job finished: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy error="rpc error: code = Unavailable desc = transport is closing"
2021-06-24T22:30:25.195+0200 [WARN]  waypoint.runner: error during job execution: job_id=01F8ZVERDYDSEE9NFF3AQD8PRS job_op=*gen.Job_Deploy err="rpc error: code = Unavailable desc = transport is closing"
2021-06-24T22:30:25.199+0200 [DEBUG] waypoint.runner: opening job stream
2021-06-24T22:30:25.199+0200 [TRACE] waypoint.runner: sending job request
2021-06-24T22:30:25.199+0200 [INFO]  waypoint.runner: waiting for job assignment
 + Found existing ECS cluster: waypoint
 + Found existing IAM role to use: ecr-example-nodejs
 + Using default subnets for Service networking
! transport is closing
2021-06-24T22:30:25.200+0200 [TRACE] waypoint: stopping signal listeners and cancelling the context
2021-06-24T22:30:25.200+0200 [WARN]  waypoint: context cancelled, stopping interrupt listener loop
levent@Levents-MBP nodejs %

and running waypoint on a MacBook Pro.

13

Where is your server installed?

14

Hi. I am not sure if you asked the question to me. Waypoint is installed on my MacBook Pro and trying to deploy to AWS eu-central, eu-west, eu-east.

15

@ltutar can you provide more information on your exact steps? I am not able to recreate this error, so in order for me to help I need a few more details on the setup.

  • Is your server installed locally on Docker? What version of docker?
  • What version of the Waypoint server?
  • What waypoint.hcl are you using?

I am guessing there is some configuration in your AWS account that may be colliding here, but I’m not sure what that might be at this time.

16

Can you run:

export WAYPOINT_LOG_LEVEL=debug

and re-run your command with -vvv?

1 Like