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 761041 - 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 6
Classification: Red Hat
Component: cyrus-sasl
Version: 6.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 822961
TreeView+ depends on / blocked
 
Reported: 2011-12-07 15:49 UTC by Stanislav Graf
Modified: 2016-06-13 14:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 822961 1278309 (view as bug list)
Environment:
Last Closed: 2016-06-13 14:17:31 UTC
Target Upstream Version:
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 469592 0 medium CLOSED saslpasswd2 triggers bogus log messages ("error deleting entry from sasldb") 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 761381 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 469592 761381

Description Stanislav Graf 2011-12-07 15:49:04 UTC 
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

Additional info:
Comment 3 Suzanne Logcher 2012-02-14 23:23:16 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 4 RHEL Program Management 2012-09-07 05:13:43 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 5 RHEL Program Management 2013-10-14 00:53:08 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 6 Jakub Jelen 2016-06-13 14:17:31 UTC 
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6 and therefore will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.
Note You need to log in before you can comment on or make changes to this bug.