Hide Forgot
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:
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.
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.
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.