...
heroku ps -a scihist-digicoll-production
(Note if a restart/redeploy just happened, and you have heroku preboot on, you may not be seeing status of dynos actually serving requests. 😞 See “disable preboot” below.)
Look at our logs
Consolidated app logs are avilable on heroku dashboard, on “resources” tab, click on “papertrail” add-on at bottom to get a nice web GUI for our logs, that also lets you search.
...
Also in addition to general logs, we have errors specifically monitored by http://honeybadger.io , each person has their own individual login.
Disable preboot
The heroku preboot feature makes it possible for us to do zero-downtime deploys, but also really complicates visibility/introspection into heroku dynos, and quick-response to making changes like dyno restarts and redeploys.
If you are troubleshooting an already problematic/downtime situation, it might make sense to turn off preboot to make things more straightforward:
heroku features:disable preboot -a scihist-digicoll-production
You can enable it again with enable instead of disable.
Is heroku itself having problems? Or are other platforms we use?
...
| Code Block |
|---|
heroku ps:restart worker -a scihist-digicoll-production heroku ps:restart web -a scihist-digicoll-production heroku ps:restart worker.2 -a scihist-digicoll-production |
Note: It’s not clear to me how often this restarting heroku dynos will actually fix a problem, and in some cases it could cause a less stable state, if for instance heroku is having problems.
Note: If heroku “preboot” is on, it can take 3+ minutes for restart to actually take effect. See “disable preboot” above.
Restart solr on Searchstax
...