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
Recently ran a deploy to production to verify if cron jobs were being correctly initiated on deploy and confirmed they are not.
This is most likely due to the api-server-instance-user-data.tpl.sh script not completing or errorring out at some point during execution. Additionally the api docker image did not start on deploy.
In order to manually fix:
sudo docker remove resources_portal_api
sudo ./start_api_with_migrations.sh
manually add back the cron jobs defined at the bottom of api-server-instance-user-data.sh
Solution or next step
Determine if the api-server-instance-user-data script is indeed erroring out and where
apply a fix and redeploy
The text was updated successfully, but these errors were encountered:
After inspecting the logs I came to a conclusion that the issue could be caused by a transient network error (Network is unreachable) or/and deb package mirrors error (Connection refused, Service Unavailable). This resulted in an incomplete package installation making awscli and certbot unavailable.
I ran the following commands to return the box into a usable state:
Context
Recently ran a deploy to production to verify if cron jobs were being correctly initiated on deploy and confirmed they are not.
This is most likely due to the
api-server-instance-user-data.tpl.sh
script not completing or errorring out at some point during execution. Additionally the api docker image did not start on deploy.In order to manually fix:
sudo docker remove resources_portal_api
sudo ./start_api_with_migrations.sh
api-server-instance-user-data.sh
Solution or next step
api-server-instance-user-data
script is indeed erroring out and whereThe text was updated successfully, but these errors were encountered: