mirror of
https://github.com/linuxserver/cstate.git
synced 2026-02-20 07:55:25 +08:00
deploy: 884167df0f28af65ff2f4c45db964ab27c90c234
This commit is contained in:
nemchik
parent
fc1e88a1c0
commit
123daa7480
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"Known Issues","permalink":"https://info.linuxserver.io/affected/known-issues/","status":"notice","pages":[{"is":"issue","title":"Known Issue: Portainer & Synology Docker UI","createdAt":"2023-05-22 12:00:00 +0000 UTC","lastMod":"2023-05-22 14:22:54 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2023-05-22-portainer/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","portainer","synology"],"filename":"2023-05-22-portainer.md"},{"is":"issue","title":"Known Issue: Heimdall 2.5.0 & 2.5.1 Releases","createdAt":"2022-11-25 16:00:00 +0000 UTC","lastMod":"2022-11-25 17:38:10 +0000 UTC","permalink":"https://info.linuxserver.io/issues/2022-11-25-heimdall/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2022-11-25 20:00:00Z","affected":["Known Issues","heimdall"],"filename":"2022-11-25-heimdall.md"},{"is":"issue","title":"Known Issue: lscr.io Unreachable","createdAt":"2022-05-22 16:00:00 +0000 UTC","lastMod":"2022-05-22 15:30:33 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2022-05-22-lscr/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2022-05-22 18:00:00Z","affected":["Known Issues","lscr.io"],"filename":"2022-05-22-lscr.md"},{"is":"issue","title":"Known Issue: nzbhydra2 Stable v4.3.1-ls52 and later","createdAt":"2022-05-05 12:00:00 +0000 UTC","lastMod":"2022-05-22 15:28:20 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2022-05-05-nzbhydra2/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2022-05-22 16:00:00Z","affected":["Known Issues","nzbhydra2"],"filename":"2022-05-05-nzbhydra2.md"},{"is":"issue","title":"Known Issue: Deluge 2.0.4","createdAt":"2021-12-14 14:00:00 +0000 UTC","lastMod":"2021-12-15 21:11:10 +0000 UTC","permalink":"https://info.linuxserver.io/issues/2021-12-14-deluge/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-12-15","affected":["Known Issues","deluge"],"filename":"2021-12-14-deluge.md"},{"is":"issue","title":"Known Issue: Paperless-ng","createdAt":"2021-07-26 00:00:00 +0000 UTC","lastMod":"2021-08-29 12:06:57 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2021-07-26-paperless-ng/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-07-30","affected":["Known Issues","paperless-ng"],"filename":"2021-07-26-paperless-ng.md"},{"is":"issue","title":"Known Issue: Swag 1.15.0","createdAt":"2021-05-29 00:00:00 +0000 UTC","lastMod":"2021-06-02 20:51:38 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-29-swag/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-06-02","affected":["Known Issues","swag"],"filename":"2021-05-29-swag.md"},{"is":"issue","title":"Known Issue: Unifi Controller v6.2.23","createdAt":"2021-05-08 00:00:00 +0000 UTC","lastMod":"2021-05-26 18:55:34 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-13-unifi-controller/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-05-14","affected":["Known Issues","unifi-controller"],"filename":"2021-05-13-unifi-controller.md"}]}
|
||||
{"is":"system","title":"Known Issues","permalink":"https://info.linuxserver.io/affected/known-issues/","status":"notice","pages":[{"is":"issue","title":"Known Issue: MariaDB Check and Repair","createdAt":"2023-05-29 12:00:00 +0000 UTC","lastMod":"2023-05-29 10:29:55 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-05-29-mariadb/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","mariadb"],"filename":"2023-05-29-mariadb.md"},{"is":"issue","title":"Known Issue: Portainer & Synology Docker UI","createdAt":"2023-05-22 12:00:00 +0000 UTC","lastMod":"2023-05-22 14:22:54 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2023-05-22-portainer/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","portainer","synology"],"filename":"2023-05-22-portainer.md"},{"is":"issue","title":"Known Issue: Heimdall 2.5.0 & 2.5.1 Releases","createdAt":"2022-11-25 16:00:00 +0000 UTC","lastMod":"2022-11-25 17:38:10 +0000 UTC","permalink":"https://info.linuxserver.io/issues/2022-11-25-heimdall/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2022-11-25 20:00:00Z","affected":["Known Issues","heimdall"],"filename":"2022-11-25-heimdall.md"},{"is":"issue","title":"Known Issue: lscr.io Unreachable","createdAt":"2022-05-22 16:00:00 +0000 UTC","lastMod":"2022-05-22 15:30:33 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2022-05-22-lscr/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2022-05-22 18:00:00Z","affected":["Known Issues","lscr.io"],"filename":"2022-05-22-lscr.md"},{"is":"issue","title":"Known Issue: nzbhydra2 Stable v4.3.1-ls52 and later","createdAt":"2022-05-05 12:00:00 +0000 UTC","lastMod":"2022-05-22 15:28:20 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2022-05-05-nzbhydra2/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2022-05-22 16:00:00Z","affected":["Known Issues","nzbhydra2"],"filename":"2022-05-05-nzbhydra2.md"},{"is":"issue","title":"Known Issue: Deluge 2.0.4","createdAt":"2021-12-14 14:00:00 +0000 UTC","lastMod":"2021-12-15 21:11:10 +0000 UTC","permalink":"https://info.linuxserver.io/issues/2021-12-14-deluge/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-12-15","affected":["Known Issues","deluge"],"filename":"2021-12-14-deluge.md"},{"is":"issue","title":"Known Issue: Paperless-ng","createdAt":"2021-07-26 00:00:00 +0000 UTC","lastMod":"2021-08-29 12:06:57 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2021-07-26-paperless-ng/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-07-30","affected":["Known Issues","paperless-ng"],"filename":"2021-07-26-paperless-ng.md"},{"is":"issue","title":"Known Issue: Swag 1.15.0","createdAt":"2021-05-29 00:00:00 +0000 UTC","lastMod":"2021-06-02 20:51:38 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-29-swag/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-06-02","affected":["Known Issues","swag"],"filename":"2021-05-29-swag.md"},{"is":"issue","title":"Known Issue: Unifi Controller v6.2.23","createdAt":"2021-05-08 00:00:00 +0000 UTC","lastMod":"2021-05-26 18:55:34 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-13-unifi-controller/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-05-14","affected":["Known Issues","unifi-controller"],"filename":"2021-05-13-unifi-controller.md"}]}
|
||||
@ -1,4 +1,29 @@
|
||||
<?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>Known Issues on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/known-issues/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-05-22T12:00:00+00:00</lastBuildDate><updated>2023-05-22T12:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/known-issues/index.xml" rel="self" type="application/rss+xml"/><item><title>Known Issue: Portainer & Synology Docker UI</title><link>https://info.linuxserver.io/issues/2023-05-22-portainer/</link><pubDate>Mon, 22 May 2023 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-22-portainer/</guid><category/><description>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.
|
||||
<?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>Known Issues on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/known-issues/</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/known-issues/index.xml" rel="self" type="application/rss+xml"/><item><title>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/><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><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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-check -u root -p&lt;PASSWORD&gt; -c -A <span style="color:#75715e"># check all databases for errors</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -r -A <span style="color:#75715e"># repair all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -a -A <span style="color:#75715e"># analyze all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -o -A <span style="color:#75715e"># optimize all databases</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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-upgrade -u root -p&lt;PASSWORD&gt;
|
||||
</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>Known Issue: Portainer & Synology Docker UI</title><link>https://info.linuxserver.io/issues/2023-05-22-portainer/</link><pubDate>Mon, 22 May 2023 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-22-portainer/</guid><category/><description>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.
|
||||
This non-standard behaviour causes containers to fail to start correctly in some cases, and may result in unexpected or unwanted configuration in others. For example, in our SABnzbd image the PATH environment variable is overwritten, leaving the application unable to locate the necessary Python modules to enable it to start.</description><content type="html"><p>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.</p>
|
||||
<p>This non-standard behaviour causes containers to fail to start correctly in some cases, and may result in unexpected or unwanted configuration in others. For example, in our <a href="https://github.com/linuxserver/docker-sabnzbd/issues/188">SABnzbd image</a> the <code>PATH</code> environment variable is overwritten, leaving the application unable to locate the necessary Python modules to enable it to start. This is likely to become more common in the future, and there is not a practical or scalable solution that we can apply from our end to avoid this issue.</p>
|
||||
<p><strong>Our position remains that we provide support only for containers created and updated using Docker Compose, the Docker CLI, or using our Unraid templates, and not any 3rd party tools.</strong></p></content></item><item><title>[Resolved] Known Issue: Heimdall 2.5.0 & 2.5.1 Releases</title><link>https://info.linuxserver.io/issues/2022-11-25-heimdall/</link><pubDate>Fri, 25 Nov 2022 16:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2022-11-25-heimdall/</guid><category>2022-11-25 20:00:00Z</category><description>Update Version 2.5.2 has been released to fix the install issues. Users running 2.5.1 or below should look to upgrade to the version-v2.5.2 or latest tags.
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"mariadb","permalink":"https://info.linuxserver.io/affected/mariadb/","status":"ok","pages":[{"is":"issue","title":"mariadb change to Alpine","createdAt":"2021-08-25 00:00:00 +0000 UTC","lastMod":"2021-08-25 15:28:09 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-08-25-mariadb-alpine/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Deprecations","mariadb"],"filename":"2021-08-25-mariadb-alpine.md"},{"is":"issue","title":"mariadb change to Alpine","createdAt":"2021-03-10 00:00:00 +0000 UTC","lastMod":"2021-03-10 16:14:48 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2021-03-10-mariadb-alpine/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Deprecations","mariadb"],"filename":"2021-03-10-mariadb-alpine.md"},{"is":"issue","title":"New Container: Mariadb","createdAt":"2015-08-12 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2015-08-12-mariadb/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","mariadb"],"filename":"2015-08-12-mariadb.md"}]}
|
||||
{"is":"system","title":"mariadb","permalink":"https://info.linuxserver.io/affected/mariadb/","status":"notice","pages":[{"is":"issue","title":"Known Issue: MariaDB Check and Repair","createdAt":"2023-05-29 12:00:00 +0000 UTC","lastMod":"2023-05-29 10:29:55 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-05-29-mariadb/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","mariadb"],"filename":"2023-05-29-mariadb.md"},{"is":"issue","title":"mariadb change to Alpine","createdAt":"2021-08-25 00:00:00 +0000 UTC","lastMod":"2021-08-25 15:28:09 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-08-25-mariadb-alpine/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Deprecations","mariadb"],"filename":"2021-08-25-mariadb-alpine.md"},{"is":"issue","title":"mariadb change to Alpine","createdAt":"2021-03-10 00:00:00 +0000 UTC","lastMod":"2021-03-10 16:14:48 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2021-03-10-mariadb-alpine/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Deprecations","mariadb"],"filename":"2021-03-10-mariadb-alpine.md"},{"is":"issue","title":"New Container: Mariadb","createdAt":"2015-08-12 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2015-08-12-mariadb/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","mariadb"],"filename":"2015-08-12-mariadb.md"}]}
|
||||
@ -1,4 +1,29 @@
|
||||
<?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>2021-08-25T00:00:00+00:00</lastBuildDate><updated>2021-08-25T00:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/mariadb/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>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/><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><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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-check -u root -p&lt;PASSWORD&gt; -c -A <span style="color:#75715e"># check all databases for errors</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -r -A <span style="color:#75715e"># repair all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -a -A <span style="color:#75715e"># analyze all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -o -A <span style="color:#75715e"># optimize all databases</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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-upgrade -u root -p&lt;PASSWORD&gt;
|
||||
</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!
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"index","cStateVersion":"5.5.1","apiVersion":"2.0","title":"Info :: LinuxServer.io","languageCodeHTML":"en","languageCode":"en","baseURL":"https://info.linuxserver.io","description":"<no value>","summaryStatus":"notice","categories":[{"name":"Images","description":"Information regarding our images","hideTitle":false,"closedByDefault":false},{"name":"Security","hideTitle":false,"closedByDefault":false}],"systems":[{"name":"Deprecations","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"New Containers","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"Vulnerabilities","category":"Security","status":"ok","unresolvedIssues":[]},{"name":"Known Issues","category":"Images","status":"notice","unresolvedIssues":[{"is":"issue","title":"Known Issue: Portainer & Synology Docker UI","createdAt":"2023-05-22 12:00:00 +0000 UTC","lastMod":"2023-05-22 14:22:54 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2023-05-22-portainer/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","portainer","synology"],"filename":"2023-05-22-portainer.md"}]},{"name":"Notifications","category":"Images","status":"ok","unresolvedIssues":[]}],"buildDate":"2023-05-23","buildTime":"13:40","buildTimezone":"UTC","colorBrand":"#0a0c0f","colorOk":"#008000","colorDisrupted":"#cc4400","colorDown":"#e60000","colorNotice":"#24478f","alwaysKeepBrandColor":"true","logo":"https://info.linuxserver.io/logo.png","googleAnalytics":"UA-00000000-1"}
|
||||
{"is":"index","cStateVersion":"5.5.1","apiVersion":"2.0","title":"Info :: LinuxServer.io","languageCodeHTML":"en","languageCode":"en","baseURL":"https://info.linuxserver.io","description":"<no value>","summaryStatus":"notice","categories":[{"name":"Images","description":"Information regarding our images","hideTitle":false,"closedByDefault":false},{"name":"Security","hideTitle":false,"closedByDefault":false}],"systems":[{"name":"Deprecations","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"New Containers","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"Vulnerabilities","category":"Security","status":"ok","unresolvedIssues":[]},{"name":"Known Issues","category":"Images","status":"notice","unresolvedIssues":[{"is":"issue","title":"Known Issue: MariaDB Check and Repair","createdAt":"2023-05-29 12:00:00 +0000 UTC","lastMod":"2023-05-29 10:29:55 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-05-29-mariadb/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","mariadb"],"filename":"2023-05-29-mariadb.md"},{"is":"issue","title":"Known Issue: Portainer & Synology Docker UI","createdAt":"2023-05-22 12:00:00 +0000 UTC","lastMod":"2023-05-22 14:22:54 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2023-05-22-portainer/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","portainer","synology"],"filename":"2023-05-22-portainer.md"}]},{"name":"Notifications","category":"Images","status":"ok","unresolvedIssues":[]}],"buildDate":"2023-05-29","buildTime":"15:47","buildTimezone":"UTC","colorBrand":"#0a0c0f","colorOk":"#008000","colorDisrupted":"#cc4400","colorDown":"#e60000","colorNotice":"#24478f","alwaysKeepBrandColor":"true","logo":"https://info.linuxserver.io/logo.png","googleAnalytics":"UA-00000000-1"}
|
||||
25
index.xml
25
index.xml
@ -1,4 +1,27 @@
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Info :: LinuxServer.io</title><link>https://info.linuxserver.io/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>Mon, 22 May 2023 12:00:00 +0000</lastBuildDate><atom:link href="https://info.linuxserver.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Known Issue: Portainer & Synology Docker UI</title><link>https://info.linuxserver.io/issues/2023-05-22-portainer/</link><pubDate>Mon, 22 May 2023 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-22-portainer/</guid><category/><description><p>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.</p>
|
||||
<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Info :: LinuxServer.io</title><link>https://info.linuxserver.io/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>Mon, 29 May 2023 12:00:00 +0000</lastBuildDate><atom:link href="https://info.linuxserver.io/index.xml" rel="self" type="application/rss+xml"/><item><title>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/><description><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><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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-check -u root -p&lt;PASSWORD&gt; -c -A <span style="color:#75715e"># check all databases for errors</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -r -A <span style="color:#75715e"># repair all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -a -A <span style="color:#75715e"># analyze all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -o -A <span style="color:#75715e"># optimize all databases</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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-upgrade -u root -p&lt;PASSWORD&gt;
|
||||
</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></description></item><item><title>Known Issue: Portainer & Synology Docker UI</title><link>https://info.linuxserver.io/issues/2023-05-22-portainer/</link><pubDate>Mon, 22 May 2023 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-22-portainer/</guid><category/><description><p>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.</p>
|
||||
<p>This non-standard behaviour causes containers to fail to start correctly in some cases, and may result in unexpected or unwanted configuration in others. For example, in our <a href="https://github.com/linuxserver/docker-sabnzbd/issues/188">SABnzbd image</a> the <code>PATH</code> environment variable is overwritten, leaving the application unable to locate the necessary Python modules to enable it to start. This is likely to become more common in the future, and there is not a practical or scalable solution that we can apply from our end to avoid this issue.</p>
|
||||
<p><strong>Our position remains that we provide support only for containers created and updated using Docker Compose, the Docker CLI, or using our Unraid templates, and not any 3rd party tools.</strong></p></description></item><item><title>New Container: hiSHtory-server</title><link>https://info.linuxserver.io/issues/2023-05-19-hishtory/</link><pubDate>Fri, 19 May 2023 20:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-19-hishtory/</guid><category/><description><p>We have released a new container for <a href="https://github.com/linuxserver/docker-hishtory-server">hiSHtory-server</a>!</p>
|
||||
<p><a href="https://github.com/ddworken/hishtory">hiSHtory</a> is a better shell history. It stores your shell history in context (what directory you ran the command in, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers.</p></description></item><item><title>COPS Deprecation Notice</title><link>https://info.linuxserver.io/issues/2023-05-15-cops/</link><pubDate>Mon, 15 May 2023 15:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-15-cops/</guid><category/><description><p>Due to numerous compatibility issues caused by the upstream project being abandoned and no actively maintained fork existing, we are deprecating our <a href="https://github.com/linuxserver/docker-cops/">COPS container</a>.</p></description></item><item><title>Reminder: 32-bit Arm Deprecation Notice</title><link>https://info.linuxserver.io/issues/2023-05-06-armhf/</link><pubDate>Sat, 06 May 2023 18:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-06-armhf/</guid><category/><description><p>Due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we will be deprecating <em>all</em> 32-bit Arm (armhf) versions of our images effective 2023-07-01.</p>
|
||||
|
||||
15
issues/2023-05-29-mariadb/index.html
Normal file
15
issues/2023-05-29-mariadb/index.html
Normal file
File diff suppressed because one or more lines are too long
1
issues/2023-05-29-mariadb/index.json
Normal file
1
issues/2023-05-29-mariadb/index.json
Normal file
@ -0,0 +1 @@
|
||||
{"is":"issue","title":"Known Issue: MariaDB Check and Repair","createdAt":"2023-05-29 12:00:00 +0000 UTC","lastMod":"2023-05-29 10:29:55 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-05-29-mariadb/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","mariadb"],"filename":"2023-05-29-mariadb.md"}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1,4 +1,29 @@
|
||||
<?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>Issues on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/issues/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-05-22T12:00:00+00:00</lastBuildDate><updated>2023-05-22T12:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/issues/index.xml" rel="self" type="application/rss+xml"/><item><title>Known Issue: Portainer & Synology Docker UI</title><link>https://info.linuxserver.io/issues/2023-05-22-portainer/</link><pubDate>Mon, 22 May 2023 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-22-portainer/</guid><category/><description>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.
|
||||
<?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>Issues on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/issues/</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/issues/index.xml" rel="self" type="application/rss+xml"/><item><title>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/><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><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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-check -u root -p&lt;PASSWORD&gt; -c -A <span style="color:#75715e"># check all databases for errors</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -r -A <span style="color:#75715e"># repair all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -a -A <span style="color:#75715e"># analyze all databases</span>
|
||||
mariadb-check -u root -p&lt;PASSWORD&gt; -o -A <span style="color:#75715e"># optimize all databases</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 style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code class="language-shell" data-lang="shell">mariadb-upgrade -u root -p&lt;PASSWORD&gt;
|
||||
</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>Known Issue: Portainer & Synology Docker UI</title><link>https://info.linuxserver.io/issues/2023-05-22-portainer/</link><pubDate>Mon, 22 May 2023 12:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-22-portainer/</guid><category/><description>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.
|
||||
This non-standard behaviour causes containers to fail to start correctly in some cases, and may result in unexpected or unwanted configuration in others. For example, in our SABnzbd image the PATH environment variable is overwritten, leaving the application unable to locate the necessary Python modules to enable it to start.</description><content type="html"><p>There is a known issue with Portainer and the Synology Docker UI when updating (or otherwise recreating) containers, which causes them to overwrite settings in the new image with values from the old container. Creating a new container from scratch does not exhibit this behaviour.</p>
|
||||
<p>This non-standard behaviour causes containers to fail to start correctly in some cases, and may result in unexpected or unwanted configuration in others. For example, in our <a href="https://github.com/linuxserver/docker-sabnzbd/issues/188">SABnzbd image</a> the <code>PATH</code> environment variable is overwritten, leaving the application unable to locate the necessary Python modules to enable it to start. This is likely to become more common in the future, and there is not a practical or scalable solution that we can apply from our end to avoid this issue.</p>
|
||||
<p><strong>Our position remains that we provide support only for containers created and updated using Docker Compose, the Docker CLI, or using our Unraid templates, and not any 3rd party tools.</strong></p></content></item><item><title>New Container: hiSHtory-server</title><link>https://info.linuxserver.io/issues/2023-05-19-hishtory/</link><pubDate>Fri, 19 May 2023 20:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-05-19-hishtory/</guid><category/><description>We have released a new container for hiSHtory-server!
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
14
issues/page/24/index.html
Normal file
14
issues/page/24/index.html
Normal file
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Loading…
x
Reference in New Issue
Block a user