A blog on museum-digital and the broader digitization of museum work.

Between 6 a.m. and 9:15 a.m., museum-digital’s main server unfortunately experienced another outage. The immediate outage has been resolved now.

The larger issue remained the same as so often during the rocky months last year:

  • With IIIF processes stopping, they keep holding onto RAM, until eventually the server is overloaded
  • With no available RAM left, the database (MySQL) falls over

To bring back the server, we needed to:

  1. Stop the web server
  2. Restart PHP (freeing up RAM)
  3. Restart MySQL (bringing it back)
  4. Restart the web server

This was, to some extend, to be expected: PHP ran without issue for some weeks, and the outage shows in the real world how close we can get. As such, the solution will be to further reduce available resources for the IIIF setup and regularly restart PHP.


For some background, see also:

Leave a Reply

Your email address will not be published. Required fields are marked *

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)