[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
[Expired for cyrus-sasl2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cyrus-sasl2 (Ubuntu) Status: Incomplete => Expired -- 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: Expired 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
In trying to recreate the issue this afternoon, it looks as though installs based on all of the updated / most recent packages are succeeding again (i.e., this may no longer be an issue). In our dpkg logs, we noticed that an update came through today for libc- bin (2.27-3ubuntu1), and wonder if this update may have been part of what resolved the issue. If that is not part of why this is working, then I will bury my head / beg your forgiveness and try to figure out if there was some other cause. Please understand that this stopped working the same day that we got the libsasl2 package updates, and that reverting the libsasl2 updates allowed us to get our installs working, so that is why we filed a bug against this package. Thanks again for your help. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
We are doing additional testing here. Please sit tight / do not research further until we check into things further on our end. Thanks again for your help. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
Before I continue - I want to say thanks for your response to this report. I appreciate your effort and help. As for the issue, when I say, "If I only install the latest packages" I mean a fully up-to-date system at the time of install, including sssd version 1.16.1-1ubuntu1.4. As part of my testing, I always used sssd version 1.16.1-1ubuntu1.4 (even when I downgraded / upgraded the referenced libsasl packages (libsasl2-2, libsasl2-modules-db, libsasl2-modules, libsasl2-modules-gssapi-mit). In terms of back-end, we use Windows AD. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
What about ldap, is that openldap on the same server, or windows ad? -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
By "packages", do you mean only the cyrus-sasl2 packages, or also sssd? In your tests, is sssd being restarted each time? -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
... I tried this following Leonidas' (leosilvab) request to "Could you downgrade to the previous version and check if it happens there too? And so re upgrade and re-test?" -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
If I only install the latest packages (without the earlier versions of these packages being installed previously) (i.e., if I do a clean install of the most current packages when deploying a new host), it does not work. If I downgrade the packages to the prior versions, and then upgrade the packages to their latest versions, it does work. To me, this is repeatable. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
So, when the system is up-to-date, there is no issue? I thought you started seeing this problem *after* upgrading cyrus-sasl2. Sorry if I'm confused. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
After allowing the packages to be upgraded to their newer versions, the problem does _not_ persist. We see expected / desired results. We only get a good outcome after the packages have been upgraded, though. When the packages are installed as the initial versions ... that is when we consistently see the issue. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
I will try updating the packages to their current-released versions and see if the problem persists. We ran into this issue across several 18.04 deployments yesterday, though. It prevented commands like `id -u username` from working (at least that is how we initially noticed a problem). I'll revert my work-arounds, update the affected packages, and will report-back shortly, though. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
I can confirm the sssd dep8 tests pass in bionic with the updated sasl package: Get:3 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsasl2-2 amd64 2.1.27~101-g0780600+dfsg-3ubuntu2.1 [49.2 kB] Get:41 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 sssd-ldap amd64 1.16.1-1ubuntu1.4 [28.8 kB] autopkgtest [12:53:44]: test ldap-user-group-krb5-auth: - - - - - - - - - - results - - - - - - - - - - ldap-user-group-krb5-auth PASS autopkgtest [12:53:45]: summary ldap-user-group-ldap-auth PASS ldap-user-group-krb5-auth PASS (full output here: http://people.ubuntu.com/~ahasenack/sssd-dep8-update- sasl.txt) -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
We are using SSSD version 1.16.1-1ubuntu1.4 on Ubuntu 18.04.3. The package itself is from the standard Ubuntu repos. $ dpkg -s sssd Package: sssd Status: install ok installed Priority: extra Section: metapackages Installed-Size: 32 Maintainer: Ubuntu Developers Architecture: amd64 Multi-Arch: foreign Version: 1.16.1-1ubuntu1.4 -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
When downgrading to the prior package, we do not see this problem. We've taken the following steps as a work-around: - apt-get -y --allow-downgrades install libsasl2-2=2.1.26.dfsg1-14build1 - apt-get -y --allow-downgrades install libsasl2-modules-db=2.1.26.dfsg1-14build1 - apt-get -y --allow-downgrades install libsasl2-modules=2.1.26.dfsg1-14build1 - apt-get -y --allow-downgrades install libsasl2-modules-gssapi-mit=2.1.26.dfsg1-14build1 Then we've used apt-pinning to pin those versions: Package: libsasl2-2 Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 Package: libsasl2-modules Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 Package: libsasl2-modules-db Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 Package: libsasl2-modules-gssapi-mit Pin: release o=Ubuntu version 2.1.26.dfsg1-14build1 Pin-Priority: 999 And we've used a hold to (temporarily) keep them from being upgraded: echo hold | sudo dpkg --set-selections ... We've done that for each of the four above packages. Going this route does prevent the issue for now / keeps SSSD from failing. -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
Can you also please show your sssd version and where it comes from? -- 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: New 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
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
Hi, Could you downgrade to the previous version and check if it happens there too? And so re upgrade and re-test? Thanks! -- 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: New 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
