Bug 634561
| Summary: | Server crushes when using Windows Sync Agreement | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] 389 | Reporter: | serejka | ||||||||
| Component: | Replication - General | Assignee: | Rich Megginson <rmeggins> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Viktor Ashirov <vashirov> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 1.2.6 | CC: | amsharma, dpal, edewata, jgalipea, nhosoi, nkinder, rmeggins, steven.jones | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-12-07 16:54:03 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 543590, 639035 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
serejka
2010-09-16 11:19:04 UTC
Sorry forgot to mention: There is no PassSync installed on windows side. In previos version 1.2.5 this worked fine. Can you install the 389-ds-base-debuginfo package, then use gdb and do a "bt full" in the thread that got the seg fault? Or just do thread apply all bt full and attach the output to this bug as an attachment. Can you also provide more information about your replication/sync configuration so that we can attempt to reproduce this issue? Created attachment 447781 [details]
output of bt full
Created attachment 447782 [details]
output thread apply all bt full
Ok, here is more info. Windows side: 1. Windows 2003 R2 Russian with Identity Management for UNIX is installed. 2. Identity managment is configured and every user has Unixes attributes (uid, gid, etc.). 3. Also there is no PassSync utility installed on windows host. Linux side: 1. Centos 5.4 installed with EPEL repository. 2. Also latest DS packages are installed: 389-adminutil-1.1.8-4.el5 389-ds-console-1.2.3-1.el5 389-ds-base-1.2.6-1.el5 389-console-1.1.4-1.el5 389-ds-base-debuginfo-1.2.6-1.el5 389-dsgw-1.1.5-1.el5 389-admin-console-1.1.5-1.el5 389-ds-console-doc-1.2.3-1.el5 389-admin-1.1.11-1.el5 389-admin-console-doc-1.1.5-1.el5 389-ds-1.2.1-1.el5 3. DS is configured by default. 4. Create replication manager under "cn=config". dn: uid=replman,cn=config uid: replman givenName: replication objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson sn: manager cn: replication manager userPassword:: e1NTSEF9d1B3ZWJ2QzROTzZWZTlsRVNBYXNjU29SQlg1ajE1ZmZxUXlva1E9PQ= 5. Enable replication by checking "Enable Changelog" and "Use default" path for database directory 6. Enable replication agreement for "userRoot" with follow configuration: dn: cn=replica,cn=dc\3Dcentosvm,cn=mapping tree,cn=config objectClass: nsDS5Replica objectClass: top nsDS5ReplicaRoot: dc=centosvm nsDS5ReplicaType: 3 nsDS5Flags: 1 nsDS5ReplicaId: 1 nsds5ReplicaPurgeDelay: 604800 nsDS5ReplicaBindDN: uid=replman,cn=config cn: replica nsState:: AQAAAAAAAADdP5JMAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAA== nsDS5ReplicaName: 66dae382-c18011df-a9eeef1d-401e8cfe nsds5ReplicaChangeCount: 2 nsds5replicareapactive: 0 7. After configuration has passed successfully trying init it via "Initiate full re-syncronization" After that DS is crashing. Have you been able to reproduce this issue? Or do I need to provide more information? *** Bug 636682 has been marked as a duplicate of this bug. *** Created attachment 449061 [details]
0001-Bug-634561-Server-crushes-when-using-Windows-Sync.patch
Ok. I can confirm this patch fixes the issue. We may close this case. Tested with below steps: 1. Install DS packages via metapackage "389-ds" 2. Enable replication opportunities 3. Create replication agreement between AD and DS 4. Start "Initiate Full Re-syncronization" VERIFIED. |