Bug 868853 - Winsync: DS error logs report wrong version of Windows AD when winsync is configured.
Winsync: DS error logs report wrong version of Windows AD when winsync is con...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Rich Megginson
Sankar Ramalingam
Depends On:
Blocks: 881827
  Show dependency treegraph
Reported: 2012-10-22 05:51 EDT by Sankar Ramalingam
Modified: 2013-02-21 03:21 EST (History)
3 users (show)

See Also:
Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Cause: When enabling replication level logging, winsync prints out what version of Windows/AD it detects. If it detects win2k3 or later, it prints out "detected win2k3 peer". Consequence: This can be confusing if you are running a later version, such as win2k8 Fix: This patch changes the message to match this logic by printing "detected win2k3 or later peer". Result: The version string is now less confusing and accurate.
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 03:21:10 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0503 normal SHIPPED_LIVE Moderate: 389-ds-base security, bug fix, and enhancement update 2013-02-21 03:18:44 EST

  None (edit)
Description Sankar Ramalingam 2012-10-22 05:51:15 EDT
Description of problem: When winsync is configured, DS error logs prints wrong version of Windows server. It prints "windows_conn_connect : detected Win2k3 peer". Where as the version which is configured is windows 2008.

Version-Release number of selected component (if applicable): 389-ds-base-1.2.11

How reproducible: Consistently

Steps to Reproduce:
1. Install the latest build of 389-ds-base-1.2.11 on RHEL64.
2. Create an instance and configure winsync.
3. Set DS error logs with nsslapd-errorlog-level: 8192
4. Check the version of windows server - search for "windows_conn_connect" string in the DS error logs.
Actual results: It prints "detected Win2k3 peer"

Expected results: It should print "detected Win2k8 peer" or "detected Win2k8r2  peer" depending on what exact windows version is configured.

Additional info:
Comment 2 Rich Megginson 2012-10-23 13:45:16 EDT
Note that the detection is really looking for win2k3 _or later_, so the error message should say "detected win2k3 or later peer".
Comment 3 Nathan Kinder 2012-11-06 10:25:59 EST
Upstream ticket:
Comment 4 Nathan Kinder 2012-11-12 11:09:13 EST
This has been checked in upstream:

master - e3357b44187acf3f43ad52a62c78911bea620b88
389-ds-base-1.2.11 - 98b809ba580530d9418e7bbf857e1ff2b79f75c8
Comment 6 Sankar Ramalingam 2012-11-20 06:40:55 EST
Upgraded the existing 389-ds-base package for the existing winsync setup and observed that the error message is changed.
windows_conn_connect : detected Win2k3 or later peer

Hence marking the bug as Verified.
Comment 7 errata-xmlrpc 2013-02-21 03:21:10 EST
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.


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