You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/deployment/troubleshooting.md
+24
Original file line number
Diff line number
Diff line change
@@ -60,6 +60,28 @@ If Terraform commands fail (locally or in the Pipeline) due to an `Error acquiri
60
60
1.**Do any engineers have a Terrafrom command running locally?** You'll need to ask them. For example: They may have started an `apply` and it's sitting waiting for them to [approve](https://developer.hashicorp.com/terraform/cli/commands/apply#automatic-plan-mode) it. They will need to (gracefully) exit for the lock to be released.
61
61
1.**If none of the steps above identified the source of the lock**, and especially if the `Created` time is more than ten minutes ago, that probably means the last Terraform command didn't release the lock. You'll need to grab the `ID` from the `Lock Info` output and [force unlock](https://developer.hashicorp.com/terraform/language/state/locking#force-unlock).
62
62
63
+
### App fails to start
64
+
65
+
If the container fails to start, you should see a [downtime alert](#monitoring). Assuming this app version was working in another [environment](../infrastructure/#environments), the issue is likely due to misconfiguration. Some things you can do:
66
+
67
+
- Check the [logs](#logs)
68
+
- Ensure the [environment variables](../../configuration/environment-variables/) and [configuration data](../../configuration/data/) are set properly.
69
+
-[Turn on debugging](../../configuration/environment-variables/#django_debug)
70
+
- Force-push/revert the [environment](../infrastructure/#environments) branch back to the old version to roll back
71
+
72
+
### Littlepay API issue
73
+
74
+
Littlepay API issues may show up as:
75
+
76
+
- The [monitor](https://github.com/cal-itp/benefits/actions/workflows/check-api.yml) failing
77
+
- The `Connect your card` button doesn't work
78
+
79
+
A common problem that causes Littlepay API failures is that the certificate expired. To resolve:
1. Put that certificate into the [configuration data](../../configuration/data/) and/or the [GitHub Actions secrets](https://github.com/cal-itp/benefits/settings/secrets/actions)
84
+
63
85
### Eligibility Server
64
86
65
87
If the Benefits application gets a 403 error when trying to make API calls to the [Eligibility Server](https://docs.calitp.org/eligibility-server/), it may be because the outbound IP addresses changed, and the Eligibility Server firewall is still restricting access to the old IP ranges.
@@ -70,3 +92,5 @@ If the Benefits application gets a 403 error when trying to make API calls to th
70
92
1. Click `Edit`
71
93
1. Click `Variables`
72
94
1. Update the relevant variable with the new list of CIDRs
95
+
96
+
Note there is nightly downtime as the Eligibility Server restarts and loads new data.
0 commit comments