Bug 469592 - saslpasswd2 triggers bogus log messages ("error deleting entry from sasldb")
Summary: saslpasswd2 triggers bogus log messages ("error deleting entry from sasldb")
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: cyrus-sasl
Version: 16
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-02 23:19 UTC by D. Wagner
Modified: 2011-12-07 15:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-03 08:32:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Cyrus IMAP 3117 0 None None None Never
Red Hat Bugzilla 761041 0 low CLOSED saslpasswd2 triggers bogus log messages ("error deleting entry from sasldb") 2021-02-22 00:41:40 UTC

Internal Links: 761041

Description D. Wagner 2008-11-02 23:19:16 UTC
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.

Comment 1 Tomas Mraz 2008-11-03 08:32:48 UTC
Upstream bug https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3117

Comment 2 Joseph Shraibman 2011-11-23 18:01:07 UTC
The url is now https://bugzilla.cyrusimap.org/show_bug.cgi?id=3117 and this is still a problem in Fedora 16


Note You need to log in before you can comment on or make changes to this bug.