The Culture In-Time server displayed a default Heroku 500 Error page. The root cause was a frozen GraphDB instance on LightSail.
Timeline
Gregory because aware of the situation by chance while going to the Staging server for Culture In-Time
Gregory tried SSH into the unix server, but could not and no response was available from the SSH session. Despite this, the LightSail instance displayed "Running".
Gregory restarted the LightSail instance and service was back to normal.
A monitoring service should be setup for the GraphDB running on LightSail before this project goes into production.
saumier
commented
10 months ago
Summary
The Culture In-Time server displayed a default Heroku 500 Error page. The root cause was a frozen GraphDB instance on LightSail.
Timeline
Gregory because aware of the situation by chance while going to the Staging server for Culture In-Time
Gregory tried SSH into the unix server, but could not and no response was available from the SSH session. Despite this, the LightSail instance displayed "Running".
Gregory restarted the LightSail instance and service was back to normal.
A monitoring service should be setup for the GraphDB running on LightSail before this project goes into production.