-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2022-03-30 at 08:00 +0200, Johnny A. Solbu wrote:
> Are you telling me that unless I shell out some money,
> _Debian_ is not going to even provide any hints on what needs to be done to
> fix what is supposed to be a simple «apt upgrade»?
Hi
On Wednesday 30 March 2022 07:38, Otto Kekäläinen wrote:
> Please keep in mind that this is an open source project. You are
> welcome to debug the issue yourself and to contribute towards a fix
> for it. If you need somebody else to fix it for you, you might
> consider using a consultant or a
On Tue, Mar 29, 2022 at 9:33 PM Johnny A. Solbu wrote:
>
> On Sunday 20 February 2022 02:23, Otto Kekäläinen wrote:
> > Is the issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
> > still affecting people?
>
> We just hit it again on our server aftre4r upgrading just now, and I am not
On Sunday 20 February 2022 02:23, Otto Kekäläinen wrote:
> Is the issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
> still affecting people?
We just hit it again on our server aftre4r upgrading just now, and I am not
sure why.
We had to resort to enableing «innodb_force_recovery =
Control: reassign -1 mariadb-server-10.3
Control: tags moreinfo
Hello!
Is the issue https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028
still affecting people? Did anybody figure out the root cause or what
upstream issue it was, or what version it was fixed in?
On 2021-10-25 19:37, Otto Kekäläinen wrote:
We have two users who have experienced a potentially corrupted
database (out of hundreds of thousands or even potentially millions of
users, depending how one wants to extrapolate the popcon data). A bug
report has been filed and it is kept open in
Hello Ondrej!
I sent the below message on Oct 10th but I am not sure if you read it.
The gist is:
> I recommend that you file a bug about this upstream, and try to attach
> relevant info from the error log, maybe a strace output etc. Upstream
> devs will guide you on what to debug next.
The bug
Control: severity -1 normal
On Thu, Oct 21, 2021 at 9:24 PM Marc Gallet wrote:
> I've been brought to this bug by apt-listbugs while doing upgrades
> on my buster install, warning me of a grave bug.
We have two users who have experienced a potentially corrupted
database (out of hundreds of
Hello.
I agree. I'm still waiting for fix and don't want to dump/drop/import
data.
JK
On Sun, 24 Oct 2021 00:51:08 +0800
Marc Gallet wrote:
> Am I to understand that the expected path forward with what is
> supposed to be a minor update offered on oldstable is that everyone
> shall dump their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2021-10-24 at 00:51 +0800, Marc Gallet wrote:
> Am I to understand that the expected path forward with what is supposed to be
> a minor update offered on oldstable is that everyone shall dump their
> databases,
> delete the data folder,
> With 10.3.29 running, I've dumped all databases (mysqldump --all-databases -p
> >mysql.dump),
> then dropped all databases, stopped mariadb and deleted /var/lib/mysql/ib*.
> Then restarted mariadb, restored databases (source mysql.dump) and finally
> upgraded to 10.3.31.
>
> So my problem is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2021-10-22 at 02:13 +0800, Marc Gallet wrote:
>
> Am I correct to assume this issue is still relevant for buster and that
> for now, I should simply defer the upgrade (marking the packages to be
> held back) and simply wait for this bug to
Package: mariadb-server
Followup-For: Bug #996028
Hi,
I've been brought to this bug by apt-listbugs while doing upgrades
on my buster install, warning me of a grave bug.
I have not attempted the upgrade yet, since, after reading this bug, I
see a risk of data corruption and I would like to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2021-10-12 at 21:58 +0200, Ondrej Zary wrote:
> > One thing you could also try is to start the server with 10.3.29 and
> > ensure that you have a clean shutdown (SET GLOBAL
> > innodb_fast_shutdown=0; SHUTDOWN) and only after that start with
On Sunday 10 October 2021 23:58:12 Otto Kekäläinen wrote:
> > The problem is in the ibdata1 file (about 450MB). Deleted other database
> > directories and it still crashes, deleted ibdata1 and it runs.
> >
> > How to bisect mariadb from git? Tried:
> > $ git bisect good mariadb-10.3.29
> > $ git
> The problem is in the ibdata1 file (about 450MB). Deleted other database
> directories and it still crashes, deleted ibdata1 and it runs.
>
> How to bisect mariadb from git? Tried:
> $ git bisect good mariadb-10.3.29
> $ git bisect bad mariadb-10.3.31
> the build process showed version 10.2 so
On Sunday 10 October 2021 16:55:45 Otto Kekäläinen wrote:
> Hello!
>
> Thanks for reporting. Could you please check if this has been reported
> upstream at jira.mariadb.org?
>
> There isn't much we can do about InnoDB internals in Debian packaging.
>
The problem is in the ibdata1 file (about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: subscribe -1
On Sun, 10 Oct 2021 16:13:29 +0200 Ondrej Zary wrote:
> Package: mariadb-server
> Version: 1:10.3.31-0+deb10u1
> Severity: grave
> Justification: causes non-serious data loss
>
> Dear Maintainer,
> upgrading mariadb-server
Haven't found this exact problem. This seems to be closest but the error
messages are different: https://jira.mariadb.org/browse/MDEV-25981
I'm going to copy the datadir to another machine and debug it further.
On Sunday 10 October 2021 16:55:45 Otto Kekäläinen wrote:
> Hello!
>
> Thanks for
Hello!
Thanks for reporting. Could you please check if this has been reported
upstream at jira.mariadb.org?
There isn't much we can do about InnoDB internals in Debian packaging.
Package: mariadb-server
Version: 1:10.3.31-0+deb10u1
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
upgrading mariadb-server from 1:10.3.29-0+deb10u1 to 1:10.3.31-0+deb10u1 failed
because mariadb failed to start. /var/log/mysql/error.log:
2021-10-10 15:12:49 0
21 matches
Mail list logo
