RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1278309 - saslpasswd2 triggers bogus log messages ("error deleting entry from sasldb")
Summary: saslpasswd2 triggers bogus log messages ("error deleting entry from sasldb")
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cyrus-sasl
Version: 7.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-05 08:52 UTC by Patrik Kis
Modified: 2018-06-19 06:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 761041
Environment:
Last Closed: 2018-06-19 06:18:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Patrik Kis 2015-11-05 08:52:27 UTC
The bug also exists in RHEL-7.2.
cyrus-sasl-2.1.26-19.2.el7

+++ This bug was initially created as a clone of Bug #761041 +++

Description of problem:

Adding a new user to the SASL database ("saslpasswd2 -c username") produce error in /var/log/messages, but command is successfully executed and user exists.

# saslpasswd2 -c anyusername
Password: 
Again (for verification): 
[16:42:53] ecode=0
# tail /var/log/messages | grep 16:42
Dec  7 16:42:53 local-rhel6i saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found
Dec  7 16:42:53 local-rhel6i saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found
Dec  7 16:42:53 local-rhel6i saslpasswd2: error deleting entry from sasldb: DB_NOTFOUND: No matching key/data pair found
[16:43:10] ecode=0
# sasldblistusers2
anyusername@local-rhel6i: userPassword
[16:47:50] ecode=0

Version-Release number of selected component (if applicable):
cyrus-sasl-lib-2.1.23-13.el6

How reproducible:
100%

Steps to Reproduce:
1. # saslpasswd2 -c anyusername
2. # tail /var/log/messages
3. # sasldblistusers2
  
Actual results:
Adding user produces error log

Expected results:
Adding user doesn't produce error log

Comment 2 Jakub Jelen 2017-07-19 12:51:20 UTC
Current GitHub Issue with this bug upstream:

https://github.com/cyrusimap/cyrus-sasl/issues/264

Not fixed yet. Adding cond nack.


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