Hi,
don't worry about it. Regressions can be serious. Let's mark this bug as
incomplete then, and it will auto-expire on its own if no further
information is added to it.
If you ever see this again, or have more data, feel free to add a
comment here.
Cheers, thanks for getting back to us with the results.
** Changed in: cyrus-sasl2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861230
Title:
_sasl_plugin_load failed
Status in cyrus-sasl2 package in Ubuntu:
Incomplete
Bug description:
We are seeing the following in the journal after upgrading to these
sets of packages:
libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1
amd64
libsasl2-modules/bionic-updates,bionic-security
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
libsasl2-modules-db/bionic-updates,bionic-security
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
libsasl2-modules-gssapi-mit/bionic-updates,bionic-security
2.1.27~101-g0780600+dfsg-3ubuntu2.1
Here are the errors:
Jan 28 15:58:43 my-hostname sssd[20949]: Starting up
Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up
Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb
Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on
sasl_canonuser_init
Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
