This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2209047 - Inconsistencies in the log messages
Summary: Inconsistencies in the log messages
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 12.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: DS12.5
: dirsrv-12.5
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
Evgenia Martynyuk
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-22 12:27 UTC by Viktor Ashirov
Modified: 2024-06-26 13:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-26 13:49:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   DIRSRV-39 0 None None Red Hat Issue Tracker 2024-06-26 13:49:04 UTC
Red Hat Issue Tracker IDMDS-4010 0 None None None 2024-01-03 16:31:55 UTC

Description Viktor Ashirov 2023-05-22 12:27:24 UTC 
Description of problem:
From https://bugzilla.redhat.com/show_bug.cgi?id=2057070 

There are some inconsistencies in the log messages, that might affect log parsing (i.e. for monitoring systems):
1. Mixed first letter case, see attached file

2. Double space before "Entry:"
Account is locked and requires administrator reset.  Entry (uid=dbyers,ou=people,dc=example,dc=com) Policy (Global)
(also this message is a bit confusing, in the source right above it says: "Exceed password retry limit. Contact system administrator to reset.")
password retry limit exceeded.  Entry (uid=tuser,ou=people,dc=example,dc=com) Policy (Global)
user is not allowed to change password.  Entry (uid=dbyers,ou=People,dc=example,dc=com) Policy (Global)

3. Dot at the end of the message
update pwdTPRUseCount=1 on entry (uid=jdoe1,ou=people,dc=example,dc=com) policy (Global).

4. Mixed separators before "Entry" (dot instead of colon)
Account is locked and requires administrator reset.  Entry (uid=dbyers,ou=people,dc=example,dc=com) Policy (Global)

5. Entry/Policy small case
Unsuccessful bind, increase pwdTPRUseCount = 1 (max 3) - entry (uid=jdoe1,ou=People,dc=example,dc=com) policy (Global)

6. Function name in the message (not sure, maybe it should be there, but it's the only one I encountered)
slapi_check_tpr_limits - attempt to bind with TPR password not yet valid (current=20230210133504Z, validity=20230210133514Z): Entry (uid=jdoe2,ou=people,dc=example,dc=com) Policy (Global)

Version-Release number of selected component (if applicable):
389-ds-base-2.2.6-1.module+el9dsrv+17949+63c5b04e
Comment 2 Viktor Ashirov 2024-06-26 13:49:05 UTC 
This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-39. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.