When a server is restarted, RabbitMQ stops and then Docker stops. When RabbitMQ becomes unavailable, the Docker containers end up reporting a bunch of errors to Sentry. If we shut down Docker first, they won't do that.
I don't know if perhaps there's something we can do in /etc/init.d.
Applies to ocp13 and ocp23.
From testing locally:
Ensure RabbitMQ is running
Run kingfisher-process ./manage.py runserver in a tab
When a server is restarted, RabbitMQ stops and then Docker stops. When RabbitMQ becomes unavailable, the Docker containers end up reporting a bunch of errors to Sentry. If we shut down Docker first, they won't do that.
I don't know if perhaps there's something we can do in
/etc/init.d
.Applies to ocp13 and ocp23.
From testing locally:
Ensure RabbitMQ is running
Run kingfisher-process
./manage.py runserver
in a tabStart a crawl:
Stop RabbitMQ
Produces crawl log like: