Skip to content

docs: troubleshooting rack delete error #123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

docs: troubleshooting rack delete error #123

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
92cb6ae
Update troubleshooting rack delete error
moisesrodriguez Jul 9, 2021
6419730
Add Cloudwatch note
moisesrodriguez Jul 21, 2021
005a825
Update troubleshooting.md
ddoc Aug 27, 2021
c248203
Update troubleshooting.md
ddoc Aug 27, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/help/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,14 @@ When you know there is an issue and want to stop a deployment, you can run the `

As ALB routing rules must have a unique priority, Convox will generate a random one for each service in the range 1-50000 (the range allowed by AWS). This is generated from a checksum of the app name, service name, domain name, and a couple of other tweaks. It is very unlikely, but it is possible to have a collision between two separate services on the same rack. To solve this, simply slightly amend your app or service name to generate a different checksum.

## I get an error when deleting rack from Convox Console

### I get `ERROR: ValidationError: Stack with id rack-name does not exist`

When deleting a Rack from the Convox Console under certain circumstances the rack is removed from the Console, but the AWS resources are still in AWS. To remove resources you need to go to your AWS account console, then head over to CloudFormation in the same region your rack was created. Under stack there will be stacks with: `rack-name`, `rack-name-app-name`, `rack-name-console-xxx`. Select them and then click Delete from the CloudFormation options. This will remove all the resources created for your rack.

Note: Some resources as Cloudwatch logs might still exist after this process.

## My app deployed but I cannot access it

Run `convox services` to find the load balancer endpoints for your application.
Expand Down