Your message dated Mon, 19 Jun 2017 07:37:33 +0000
with message-id <>
and subject line Bug#865083: fixed in mariadb-10.1 10.1.24-5
has caused the Debian Bug report #865083,
regarding mariadb-server-10.1: mariadb@.service doesn't create /var/run/mysqld
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

Debian Bug Tracking System
Contact with problems
--- Begin Message ---
Package: mariadb-server-10.1
Version: 10.1.23-9+deb9u1
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

After upgrading from Jessie to Stretch I was unable to get my multi-instance 
mySQL setup working using the installed .service files.

I have a machine with 2 mySQl instances running, which in Jessie I managed with 
mysqld_multi in an init.d script. This is no longer supported with systemd/mariadb in 
Stretch (only the first instance was started) and so I changed to using 
the"mariadb@.service"  to invoke each instance. Once this was up and running I 
rebooted and both mySQL instanced failed to start, with:
[ERROR] Can't start server : Bind on unix socket: No such file or directory
[ERROR] Do you already have another mysqld server running on socket: 
/var/run/mysqld/mysqld.sock ? syslog. On inspection the /var/run/mysqld directory did not exist. I 
created it and both instances started manually, but after a reboot the same 
problem persisted. I fixed the problem by copying the line that creates 
/var/run/mysqld from the single-instance mariadb.service.

@@ -65,6 +65,8 @@
 # Execute pre and post scripts as root, otherwise it does it as User=

+ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld

The mariadb and mariadb@ services can't both be active at once, so I think this 
is a serious bug that breaks the ability to run multiple mySQL instances out of 
the box.

I had a few other issues after the upgrade too, I'm not sure if they count as 
bugs or not because I had a mysqld_multi stule my.cnf (ie with [mysqld1], 
[mysqld2] sections) so I don't know if they would occur with an existing 
single-instance install.

1. My main [mysqld] config settings were being overwritten by a 50_server.cnf 
file in mariadb.conf.d, even after I copied them to a my.cnf file in conf.d. I 
had to deleted the 50_server.cnf to recreate the server I had on Jessie. And 
should this file be in mariadb.conf.d anyway when it's got non-mariadb-specific 
settings like cache sizes etc (I may have caught it sooner if it were in 

2. I had to run mysql_upgrade on both databases after the install - should this 
be automatic?



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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           
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:
ii  mailutils [mailx]  1:3.1.1-1
pn  mariadb-test       <none>
pn  netcat-openbsd     <none>
pn  tinyca             <none>

-- Configuration Files:
/etc/init.d/mysql changed [not included]
/etc/mysql/mariadb.conf.d/50-server.cnf [Errno 2] No such file or directory: 

-- debconf information excluded

--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.24-5

We believe that the bug you reported is fixed in the latest version of
mariadb-10.1, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Ondřej Surý <> (supplier of updated mariadb-10.1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing

Hash: SHA512

Format: 1.8
Date: Mon, 19 Jun 2017 08:52:26 +0200
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.24-5
Distribution: unstable
Urgency: medium
Maintainer: Debian MySQL Maintainers <>
Changed-By: Ondřej Surý <>
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database, shared library
 mariadb-client - MariaDB database client (metapackage depending on the latest 
 mariadb-client-10.1 - MariaDB database client binaries
 mariadb-client-core-10.1 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
 mariadb-server-10.1 - MariaDB database server binaries
 mariadb-server-core-10.1 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 865083
 mariadb-10.1 (10.1.24-5) unstable; urgency=medium
   * Add @SYSTEMD_EXECSTARTPOST@ replacement token to mariadb@.service, so
     the /var/run/mysqld directory is created even for multi-server setup
     (Closes: #865083)
 678bdcadb486c61ddff18798a14c93182400e4ab 4448 mariadb-10.1_10.1.24-5.dsc
 f1d3d5f156202a362a1321d535859843d3c3e6f9 228996 
 954ca37fd622065c59230bc60ba69241c0bdb4d1 19743 
 93acd482991334ac6c931e37aab7055d443896ccc7f6ae9238a244fd76cdc0d8 4448 
 94c51de383d6ca147dc0399456956c86a58ba89b4fe66c6a78f110f914a5820f 228996 
 962e9b53ecadc33c93047fb65b3e26c0eec646f1f462e511b7f6f03345783d93 19743 
 69ec778a275fc9f33c8701261207bad9 4448 database optional 
 061cae5b0ead193f040a5170d63bd3be 228996 database optional 
 5bdacfc735a666da5f7a7c147c4b7be6 19743 database optional 



--- End Message ---

Reply via email to