OK. Thanks. we just use the RPM package from OEL8. Do you know if 2.6 RPM is available on OEL8?
On Fri, Jun 21, 2024 at 1:06 PM Quanah Gibson-Mount quanah@fast-mail.org wrote:
--On Friday, June 21, 2024 1:35 PM -0400 "Luo, Frank" luoy@miamioh.edu wrote:
sorry. it is 2.4.46 and I believe it is standard syncrepl ( I could not find syncdata in slapd.conf).
Hi,
The OpenLDAP 2.4 series has been deprecated for several years, and numerous issues with replication have been fixed in the later release series. I would strongly advise upgrading to a supported release, in particular the OpenLDAP 2.6 series. You've most likely encountered one of the many known and (later) fixed issues with syncrepl in the 2.4 series.
Regards, Quanah
--On Friday, June 21, 2024 2:12 PM -0400 "Luo, Frank" luoy@miamioh.edu wrote:
OK. Thanks. we just use the RPM package from OEL8. Do you know if 2.6 RPM is available on OEL8?
I would suggest using one of the freely provided binaries from either Symas or the LTB project. The Symas packages can optionally come with support.
https://repo.symas.com/soldap/rhel8/ https://ltb-project.org/
Regardless of which you choose, you may want to read over https://repo.symas.com/soldap/upgrading/ and related documentation, since there can be some changes needed when going from 2.4 to later release series.
Regards, Quanah
Hello,
May I ask why you suggested 2.5 series over 2.6? I thought that the 2.5 branch was for long term support while the 2.6 branch was more for development and new features (and that a feature present in the 2.6 branch could be removed at any time)
So, I thought that the 2.5 series is more stable and adapted for a production environment.
Thanks
__________________________________________ Steeve Gagnon Analyste des systèmes Infrastructure des serveurs Service des technologies de l'information Université de Sherbrooke Tél. : 819-821-8000 poste 62495 USherbrooke.ca/sti
-----Message d'origine----- De : Quanah Gibson-Mount quanah@fast-mail.org Envoyé : 21 juin 2024 13:23 À : Luo, Frank luoy@miamioh.edu Cc : openldap-technical openldap-technical@openldap.org Objet : Re: sync repl issue
--On Friday, June 21, 2024 2:12 PM -0400 "Luo, Frank" luoy@miamioh.edu wrote:
OK. Thanks. we just use the RPM package from OEL8. Do you know if 2.6 RPM is available on OEL8?
I would suggest using one of the freely provided binaries from either Symas or the LTB project. The Symas packages can optionally come with support.
https://repo.symas.com/soldap/rhel8/ https://ltb-project.org/
Regardless of which you choose, you may want to read over https://repo.symas.com/soldap/upgrading/ and related documentation, since there can be some changes needed when going from 2.4 to later release series.
Regards, Quanah
--On Wednesday, June 26, 2024 8:21 PM +0000 Steeve Gagnon Steeve.Gagnon@USherbrooke.ca wrote:
Hello,
May I ask why you suggested 2.5 series over 2.6? I thought that the 2.5 branch was for long term support while the 2.6 branch was more for development and new features (and that a feature present in the 2.6 branch could be removed at any time)
So, I thought that the 2.5 series is more stable and adapted for a production environment.
I think you mean, why do I suggest 2.6 over 2.5? It's been out several years, the core functions are solid. 2.5 had many fixes to replication, 2.6 has further fixes. I've run 2.6 in production for over 2 years, making use of some of the newer features (file based logging for example).
--Quanah
On 6/26/24 15:52, Quanah Gibson-Mount wrote:
I think you mean, why do I suggest 2.6 over 2.5? It's been out several years, the core functions are solid. 2.5 had many fixes to replication, 2.6 has further fixes. I've run 2.6 in production for over 2 years, making use of some of the newer features (file based logging for example).
Is there any chance that something new will be added to a future version of 2.6 that might cause problems? It would seem that since 2.5 is the official LTS Release according to https://www.openldap.org/software/download/, that the project would not add any new features to 2.5, thus reducing the risk than a new version would cause problems or unexpected changes in behavior. Whereas, since 2.6 is the official "Feature Release", that a new feature might be added to 2.6 that could produce an undesirable outcome in someone's production environment?
Thanks,
--On Wednesday, June 26, 2024 5:29 PM -0700 Christopher Paul chris.paul@rexconsulting.net wrote:
On 6/26/24 15:52, Quanah Gibson-Mount wrote:
I think you mean, why do I suggest 2.6 over 2.5? It's been out several years, the core functions are solid. 2.5 had many fixes to replication, 2.6 has further fixes. I've run 2.6 in production for over 2 years, making use of some of the newer features (file based logging for example).
Is there any chance that something new will be added to a future version of 2.6 that might cause problems? It would seem that since 2.5 is the official LTS Release according to https://www.openldap.org/software/download/, that the project would not add any new features to 2.5, thus reducing the risk than a new version would cause problems or unexpected changes in behavior. Whereas, since 2.6 is the official "Feature Release", that a new feature might be added to 2.6 that could produce an undesirable outcome in someone's production environment?
New features have to be enabled, so if you don't enable it, how would it affect things? For example, the recent work on the memberOf overlay to work with replication still requires a flag to do the behavior change.
We also of course have a test suite to ensure core functionality is not affected by changes (new features or not).
--Quanah
openldap-technical@openldap.org