[Date Prev][Date Next]
Re: question on syncprov
Sorry, I probably wasn't clear. One of the main reasons for this upgrade, was to get off RHEL5, and move to RHEL6, the updated openldap packages being more of a side effect.
I'm hoping I just missed something in the configuration, and that 2.4.23-20.el6.x86_6 (which looks to be the latest in RedHat's repo), will work, rather than build 2.4.31 from source. We use Puppet to manage as much as possible, and while we do have our own in house repo for custom packages, I'd want to have more of an idea that the distro provided rpms definitely won't work with replication before bothering to build one, though I can certainly test from ltb (though that thread mentions "excluding synrepl providers"?).
On Fri, May 25, 2012 at 3:00 PM, Nick Milas <firstname.lastname@example.org>
Can't tell you about the specific issue, but, as has been discussed numerous times in this list, avoid using the distro-provided RPMs, esp. if you are using replication.
On 25/5/2012 9:15 μμ, Steve Reveliotty wrote:
I'm trying to migrate from OpenLDAP 2.3.43-12.el5_6.7 to OpenLDAP 2.4.23-20.el6.x86_6.
Obviously you went from CentOS / RHEL 5 to CentOS / RHEL 6.
In any case, use a package with 2.4.31.
Copying from another thread:
From experience, I recommend using ready-made RPMs (or building
from SRPMs) rather than building from source. This way you can
upgrade at will and fully control your system in a way compatible
with RHEL/CentOS package practices.
Of those I have worked with, I would propose you try using Symas
Silver (excluding syncrepl providers - if you cannot afford paid
support - otherwise check gold), or full-featured LTB project's RPMs
(free, with on-line issue system). We use the latter.
For example, download the latest RPMs and install, e.g. here (for