After upgrading to cyrus-sasl-2.1.20-r2, the /etc/sasl2/sasldb2 is replaced with an "empty" user database, breaking cyrus authentications. Reproducible: Always Steps to Reproduce: 1. use sasldblistusers2 to show current users 2. upgrade 3. after the upgrade sasldblistusers2 shows no users Expected Results: The upgrade should save the current sasldb2 file and restore it. If there is a change in the database format, the current database should be migrated to it. At the very minimum, the current database should be saved before overwriting and a notice given that restoring the database manually is necessary. Workaround: save the file manually before upgrading, and restoring it after the upgrade. That's what I did this time around.
When you upgraded and ran etc-update you were prompted about what to do with /etc/sasl2/sasldb2; and you told etc-update to update it. Sorry, but this is not a bug. Feel free to comment and ask anything you want, tough. Cheers, Ferdy
It's strange. When I upgraded, there was no notice to use etc-update (and I normally use dispatch-conf) and I'm positive that I did not update any config files at all. I try to be careful about config updates since this box is my production server. I just reran the upgrade, and, sure enough, there's the notice for etc-update. I ran dispatch-conf, "zapped" the new sasldb2, and all is well. <sigh> Ok, gremlins. Thanks for your work maintaining this. I do depend on cyrus and friends... Kirk
I have often had this same problem. Think it might be a weird problem with dispatch-conf and diff. See bug 129670
