Bug#864943: mariadb-server-10.1: Starting mariadb service does not terminate

[Otto Kekäläinen]

Hi!

Latest version of MariaDB in Debian unstable/testing/Bookworm is
10.11.2. You might want to consider testing it.

If you want to contribute in the open source way to fix this or any
other issue, see
https://salsa.debian.org/mariadb-team/mariadb-server/-/wikis/Contributing-to-MariaDB-packaging-in-Debian
on how to submit a Merge Request!


If you have time to help, please consider these (in order of importance):

1. Review current open MRs at
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests

2. Review items highlighted by Debian QA systems (Lintian, builds etc)
and submit a fix to improve the quality:
https://tracker.debian.org/pkg/mariadb

3. Review what testing we have at
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines and
think about potential gaps - CI is very important as it is the only
way we can prevent regressions in a scalable way

4. Review/follow-up on existing bugs that currently need more
information: 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no=mariadb=mariadb-10.6=mariadb-10.5=mariadb-10.3=mariadb-10.1

MariaDB and C++ skills are useful, but not required. For example
reviewing the NEWS for 10.11 requires no coding skills:
https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/37


My request for help from debian-devel in
https://lists.debian.org/debian-devel/2023/02/msg00272.html did not
get many responses, so the future of this package depends on how
active the users and people who previously reported bugs are in
participating in the maintenance of the package.

- Otto

Bug#864943: mariadb-server-10.1: Starting mariadb service does not terminate

[Ondřej Surý]

Control: tags -1 +moreinfo

Hi Thomas,

I am afraid that we will need to have a reproducer outside of the Docker
or find what's causing the Docker instance to be stuck[*]. There are too
much unknown variables when using Docker, and it's quite hard to debug.

* - or at least provide a full log of what is happening inside your
Docker container.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Sat, Jun 17, 2017, at 20:29, Thomas Mayer wrote:
> Package: mariadb-server-10.1
> Version: 10.1.23-9+deb9u1
> Severity: normal
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
> 1. Creating a Docker container with MariaDB installed
> 2. Start MariaDB via Docker interface
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Reproduce this issue with this Docker container (stretch):
> 
> https://github.com/thomaszbz/native-dockerfiles-typo3/tree/3b28a02bd84aa418c62e4764844f8b862c14ee8a
> https://github.com/thomaszbz/native-dockerfiles-typo3/blob/3b28a02bd84aa418c62e4764844f8b862c14ee8a/typo3-debian-stretch/Dockerfile
> 
> Start MariaDB with:
> 
> docker exec -it typo3 service mysql start
> or
> docker exec -t typo3 service mysql start
> or
> docker exec -it jft /bin/bash -c "service mysql start"
> 
> Output:
> 
> [ ok ] Starting MariaDB database server: mysqld.
> <<< now the terminal hangs. Even CTRL+C does not work.
> 
> 
>* What was the outcome of this action?
> 
> The termial does not terminate/return. It's not possible to type in the
> next command unless someone (other user session) executes a "service
> mysql stop" or stops the Docker container.
> 
>* What outcome did you expect instead?
> 
> Starting MariaDB should just terminate. In that respect: I can start
> apache2 without any issues. It returns/terminates and in my terminal I
> can just type in the next command.
> 
>* Regression consideration
> 
> Please note that this issue did not happen with the jessie equivalent
> which relied on mysql:
> 
> https://github.com/thomaszbz/native-dockerfiles-typo3/blob/3b28a02bd84aa418c62e4764844f8b862c14ee8a/typo3-debian-jessie/Dockerfile
> 
> That said, this issue would be a regression if there was no migration
> from mysql to mariadb in between. Formally-spoken, it's not necessarily
> a regression because of that migration. I'm not sure if Debian's
> commitment here is to have the mysql/mariadb migration as smooth as
> possible. Nevertheless, IMO, it's still a bug.
> 
> I also think that the bug is in mariadb and not in Docker because
> starting apache2 just works fine.
> 
> -- System Information:
> Debian Release: 9.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.8.0-54-generic (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
> LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> (ignored: LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: unable to detect
> 
> Versions of packages mariadb-server-10.1 depends on:
> ii  adduser   3.115
> ii  debconf [debconf-2.0] 1.5.61
> ii  galera-3  25.3.19-2
> ii  gawk  1:4.1.4+dfsg-1
> ii  init-system-helpers   1.48
> ii  iproute2  4.9.0-1
> ii  libaio1   0.3.110-3
> ii  libc6 2.24-11
> ii  libdbi-perl   1.636-1+b1
> ii  libpam0g  1.1.8-3.6
> ii  libstdc++66.3.0-18
> ii  libsystemd0   232-25
> ii  lsb-base  9.20161125
> ii  lsof  4.89+dfsg-0.1
> ii  mariadb-client-10.1   10.1.23-9+deb9u1
> ii  mariadb-common10.1.23-9+deb9u1
> ii  mariadb-server-core-10.1  10.1.23-9+deb9u1
> ii  passwd1:4.4-4.1
> ii  perl  5.24.1-3
> ii  psmisc22.21-2.1+b2
> ii  rsync 3.1.2-1
> ii  socat 1.7.3.1-2+b1
> ii  zlib1g1:1.2.8.dfsg-5
> 
> Versions of packages mariadb-server-10.1 recommends:
> ii  libhtml-template-perl  2.95-2
> 
> Versions of packages mariadb-server-10.1 suggests:
> pn  mailx   
> pn  mariadb-test
> pn  netcat-openbsd  
> pn  tinyca  
> 
> -- debconf information:
>   mariadb-server-10.1/old_data_directory_saved:
>   mariadb-server-10.1/nis_warning:
>   mariadb-server-10.1/postrm_remove_databases: false
> 
> -- 
> Thomas Mayer
> 2bis10 IT-Services UG (haftungsbeschränkt)
> Durlacher Allee 61
> D-76131 Karlsruhe
> Telefon:  +49-721-7238
> Telefax:  +49-721-72380001
> E-Mail:   thomas.ma...@2bis10.de
> Internet: https://www.2bis10.de
> 

Bug#864943: mariadb-server-10.1: Starting mariadb service does not terminate

[Thomas Mayer]

Package: mariadb-server-10.1
Version: 10.1.23-9+deb9u1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

1. Creating a Docker container with MariaDB installed
2. Start MariaDB via Docker interface

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Reproduce this issue with this Docker container (stretch):

https://github.com/thomaszbz/native-dockerfiles-typo3/tree/3b28a02bd84aa418c62e4764844f8b862c14ee8a
https://github.com/thomaszbz/native-dockerfiles-typo3/blob/3b28a02bd84aa418c62e4764844f8b862c14ee8a/typo3-debian-stretch/Dockerfile

Start MariaDB with:

docker exec -it typo3 service mysql start
or
docker exec -t typo3 service mysql start
or
docker exec -it jft /bin/bash -c "service mysql start"

Output:

[ ok ] Starting MariaDB database server: mysqld.
<<< now the terminal hangs. Even CTRL+C does not work.


   * What was the outcome of this action?

The termial does not terminate/return. It's not possible to type in the
next command unless someone (other user session) executes a "service
mysql stop" or stops the Docker container.

   * What outcome did you expect instead?

Starting MariaDB should just terminate. In that respect: I can start
apache2 without any issues. It returns/terminates and in my terminal I
can just type in the next command.

   * Regression consideration

Please note that this issue did not happen with the jessie equivalent
which relied on mysql:

https://github.com/thomaszbz/native-dockerfiles-typo3/blob/3b28a02bd84aa418c62e4764844f8b862c14ee8a/typo3-debian-jessie/Dockerfile

That said, this issue would be a regression if there was no migration
from mysql to mariadb in between. Formally-spoken, it's not necessarily
a regression because of that migration. I'm not sure if Debian's
commitment here is to have the mysql/mariadb migration as smooth as
possible. Nevertheless, IMO, it's still a bug.

I also think that the bug is in mariadb and not in Docker because
starting apache2 just works fine.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-54-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored:
LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages mariadb-server-10.1 depends on:
ii  adduser   3.115
ii  debconf [debconf-2.0] 1.5.61
ii  galera-3  25.3.19-2
ii  gawk  1:4.1.4+dfsg-1
ii  init-system-helpers   1.48
ii  iproute2  4.9.0-1
ii  libaio1   0.3.110-3
ii  libc6 2.24-11
ii  libdbi-perl   1.636-1+b1
ii  libpam0g  1.1.8-3.6
ii  libstdc++66.3.0-18
ii  libsystemd0   232-25
ii  lsb-base  9.20161125
ii  lsof  4.89+dfsg-0.1
ii  mariadb-client-10.1   10.1.23-9+deb9u1
ii  mariadb-common10.1.23-9+deb9u1
ii  mariadb-server-core-10.1  10.1.23-9+deb9u1
ii  passwd1:4.4-4.1
ii  perl  5.24.1-3
ii  psmisc22.21-2.1+b2
ii  rsync 3.1.2-1
ii  socat 1.7.3.1-2+b1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mariadb-server-10.1 recommends:
ii  libhtml-template-perl  2.95-2

Versions of packages mariadb-server-10.1 suggests:
pn  mailx   
pn  mariadb-test
pn  netcat-openbsd  
pn  tinyca  

-- debconf information:
  mariadb-server-10.1/old_data_directory_saved:
  mariadb-server-10.1/nis_warning:
  mariadb-server-10.1/postrm_remove_databases: false

-- 
Thomas Mayer
2bis10 IT-Services UG (haftungsbeschränkt)
Durlacher Allee 61
D-76131 Karlsruhe
Telefon:  +49-721-7238
Telefax:  +49-721-72380001
E-Mail:   thomas.ma...@2bis10.de
Internet: https://www.2bis10.de
=
Handelsregister: Amtsgericht Mannheim, HRB 705613
Geschäftsführer: Thomas Mayer
USt-IDNr.:   DE269622651
Bankverbindung:  Sparkasse Karlsruhe
BIC: KARSDE66XXX
IBAN:DE41660501010108087016
=