Bug#842009: fatal: load_library_symbols: dlopen failure

Thomas

unread,

Oct 25, 2016, 5:00:03 AM10/25/16

to

Package: postfix-mysql
Version: 3.1.3-1
Severity: important

Dear Maintainer,

after upgrading postfix and it's depending packages to 3.1.3-1 I cannot send emails anymore.
In /var/log/mail.err this error is tracked:
Oct 25 10:16:26 vm104-mail postfix/proxymap[3263]: fatal: load_library_symbols: dlopen failure loading /usr/lib/postfix/postfix-mysql.so.1.0.1: libmariadbclient.so.18: cannot open shared object file: No such file or directory

After downgrading to previous version 3.1.0-5+b1 this error is not reported anymore and mailserver works as expected.

-- System Information:
Debian Release: 8.6
APT prefers stable
APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.19-1-pve (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages postfix-mysql depends on:
ii libc6 2.19-18+deb8u6
ii libmysqlclient18 10.1.18+maria-1~jessie
ii postfix 3.1.3-1

postfix-mysql recommends no packages.

postfix-mysql suggests no packages.

-- no debconf information

Scott Kitterman

unread,

Oct 25, 2016, 9:30:03 AM10/25/16

to

postfix-mysql 3.1.3-1 depends on libmariadbclient18, not libmysqlclient18. Also, 10.1.18+maria-1~jessie is not a Debian libmysqlclient18 version. Where did it come from?

Presumably this is a stable system you've partially upgraded? Try it again with libmariadbclient18 installed.

Scott K

c.m...@web.de

unread,

Oct 25, 2016, 10:10:03 AM10/25/16

to

Hello!

Thanks for this input.

Actually on my server I have installed both, libmariadbclient18 and libmysqlclient18.

root@vm104-mail:~# apt list --installed | grep client18
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
libmariadbclient18/unknown,now 10.1.18+maria-1~jessie amd64 [installed]
libmysqlclient18/unknown,now 10.1.18+maria-1~jessie amd64 [installed]

Do you recommend to uninstall libmysqlclient18?

I have installed MariaDB from official repo
http://mirror2.hs-esslingen.de/mariadb/repo/10.1/debian

THX
Thomas

Scott Kitterman

unread,

Oct 25, 2016, 1:40:03 PM10/25/16

to

On October 25, 2016 7:00:05 AM PDT, c.m...@web.de wrote:
>Hello!
>
>Thanks for this input.
>
>Actually on my server I have installed both, libmariadbclient18 and
>libmysqlclient18.
>
>root@vm104-mail:~# apt list --installed | grep client18
>WARNING: apt does not have a stable CLI interface. Use with caution in
>scripts.
>libmariadbclient18/unknown,now 10.1.18+maria-1~jessie amd64 [installed]
>libmysqlclient18/unknown,now 10.1.18+maria-1~jessie amd64 [installed]
>
>Do you recommend to uninstall libmysqlclient18?
>
>I have installed MariaDB from official repo
>http://mirror2.hs-esslingen.de/mariadb/repo/10.1/debian

Where do their packages install libmariadbclient.so.18? Is the path architecture qualified as in Debian (for example):

/usr/lib/x86_64-linux-gnu/libmariadbclient.so.18

Scott K

Thomas

unread,

Oct 26, 2016, 2:10:02 AM10/26/16

to

Hi,

file libmariadbclient.so.18 does not exist on my system.

root@vm104-mail:~# find /usr/ -name "lib*client.so*"
/usr/lib/libc-client.so.2007e.0
/usr/lib/libmysqlclient.so.18.0.0
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3.2.9
/usr/lib/x86_64-linux-gnu/libdebconfclient.so.0.0.0
/usr/lib/x86_64-linux-gnu/libdebconfclient.so.0
/usr/lib/libmysqlclient.so.18
/usr/lib/libc-client.so.2007e

An this is the content of
libmariadbclient18_10.1.18+maria-1~jessie_amd64.deb:
root@vm104-mail:~# dpkg-deb -c
/var/cache/apt/archives/libmariadbclient18_10.1.18+maria-1~jessie_amd64.deb
drwxr-xr-x root/root 0 2016-09-30 05:28 ./
drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/
drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/share/
drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/share/doc/
drwxr-xr-x root/root 0 2016-09-30 05:29
./usr/share/doc/libmariadbclient18/
-rw-r--r-- root/root 417 2016-09-30 05:11
./usr/share/doc/libmariadbclient18/changelog.Debian.gz
-rw-r--r-- root/root 2502 2016-09-29 21:06
./usr/share/doc/libmariadbclient18/copyright
drwxr-xr-x root/root 0 2016-09-30 05:29 ./usr/lib/
-rw-r--r-- root/root 3799016 2016-09-30 05:28
./usr/lib/libmysqlclient.so.18.0.0
drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/lib/mysql/
drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/lib/mysql/plugin/
-rw-r--r-- root/root 10096 2016-09-30 05:28
./usr/lib/mysql/plugin/dialog.so
-rw-r--r-- root/root 6000 2016-09-30 05:28
./usr/lib/mysql/plugin/mysql_clear_password.so
lrwxrwxrwx root/root 0 2016-09-30 05:29
./usr/lib/libmysqlclient_r.so.18 -> libmysqlclient.so
lrwxrwxrwx root/root 0 2016-09-30 05:29
./usr/lib/libmysqlclient_r.so.18.0.0 -> libmysqlclient.so
lrwxrwxrwx root/root 0 2016-09-30 05:29
./usr/lib/libmysqlclient.so.18 -> libmysqlclient.so.18.0.0

Would a softlink fix the issue?
Or should I downgrade MariaDB client?
Or should I contact maintainers of MariaDB 10.1?

THX
Thomas

Nathan Anderson

unread,

Oct 26, 2016, 3:50:02 AM10/26/16

to

I experience the same issue with MariaDB 10.1 from MariaDB's own repository (not sure why 10.1 isn't in Debian's repo to begin with...).

I spun up a VM and tested postfix-mysql 3.1.3-1 with mysql-5.7 from Debian's unstable repo and I couldn't get mysql sasl dbs to work there either...

On Wed, 26 Oct 2016 07:59:23 +0200 Thomas wrote: > Hi, > > file libmariadbclient.so.18 does not exist on my system. > > root@vm104-mail:~# find /usr/ -name "lib*client.so*" > /usr/lib/libc-client.so.2007e.0 > /usr/lib/libmysqlclient.so.18.0.0 > /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 > /usr/lib/x86_64-linux-gnu/libavahi-client.so.3.2.9 > /usr/lib/x86_64-linux-gnu/libdebconfclient.so.0.0.0 > /usr/lib/x86_64-linux-gnu/libdebconfclient.so.0 > /usr/lib/libmysqlclient.so.18 > /usr/lib/libc-client.so.2007e > > An this is the content of > libmariadbclient18_10.1.18+maria-1~jessie_amd64.deb: > root@vm104-mail:~# dpkg-deb -c > /var/cache/apt/archives/libmariadbclient18_10.1.18+maria-1~jessie_amd64.deb > drwxr-xr-x root/root 0 2016-09-30 05:28 ./ > drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/ > drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/share/ > drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/share/doc/ > drwxr-xr-x root/root 0 2016-09-30 05:29 > ./usr/share/doc/libmariadbclient18/ > -rw-r--r-- root/root 417 2016-09-30 05:11 > ./usr/share/doc/libmariadbclient18/changelog.Debian.gz > -rw-r--r-- root/root 2502 2016-09-29 21:06 > ./usr/share/doc/libmariadbclient18/copyright > drwxr-xr-x root/root 0 2016-09-30 05:29 ./usr/lib/ > -rw-r--r-- root/root 3799016 2016-09-30 05:28 > ./usr/lib/libmysqlclient.so.18.0.0 > drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/lib/mysql/ > drwxr-xr-x root/root 0 2016-09-30 05:28 ./usr/lib/mysql/plugin/ > -rw-r--r-- root/root 10096 2016-09-30 05:28 > ./usr/lib/mysql/plugin/dialog.so > -rw-r--r-- root/root 6000 2016-09-30 05:28 > ./usr/lib/mysql/plugin/mysql_clear_password.so > lrwxrwxrwx root/root 0 2016-09-30 05:29 > ./usr/lib/libmysqlclient_r.so.18 -> libmysqlclient.so > lrwxrwxrwx root/root 0 2016-09-30 05:29 > ./usr/lib/libmysqlclient_r.so.18.0.0 -> libmysqlclient.so > lrwxrwxrwx root/root 0 2016-09-30 05:29 > ./usr/lib/libmysqlclient.so.18 -> libmysqlclient.so.18.0.0 > > Would a softlink fix the issue? > Or should I downgrade MariaDB client? > Or should I contact maintainers of MariaDB 10.1? > > THX > Thomas > > Am 25.10.2016 um 19:37 schrieb Scott Kitterman: > > > > > > On October 25, 2016 7:00:05 AM PDT, c.m...@web.de wrote: > >> Hello! > >> > >> Thanks for this input. > >> > >> Actually on my server I have installed both, libmariadbclient18 and

Scott Kitterman

unread,

Oct 26, 2016, 5:10:03 AM10/26/16

to

On October 26, 2016 12:27:33 AM PDT, Nathan Anderson <nat...@nja.id.au> wrote:
>I experience the same issue with MariaDB 10.1 from MariaDB's own
>repository (not sure why 10.1 isn't in Debian's repo to begin with...).
>
>
>I spun up a VM and tested postfix-mysql 3.1.3-1 with mysql-5.7 from
>Debian's unstable repo and I couldn't get mysql sasl dbs to work there
>either...

The postfix-mysql package for 3.1.3-1 is compiled against Debian's mariadb (the default MySQL implementation for the next release). See https://packages.debian.org/unstable/postfix-mysql - did you try it with libmariadbclient18? Simply installing postfix-mysql will cause that to be installed.

Based on the information provided, the packages provided by MariaDB are not binary compatible with the Debian packages. For postfix-mysql to work with them, it would have to be rebuilt locally. This is obviously not something that the postfix maintainers can provide support for.

It might be worth a discussion with the Debian mariadb maintainers and the external package providers to determine if they can be made more compatible. Either way, postfix is just a bystander.

Scott K

Nathan Anderson

unread,

Oct 26, 2016, 5:40:03 AM10/26/16

to

In response to 'libmariadbclient18', here's a list of mariadb packages:

dpkg -l | grep maria
ii libmariadbclient18 10.1.18+maria-1~sid amd64
MariaDB database client library
ii libmysqlclient18 10.1.18+maria-1~sid amd64
Virtual package to satisfy external depends
ii mariadb-client-10.1 10.1.18+maria-1~sid amd64
MariaDB database client binaries
ii mariadb-client-core-10.1 10.1.18+maria-1~sid amd64
MariaDB database core client binaries
ii mariadb-common 10.1.18+maria-1~sid all
MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf)
ii mariadb-server 10.1.18+maria-1~sid all
MariaDB database server (metapackage depending on the latest
version)
ii mariadb-server-10.1 10.1.18+maria-1~sid amd64
MariaDB database server binaries
ii mariadb-server-core-10.1 10.1.18+maria-1~sid amd64
MariaDB database core server files
ii mysql-common 10.1.18+maria-1~sid all
MariaDB database common files (e.g. /etc/mysql/my.cnf)

Postfix/postfix-mysql 3.1.0-5+b1 doesn't have this issue that's being
reported so are you sure it's just a bystander?

On Wed, 26 Oct 2016 01:36:01 -0700 Scott Kitterman wrote: > > > On
October 26, 2016 12:27:33 AM PDT, Nathan Anderson wrote: > >I experience

Scott Kitterman

unread,

Oct 26, 2016, 5:50:03 AM10/26/16

to

On October 26, 2016 2:30:04 AM PDT, Nathan Anderson <nat...@nja.id.au> wrote:
>In response to 'libmariadbclient18', here's a list of mariadb packages:
>
>dpkg -l | grep maria
>ii libmariadbclient18 10.1.18+maria-1~sid amd64
>
> MariaDB database client library
>ii libmysqlclient18 10.1.18+maria-1~sid amd64
>
> Virtual package to satisfy external depends
>ii mariadb-client-10.1 10.1.18+maria-1~sid amd64
>
> MariaDB database client binaries
>ii mariadb-client-core-10.1 10.1.18+maria-1~sid amd64
>
> MariaDB database core client binaries
>ii mariadb-common 10.1.18+maria-1~sid all
>
> MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf)
>ii mariadb-server 10.1.18+maria-1~sid all
>
> MariaDB database server (metapackage depending on the latest
>version)
>ii mariadb-server-10.1 10.1.18+maria-1~sid amd64
>
> MariaDB database server binaries
>ii mariadb-server-core-10.1 10.1.18+maria-1~sid amd64
>
> MariaDB database core server files
>ii mysql-common 10.1.18+maria-1~sid all
>
> MariaDB database common files (e.g. /etc/mysql/my.cnf)
>
>Postfix/postfix-mysql 3.1.0-5+b1 doesn't have this issue that's being
>reported so are you sure it's just a bystander?

Prior to 3.1.3-1, postfix was compiled using the Debian MySQL packages. Based on the guidelines provided by the Debian team that is maintaining MySQL and it's variants, we changed to build against the default MySQL implementation, which is MariaDB.

As far as I can tell, the error described in this bug report won't happen with the libmariadbclient18 packages in Debian. The problem is that the packages provided by MariaDB are done differently (files named like a MySQL package).

The bottom line issue is the difference between the MariaDB packages in Debian and those provided by MariaDB.

Scott K

Thomas

unread,

Oct 30, 2016, 2:40:02 PM10/30/16

to

Hello!

After uninstalling MariaDB-Client-10.1, installing MariaDB-Client
(10.0.27-2) from Debian repo and upgrading postfix (3.1.3-1)
root@vm104-mail:~# dpkg -l | grep maria
ii libmariadbclient18:amd64 10.0.27-2 amd64
MariaDB database client library
ii mariadb-client 10.0.27-2 all
MariaDB database client (metapackage depending on the latest version)
ii mariadb-client-10.0 10.0.27-2 amd64
MariaDB database client binaries
rc mariadb-client-10.1 10.1.18+maria-1~jessie amd64
MariaDB database client binaries
ii mariadb-client-core-10.0 10.0.27-2 amd64

MariaDB database core client binaries

ii mariadb-common 10.0.27-2 all
MariaDB common metapackage

root@vm104-mail:~# dpkg -l | grep postfix
ii postfix 3.1.3-1 amd64
High-performance mail transport agent
ii postfix-ldap 3.1.3-1 amd64
LDAP map support for Postfix
ii postfix-mysql 3.1.3-1 amd64
MySQL map support for Postfix
ii postfix-pcre 3.1.3-1 amd64
PCRE map support for Postfix

I get this error in /var/log/mail.err:
Oct 30 19:30:49 vm104-mail dovecot: managesieve-login: Error: Timeout
waiting for handshake from auth server. my pid=31553, input bytes=0
Oct 30 19:30:49 vm104-mail dovecot: managesieve-login: Error: Timeout
waiting for handshake from auth server. my pid=31549, input bytes=0
Oct 30 19:30:51 vm104-mail dovecot: auth: Fatal: Unknown database driver
'mysql'
Oct 30 19:30:51 vm104-mail dovecot: master: Error: service(auth):
command startup failed, throttling for 60 secs
Oct 30 19:31:10 vm104-mail dovecot: auth: Fatal: Unknown database driver
'mysql'
Oct 30 19:31:10 vm104-mail dovecot: master: Error: service(auth):
command startup failed, throttling for 2 secs
Oct 30 19:31:15 vm104-mail dovecot: auth: Fatal: Unknown database driver
'mysql'
Oct 30 19:31:15 vm104-mail dovecot: master: Error: service(auth):
command startup failed, throttling for 4 secs
Oct 30 19:31:20 vm104-mail dovecot: auth: Fatal: Unknown database driver
'mysql'
Oct 30 19:31:20 vm104-mail dovecot: master: Error: service(auth):
command startup failed, throttling for 8 secs
Oct 30 19:31:28 vm104-mail dovecot: auth: Fatal: Unknown database driver
'mysql'
Oct 30 19:31:28 vm104-mail dovecot: master: Error: service(auth):
command startup failed, throttling for 16 secs
Oct 30 19:31:44 vm104-mail dovecot: auth: Fatal: Unknown database driver
'mysql'
Oct 30 19:31:44 vm104-mail dovecot: master: Error: service(auth):
command startup failed, throttling for 32 secs

What's causing this issue now?
Should I open another ticket?

Scott Kitterman

unread,

Oct 30, 2016, 3:20:03 PM10/30/16

to

That's a consequence of the postfix you're using being compiled with mariadb and dovecot still using mysql.

See https://lintian.debian.org/maintainer/jaldhar...@debian.org.html#dovecot

It might be worth filing a bug against dovecot to switch.

Scott K

c.m...@web.de

unread,

Oct 31, 2016, 4:10:02 AM10/31/16

to

All right.

From my point of view this bug report can be closed.