Your message dated Mon, 21 Sep 2020 00:28:54 +0300
with message-id 
<cahj_tlazfupiohh2zedfqjn3f1y1kgtkzoklvbb-yt4g9uv...@mail.gmail.com>
and subject line Re: [debian-mysql] Bug#878421: mariadb-server-10.0: packages 
depending on mariadb-server starts before mariadb-server fully loaded
has caused the Debian Bug report #878421,
regarding mariadb-server-10.0: packages depending on mariadb-server starts 
before mariadb-server fully loaded
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 [email protected]
immediately.)


-- 
878421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878421
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server-10.0
Version: 10.0.32-0+deb8u1
Severity: normal

Dear Maintainer,

Not sure whether it's the proper place to report this but anyway, let's go.

I've been using linux since v 0.93 and I'm used to the init.d script system.

The new service system since debian 7 or 8, I'm a total newbie and don't 
understand it fully.
All I know is that it starts deamons in parallel instead of one after another.

The problem I have is that nginx, apache, mythserver, exim among others rely on 
mysql
and require that mysql (mariadb-server here) is fully loaded and running before 
those
packages are even started.

That is not the case.  Each one reports errors mysql related until 
mariadb-server is finally
completely ready.

How could I remedy to that once and for all?

Still using debian 8 BTW.  Past experiences with Debian upgrades always break 
exim, samba,
dovecot among others which requires a lot of time to fix.

-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (990, 'oldstable-updates'), (990, 'oldstable'), (500, 
'oldoldstable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages mariadb-server-10.0 depends on:
ii  adduser                   3.113+nmu3
ii  debconf [debconf-2.0]     1.5.56+deb8u1
ii  libaio1                   0.3.110-1
ii  libc6                     2.19-18+deb8u10
ii  libdbi-perl               1.631-3+b1
ii  libpam0g                  1.1.8-3.1+deb8u2+b1
ii  libstdc++6                4.9.2-10
ii  lsb-base                  4.1+Debian13+nmu1
ii  mariadb-client-10.0       10.0.32-0+deb8u1
ii  mariadb-common            10.0.32-0+deb8u1
ii  mariadb-server-core-10.0  10.0.32-0+deb8u1
ii  passwd                    1:4.2-3+deb8u4
ii  perl                      5.20.2-3+deb8u9
ii  psmisc                    22.21-2
ii  zlib1g                    1:1.2.8.dfsg-2+b1

Versions of packages mariadb-server-10.0 recommends:
ii  libhtml-template-perl  2.95-1

Versions of packages mariadb-server-10.0 suggests:
ii  bsd-mailx [mailx]  8.1.2-0.20141216cvs-2
ii  mariadb-test       10.0.32-0+deb8u1
pn  tinyca             <none>

-- debconf information:
  mysql-server/password_mismatch:
  mariadb-server-10.0/really_downgrade: false
* mariadb-server/oneway_migration: true
  mysql-server/no_upgrade_when_using_ndb:
  mysql-server-10.0/nis_warning:
  mysql-server-10.0/postrm_remove_databases: false
* mysql-server/error_setting_password:

--- End Message ---
--- Begin Message ---
Tags: wontfix

The systemd service file
(https://salsa.debian.org/mariadb-team/mariadb-10.5/-/blob/master/support-files/mariadb.service.in)
is defined to run as soon as possible when the network is available.

If there is something that depends on MariaDB to be running (maybe
mythserver?) if should define so in it's systemd files.

Closing bug as 'wontfix' for MariaDB Server.

--- End Message ---

Reply via email to