Hi Randy, The deinstall of the module libsasl2-modules-ldap solved the issue. It was installed, but not in use and therefore not configured which results in the mentioned warnings.
Grtz, Stefan > Op 2 jul. 2018, om 19:02 heeft Ryan Tandy <r...@nardis.ca> het volgende > geschreven: > > Hi Stefan, > > On Mon, Jul 02, 2018 at 12:26:08PM +0200, Stefan van Lieshout wrote: >> The upgrade to 2.4.40+dfsg-1+deb8u4 results in a lot of warnings in the >> logfile /var/log/auth.log >> >> Jul 2 09:27:43 hostname apache2: ldapdb_canonuser_plug_init() failed in >> sasl_canonuser_add_plugin(): invalid parameter supplied >> Jul 2 09:27:43 hostname apache2: _sasl_plugin_load failed on >> sasl_canonuser_init for plugin: ldapdb >> >> This is not only for the apache2 process, also sssd_be, sm-mta & php spawn >> the same warnings. >> >> A downgrade to 2.4.40+dfsg-1+deb8u3 did solve the issue. > > Thank you for the report. Indeed one thing that changed in this version is > that libldap now initializes libsasl eagerly, instead on on first use, so > previously these messages might have only appeared when a process invoked > SASL via LDAP - or not at all. > > You are the first to mention an issue like this, though, so I wonder if it's > caused by a local configuration on your side. > > Is your libsasl2-modules-ldap up-to-date with libsasl2-2? What do you use it > for?
