Bug 820258
Summary: | Change in winSyncInterval does not take immediate effect | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Steeve Goveas <sgoveas> |
Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Sankar Ramalingam <sramling> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | jgalipea, nhosoi, nkinder, sgoveas |
Target Milestone: | rc | ||
Target Release: | 7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 389-ds-base-1.3.1.2-1.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-13 13:24:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Upstream ticket: https://fedorahosted.org/389/ticket/393 moving all ON_QA bugs to MODIFIED in order to add them to the errata (can't add bugs in the ON_QA state to an errata). When the errata is created, the bugs should be automatically moved back to ON_QA. Hi Steeve, Requesting you to verify bugzilla from the IPA's automated test runs. Clearing the NEED_INFO flag since the request is also sent by email. :: [ PASS ] :: Creating error log ldif file (Expected 0, got 0) modifying entry "cn=config" :: [ PASS ] :: Setting the error log level (Expected 0, got 0) :: [ PASS ] :: Creating sync interval ldif file (Expected 0, got 0) modifying entry "cn=meTosquab.adrelm.com,cn=replica,cn=dc\3Dtestrelm\2Cdc\3Dcom,cn=mapping tree,cn=config" :: [ PASS ] :: Change winsync interval to 30 seconds (Expected 0, got 0) :: [ PASS ] :: Waiting for new interval logs (Expected 0, got 0) :: [ PASS ] :: Running 'grep "Running Dirsync" /var/log/dirsrv/slapd-TESTRELM-COM/errors | tail -n2 > /tmp/tmp.J3C2YukU34/tmpout.ipa_winsync_bz820258.out 2>&1' (Expected 0, got 0) [26/Nov/2013:10:01:15 -0500] NSMMReplicationPlugin - Running Dirsync [26/Nov/2013:10:01:45 -0500] NSMMReplicationPlugin - Running Dirsync 01 01 :: [ PASS ] :: Running 'z=0' (Expected 0, got 0) 0 15 45 :: [ PASS ] :: Running 't=30' (Expected 0, got 0) 30 :: [ PASS ] :: Creating file to avoid dirsrv restarts in future tests (Expected 0, got 0) :: [ PASS ] :: Winsync Interval successfully modified to 30 Seconds. bz820258 not found * Re-modify :: [ PASS ] :: Creating sync interval ldif file (Expected 0, got 0) modifying entry "cn=meTosquab.adrelm.com,cn=replica,cn=dc\3Dtestrelm\2Cdc\3Dcom,cn=mapping tree,cn=config" :: [ PASS ] :: Replace winsync interval to 35 seconds (Expected 0, got 0) :: [ PASS ] :: Waiting for new interval logs (Expected 0, got 0) :: [ PASS ] :: Running 'grep "Running Dirsync" /var/log/dirsrv/slapd-TESTRELM-COM/errors | tail -n2 > /tmp/tmp.J3C2YukU34/tmpout.ipa_winsync_0022.out 2>&1' (Expected 0, got 0) [26/Nov/2013:10:21:52 -0500] NSMMReplicationPlugin - Running Dirsync [26/Nov/2013:10:22:27 -0500] NSMMReplicationPlugin - Running Dirsync 52 27 87 :: [ PASS ] :: Running 'r=35' (Expected 0, got 0) 35 :: [ PASS ] :: Winsync Interval successfully re-modified to 35 Seconds * Verified in version 389-ds-base-1.3.1.6-10.el7.x86_64 ipa-server-3.3.3-5.el7.x86_64 This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |
Description of problem: Change in winSyncInterval does not take immediate effect Version-Release number of selected component (if applicable): 389-ds-base-1.2.10.2-6.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure AD winsync 2. Update errorlog level of 389-ds config to 8192 nsslapd-errorlog-level: 8192 3. Modify winsync interval to 120 seconds 4. Observe the error logs for timestamp of "Running Dirsync" eg: tail -f /var/log/dirsrv/slapd-LAB-ENG-PNQ-REDHAT-COM/errors | grep "Running Dirsync" Actual results: Dirsync is initiated at default 300 seconds interval. The new interval doesn't take effect unless dirsrv is restarted. Expected results: winSyncInterval change should take effect immediately without restart. Additional info: Last night I had changed the interval to 600 seconds. Today I set it to 120 seconds and watched the logs to check when the interval change would take effect. After more than an hour I restarted only dirsrv this time. [root@wheeljack ~]# date; ldapmodify -x -D "cn=directory manager" -w wheeljack << EOF dn: cn=meTodhcp201-118.englab.pnq.redhat.com,cn=replica,cn=dc\3Dlab\2Cdc\3Deng\2Cdc\3Dpnq\2Cdc\3Dredhat\2Cdc\3Dcom,cn=mapping tree,cn=config changetype: modify replace: winSyncInterval winSyncInterval: 120 EOF Wed May 9 12:16:06 IST 2012 modifying entry "cn=meTodhcp201-118.englab.pnq.redhat.com,cn=replica,cn=dc\3Dlab\2Cdc\3Deng\2Cdc\3Dpnq\2Cdc\3Dredhat\2Cdc\3Dcom,cn=mapping tree,cn=config" [root@wheeljack ~]# date; service dirsrv restart Wed May 9 13:30:38 IST 2012 Shutting down dirsrv: LAB-ENG-PNQ-REDHAT-COM... [ OK ] PKI-IPA... [ OK ] Starting dirsrv: LAB-ENG-PNQ-REDHAT-COM... [ OK ] PKI-IPA... [ OK ] [root@wheeljack ~]# [root@wheeljack ~]# tail -f /var/log/dirsrv/slapd-LAB-ENG-PNQ-REDHAT-COM/errors | grep "Running Dirsync" [09/May/2012:12:10:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:12:20:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:12:30:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:12:40:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:12:50:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:00:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:10:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:20:24 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:30:24 +051800] NSMMReplicationPlugin - Running Dirsync >>[09/May/2012:13:30:44 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:32:44 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:34:44 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:36:44 +051800] NSMMReplicationPlugin - Running Dirsync [09/May/2012:13:38:44 +051800] NSMMReplicationPlugin - Running Dirsync