mirror of
https://github.com/linuxserver/cstate.git
synced 2026-02-20 07:55:25 +08:00
31 lines
7.8 KiB
XML
31 lines
7.8 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://info.linuxserver.io"/><title>mariadb on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/mariadb/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-05-29T12:00:00+00:00</lastBuildDate><updated>2023-05-29T12:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/mariadb/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] Known Issue: MariaDB Check and Repair</title><link>https://info.linuxserver.io/issues/2023-05-29-mariadb/</link><pubDate>Mon, 29 May 2023 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-29-mariadb/</guid><category>2023-09-06 21:00:00Z</category><description>There is a known issue with MariaDB when updating the container image to a new version. If a database upgrade is required and user databases are not in a healthy state, then the MariaDB service may fail to start.
|
|
MariaDB version updates (ex: 10.6.x to 10.11.x) can happen when updating the container image. Upgrading user databases is done manually by running a command.
|
|
Recovery Procedure If you have recently updated your container image and your container logs show repeating entries of:</description><content type="html"><p>There is a known issue with MariaDB when updating the container image to a new version. If a database upgrade is required and user databases are not in a healthy state, then the MariaDB service may fail to start.</p>
|
|
<p>MariaDB version updates (ex: <code>10.6.x</code> to <code>10.11.x</code>) can happen when updating the container image. Upgrading user databases is done manually by running a command.</p>
|
|
<h3 id="recovery-procedure">Recovery Procedure</h3>
|
|
<p>If you have recently updated your container image and your container logs show repeating entries of:</p>
|
|
<pre tabindex="0"><code class="language-log" data-lang="log">Caught SIGTERM signal!
|
|
</code></pre><ul>
|
|
<li>Roll back the container image to a previous tag (ex: <code>lscr.io/linuxserver/mariadb:10.6.13</code> assuming this was the version you were running when things were last working)</li>
|
|
<li>Run the check, repair, analyze, and optimize commands, watch for any issues</li>
|
|
<li>Update the container image to the new tag (ex: <code>lscr.io/linuxserver/mariadb:10.11.3</code> or <code>lscr.io/linuxserver/mariadb:latest</code>)</li>
|
|
<li>Run the upgrade command</li>
|
|
</ul>
|
|
<p>This should get MariaDB running again with your user databases in a healthy state.</p>
|
|
<h3 id="check-and-repair">Check and Repair</h3>
|
|
<p>If user databases are not in a healthy state (sometimes caused by a failed upgrade), it may be remedied by running:</p>
|
|
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>mariadb-check -u root -p&lt;PASSWORD&gt; -c -A <span style="color:#75715e"># check all databases for errors</span>
|
|
</span></span><span style="display:flex;"><span>mariadb-check -u root -p&lt;PASSWORD&gt; -r -A <span style="color:#75715e"># repair all databases</span>
|
|
</span></span><span style="display:flex;"><span>mariadb-check -u root -p&lt;PASSWORD&gt; -a -A <span style="color:#75715e"># analyze all databases</span>
|
|
</span></span><span style="display:flex;"><span>mariadb-check -u root -p&lt;PASSWORD&gt; -o -A <span style="color:#75715e"># optimize all databases</span>
|
|
</span></span></code></pre></div><p>After running the above commands, you may need to run the upgrade command again.</p>
|
|
<h3 id="upgrading">Upgrading</h3>
|
|
<p>When this container initializes, if <code>MYSQL_ROOT_PASSWORD</code> is set an upgrade check will run. If an upgrade is required the log will indicate the need stop any services that are accessing databases in this container, and then run the command:</p>
|
|
<div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>mariadb-upgrade -u root -p&lt;PASSWORD&gt;
|
|
</span></span></code></pre></div><h3 id="closing-notes">Closing Notes</h3>
|
|
<p>If you are running MariaDB databases in production, we always recommend pinning the container image to a specific version tag, such as <code>lscr.io/linuxserver/mariadb:10.6.13-r0-ls97</code>, and planning any upgrades so that you can test and monitor them.</p></content></item><item><title>mariadb change to Alpine</title><link>https://info.linuxserver.io/issues/2021-08-25-mariadb-alpine/</link><pubDate>Wed, 25 Aug 2021 00:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2021-08-25-mariadb-alpine/</guid><category/><description>As previously announced we have now moved the MariaDB :alpine tag to :latest and deprecated our Ubuntu-based image. No user action is required when updating to the new tag, but as ever we recommend ensuring you have a proven backup of your data before performing any updates. Going forward, the :alpine tag will not receive any further updates.
|
|
If for some reason you need to remain on the old version, you can pin your install to the version-110.</description><content type="html"><p>As <a href="https://info.linuxserver.io/issues/2021-03-10-mariadb-alpine/">previously announced</a> we have now moved the MariaDB <code>:alpine</code> tag to <code>:latest</code> and deprecated our Ubuntu-based image. No user action is required when updating to the new tag, but as ever we recommend ensuring you have a proven backup of your data before performing any updates. Going forward, the <code>:alpine</code> tag will not receive any further updates.</p>
|
|
<p>If for some reason you need to remain on the old version, you can pin your install to the <code>version-110.4.21mariabionic</code> tag, although please be aware that no further updates will be provided for it.</p></content></item><item><title>mariadb change to Alpine</title><link>https://info.linuxserver.io/issues/2021-03-10-mariadb-alpine/</link><pubDate>Wed, 10 Mar 2021 00:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2021-03-10-mariadb-alpine/</guid><category/><description>We have created a new alpine based version of our mariadb container. Our intent is to move :alpine tag to :latest once ready. Further info on the timeline will follow in the coming weeks.</description><content type="html"><p>We have created a new alpine based version of our mariadb container.
|
|
Our intent is to move <code>:alpine</code> tag to <code>:latest</code> once ready. Further info on the timeline will follow in the coming weeks.</p></content></item><item><title>New Container: Mariadb</title><link>https://info.linuxserver.io/issues/2015-08-12-mariadb/</link><pubDate>Wed, 12 Aug 2015 00:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2015-08-12-mariadb/</guid><category/><description>We have released a new container for Mariadb!
|
|
Mariadb is one of the most popular database servers. Made by the original developers of MySQL.</description><content type="html"><p>We have released a new container for <a href="https://github.com/linuxserver/docker-mariadb">Mariadb</a>!</p>
|
|
<p><a href="https://mariadb.org/">Mariadb</a> is one of the most popular database servers. Made by the original developers of MySQL.</p></content></item></channel></rss> |