Description of problem: When adding a new user to the SASL database ("saslpasswd2 -c username"), I get a bunch of log messages in syslog (/var/log/messages), like this: Nov 2 14:18:55 senfl saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found Nov 2 14:18:55 senfl saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found As far as I can tell these log messages appear to be irrelevant and should be ignored. The operation succeeded, but saslpasswd2 is still logging error messages. This doesn't prevent one from using SASL but it is confusing. A websearch suggests that perhaps this is something having to do with SASL->SASL2 migration: that saslpasswd2 is trying to delete the entry from an old SASL database while adding it to the SASL2 database. That seems like a misdesign, though. I started from a fresh Fedora 9 install with no prior SASL database, and the very first time I ran saslpasswd2, I got these errors. These log messages caused me to go astray while trying to debug a problem that turned out to be unrelated. Not a showstopper but presumably worth fixing. Version-Release number of selected component (if applicable): # rpm -q -f =saslpasswd2 cyrus-sasl-lib-2.1.22-15.fc9.x86_64 cyrus-sasl-lib-2.1.22-15.fc9.i386 Other installed RPMs in case they are relevant: cyrus-sasl-lib-2.1.22-15.fc9.i386 perl-Authen-SASL-2.10-2.fc9.noarch cyrus-sasl-lib-2.1.22-15.fc9.x86_64 cyrus-sasl-plain-2.1.22-15.fc9.x86_64 cyrus-sasl-md5-2.1.22-15.fc9.x86_64 cyrus-sasl-devel-2.1.22-15.fc9.x86_64 cyrus-sasl-2.1.22-15.fc9.x86_64 How reproducible: 100% reproducible. Steps to Reproduce: 1. As root, run: saslpasswd2 -c anyusername 2. Then: tail -f /var/log/messages Actual results: This message is logged via syslog: Nov 2 14:18:55 senfl saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found Expected results: No errors should be logged via syslog.
Upstream bug https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3117
The url is now https://bugzilla.cyrusimap.org/show_bug.cgi?id=3117 and this is still a problem in Fedora 16