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 1673472 - the warning about skew time could last forever.
Summary: the warning about skew time could last forever.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.7
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: 7.7
Assignee: Ludwig
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-07 15:24 UTC by German Parente
Modified: 2020-09-13 22:19 UTC (History)
12 users (show)

Fixed In Version: 389-ds-base-1.3.9.1-3.el7
Doc Type: Bug Fix
Doc Text:
Cause: replication adjusts its CSN time generator to manage time differences on different servers. A special handling for large negative time skews could even increase the time skew Consequence: Once this state was reached the error log was flooded with messages about time skew, eventually the skew field could overflow. Fix: remove the special handling for larger negative time skew, the csn genarator is handling the potential oveflow of the offset counter already Result: no more confusing messages, csn generator works correctly
Clone Of:
Environment:
Last Closed: 2019-08-06 12:59:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 3324 0 None None None 2020-09-13 22:19:11 UTC
Red Hat Product Errata RHBA-2019:2152 0 None None None 2019-08-06 12:59:32 UTC

Description German Parente 2019-02-07 15:24:01 UTC
Description of problem:

after a problem with skew time for csn generators, the server tries to adjust the delta but sometimes, instead of reduce it till it will dissapear, we are incrementing it. So, the WARN can last forever.

Example:

[26/Jan/2019:15:25:33.964643906 +0300] - WARN - csngen_new_csn - Too much time skew (-492 secs). Current seqnum=4
[26/Jan/2019:15:25:33.976372625 +0300] - WARN - csngen_new_csn - Too much time skew (-493 secs). Current seqnum=1
[26/Jan/2019:15:25:33.979472136 +0300] - WARN - csngen_new_csn - Too much time skew (-494 secs). Current seqnum=1
[26/Jan/2019:15:25:34.120723671 +0300] - WARN - csngen_new_csn - Too much time skew (-494 secs). Current seqnum=1

it's each time bigger. I will never arrive to 0.


Version-Release number of selected component (if applicable): current version.

Comment 17 mreynolds 2019-03-22 14:10:56 UTC
https://pagure.io/389-ds-base/issue/50265

Comment 19 Akshay Adhikari 2019-05-22 06:04:05 UTC
Bild Tested: 389-ds-base-1.3.9.1-7.el7.x86_64

The warning message is hard to reproduce, changes can be seen in the source. 
Marking it as VERIFIED, SanityOnly.

Comment 21 errata-xmlrpc 2019-08-06 12:59:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2152


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