jugovimm
commented
3 months ago Info for later:
- Able to recreate issue by using container.sh start and stopping the ES container as described; did not start landing page, attempted to access data.local
- Seemingly, no error logged to sentry for this when reproduced locally
- Running .init-webpack.sh makes the UI work again, but without ES info
on prod when there's an error we get a side effect error in the logs about the error jinja template:
... July 16, 2024 at 11:38 (UTC-7:00) | return self.ensure_sync(handler)(e) | web July 16, 2024 at 11:38 (UTC-7:00) | File "/usr/local/lib/python3.9/site-packages/invenio_theme/views.py", line 38, in page_not_found | web July 16, 2024 at 11:38 (UTC-7:00) | return render_template(current_app.config["THEME_404_TEMPLATE"]), 404 | web July 16, 2024 at 11:38 (UTC-7:00) | File "/usr/local/lib/python3.9/site-packages/flask/templating.py", line 147, in render_template ...
So it might be just a matter of figuring out why RDM's "THEME_404_TEMPLATE" isn't found
re-create this situation locally but starting everything up with ./container.sh start, then stop the elastic search container.