Your message dated Thu, 27 Apr 2023 20:59:46 +0200
with message-id <7d6f11c3-b3d0-46e8-c7e0-c6ac99109...@debian.org>
and subject line mariadb-10.1 has been removed from Debian
has caused the Debian Bug report #864943,
regarding mariadb-server-10.1: Starting mariadb service does not terminate
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
864943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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++6                6.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-common            10.1.23-9+deb9u1
ii  mariadb-server-core-10.1  10.1.23-9+deb9u1
ii  passwd                    1:4.4-4.1
ii  perl                      5.24.1-3
ii  psmisc                    22.21-2.1+b2
ii  rsync                     3.1.2-1
ii  socat                     1.7.3.1-2+b1
ii  zlib1g                    1: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           <none>
pn  mariadb-test    <none>
pn  netcat-openbsd  <none>
pn  tinyca          <none>

-- 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-72380000
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
=========================================================

--- End Message ---
--- Begin Message ---
Version: 1:10.1.37-3+rm

src:mariadb-10.1 was last released with Debian 9 (stretch)
in June 2017 and was removed from the Debian archive afterwards.
It has been superseded by newer versions.
See https://bugs.debian.org/920581 for details on the removal.
After regular security support for stretch ended in July 2020 and LTS
support ended in July 2022, I'm closing the remaining bug reports now.
In case the bug is still present in recent releases, please reopen and
reassign it.

Andreas

--- End Message ---

Reply via email to