Re: Failed to send extended operation: LDAP error -1 (Can't contact LDAP server)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Well, I wouldn't reccomend manually importing ldifs from one server to another. So, you have servera (single master) -> serverb (consumer) and you want to add serverc in as a multimaster correct?

The way I would do that is make serverc a consumer off servera first and initialize it servera to get your data over. Next I would enable changelogs on serverc then change it to a multimaster from a consumer (as well as changing servera to a multimaster). Then setup a replication agreement form serverc to servera, and finally another replication agreement between serverc and serverb.

Once all is done you should have servera and serverc as masters with serverb as a consumer.

I've basically gone through this process a couple times in my own enviroment and it seems to work well. I have also seen very.. odd behavior when I manually export/import an LDIF from another server.


On Sun, May 4, 2014 at 11:17 AM, Graham Leggett <minfrin@xxxxxxxx> wrote:
On 04 May 2014, at 7:57 PM, Dustin Rice <dustin@xxxxxxx> wrote:

> Oh sure, just the way it was worded I wasn't sure if you were seeing successful SSL connections or just "lots of SSL traffic", which can still be handshake failures.
>
> Can you successfully perform ldapsearches from serverb to serverc over 636?

Yes.

Weirdly, serverc returns a referral to serverb and servera, which is unexpected:

/usr/bin/ldapsearch -x -H ldaps://serverc.example.com:636 -D "cn=Directory Manager" -W -b "o=Foo,c=ZA" "(objectclass=*)"
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base <o=Foo,c=ZA> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#

# search result
search: 2
result: 10 Referral
matchedDN: o=Foo,c=za
ref: ldap://serverb.example.com:389/o%3DFoo%2Cc%3Dza
ref: ldap://servera.example.com:389/o%3DFoo%2Cc%3Dza

# numResponses: 1

serverc contains a manually imported copy of the ldif from servera.

Regards,
Graham
--

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users

[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux