<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>museum-digital:blog - Server outage</title>
    <subtitle>A blog on museum-digital and the broader digitization of museum work.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://blog.museum-digital.org/tags/server-outage/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://blog.museum-digital.org"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-02-24T00:00:00+00:00</updated>
    <id>https://blog.museum-digital.org/tags/server-outage/atom.xml</id>
    <entry xml:lang="en">
        <title>md:down (Temporarily)</title>
        <published>2026-02-24T00:00:00+00:00</published>
        <updated>2026-02-24T00:00:00+00:00</updated>


        
        <author>
          <name>Joshua Ramon Enslin</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.museum-digital.org/2026/02/24/mddown-temporarily/"/>
        <id>https://blog.museum-digital.org/2026/02/24/mddown-temporarily/</id>
        
        <content type="html" xml:base="https://blog.museum-digital.org/2026/02/24/mddown-temporarily/">&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;The larger issue remained the same as so often during the rocky months last year:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;With IIIF processes stopping, they keep holding onto RAM, until eventually the server is overloaded&lt;/li&gt;
&lt;li&gt;With no available RAM left, the database (MySQL) falls over&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To bring back the server, we needed to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Stop the web server&lt;/li&gt;
&lt;li&gt;Restart PHP (freeing up RAM)&lt;/li&gt;
&lt;li&gt;Restart MySQL (bringing it back)&lt;/li&gt;
&lt;li&gt;Restart the web server&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;For some background, see also:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;https://blog.museum-digital.org/2025/12/29/trimming/&quot;&gt;Trimming.&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://blog.museum-digital.org/2025/12/22/cleaning-out-our-closet/&quot;&gt;Cleaning Out Our Closet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;https://blog.museum-digital.org/2025/12/09/updates-ai-scrapers-and-resilience/&quot;&gt;Updates, AI scrapers, and Resilience&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;div
  class=&quot;my-4 flex flex-col rounded-lg bg-(--admonition-bg)&quot;
  style=&quot;--admonition-bg: var(--admonition-info);&quot;
&gt;
  &lt;div class=&quot;flex items-center rounded-t-lg bg-(--admonition-bg) p-1&quot;&gt;
    &lt;div
      class=&quot;mx-2 h-4 w-4 text-[0px] [background:var(--url)_center_center_no-repeat] dark:invert&quot;
      style=&quot;--url: url(icons/info.svg);&quot;
    &gt;
      info
    &lt;/div&gt;
    &lt;span&gt;&lt;strong&gt;License&lt;/strong&gt;&lt;/span&gt;
  &lt;/div&gt;
  &lt;div class=&quot;pl-4&quot;&gt;&lt;p&gt;This content is licensed under a &lt;a rel=&quot;external&quot; href=&quot;https://creativecommons.org/licenses/by/4.0/&quot;&gt;Creative Commons Attribution 4.0 International license&lt;/a&gt;.&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;
</content>

        
        
        <post-thumbnail><url>https://blog.museum-digital.org/2026/02/24/mddown-temporarily/IMG_0438-scaled.png</url></post-thumbnail>
        
        
    </entry>
    <entry xml:lang="en">
        <title>Maintenance / Outage: Search Database not Available for Today</title>
        <published>2025-06-11T00:00:00+00:00</published>
        <updated>2025-06-11T00:00:00+00:00</updated>


        
        <author>
          <name>Joshua Ramon Enslin</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.museum-digital.org/2025/06/11/maintenance-outage-search-database-not-available-for-today/"/>
        <id>https://blog.museum-digital.org/2025/06/11/maintenance-outage-search-database-not-available-for-today/</id>
        
        <content type="html" xml:base="https://blog.museum-digital.org/2025/06/11/maintenance-outage-search-database-not-available-for-today/">&lt;p&gt;Some minutes ago, our search server crashed. To bring everything back to normal, we will have to re-index, which will take a few hours. As that is being done, most of the frontend will remain operational without issue. musdb will, depending on the instance, be unavailable into the night.&lt;/p&gt;
</content>

        
        
        
    </entry>
    <entry xml:lang="en">
        <title>Server Outage / Switch Fault (March 6th, 2024)</title>
        <published>2024-03-06T00:00:00+00:00</published>
        <updated>2024-03-06T00:00:00+00:00</updated>


        
        <author>
          <name>Joshua Ramon Enslin</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.museum-digital.org/2024/03/06/server-outage-switch-fault/"/>
        <id>https://blog.museum-digital.org/2024/03/06/server-outage-switch-fault/</id>
        
        <content type="html" xml:base="https://blog.museum-digital.org/2024/03/06/server-outage-switch-fault/">&lt;p&gt;Between March 6th, 2024, 9:54 a.m. and 10:34 a.m. museum-digital’s main server was unavailable due to a switch fault at the data center at our hosting provider, Hetzner. Details can be seen here on &lt;a rel=&quot;external&quot; href=&quot;https://status.hetzner.com/incident/f9758dfb-0bc2-440e-8743-0c322194b682&quot;&gt;Hetzner&lt;/a&gt;’s website.&lt;/p&gt;
&lt;p&gt;By 10:34 the error was fixed by the technicians in the data center and all systems at museum-digital are operational again.&lt;/p&gt;
&lt;p&gt;We are sorry for the downtime and looking into ways to better mitigate similar issues in the future.&lt;/p&gt;
</content>

        
    </entry>
</feed>
