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
This process is being twitchy. It runs sometimes and not others. We were not able to pin down why. It worked great in the previous production system for years.
Potential future work
Production is currently configured to run jobs :async. If you set up sidekiq or some other job system, you can update production environment to run in background.
If you switch to background jobs, the Pingdom process should still work. Instead of getting a time out, the page will return an error on the 4:10 am load if one of the authorities is failing. The slight change is that you will no longer see the down/up pattern. You will only see a down when an authority is failing.
The text was updated successfully, but these errors were encountered:
Redeploy the system - This seemed to work sometimes and have no affect other times. And redeploying has its own issues where the system doesn't come back up sometimes.
Turn off performance calculations by turning off performance related displays in the production env file in S3. The calculations are very processor intensive.
NOTE: I've never gotten Graph generation to work in Elastic Beanstalk even though they run fine on my laptop. I wasn't able to test them in the new setup because of this issue.
I reset the preferred time zone to a time that expired the cache during the day when I could watch it fail. Only it never failed when I did that. This could mean there is something unique happening during the night that is causing the failure.
Normal process
See Monitoring Connections to Authorities to understand the normal processing.
Current problem
This process is being twitchy. It runs sometimes and not others. We were not able to pin down why. It worked great in the previous production system for years.
Potential future work
The text was updated successfully, but these errors were encountered: