I am experiencing unexpected results when converting the syncprov-checkpoint option in file-based configuration to the olcSpCheckpoint attribute in online configuration.
To reproduce the unexpected results:
1. Configure OpenLDAP using file-based configuration that contains the following line:
syncprov-checkpoint 100 10
2. Convert file-based configuration to online configuration using the following command:
slapd -f slapd.conf -F slapd.d
My file-based configuration is converted to the cn=config database, but after conversion the value of the olcSpCheckpoint attribute in the olcOverlay={1}syncprov,olcDatabase={1}bdb,cn=config entry is "100 600" when I expect it to be the same as in my file-based configuration ("100 10").
Is this a bug or does the olcSpCheckpoint attribute use different units (seconds) than the syncprov-checkpoint option (minutes)?
Kyle Blaney
--On Monday, November 09, 2009 11:00 AM -0500 Kyle Blaney kblaney@nortel.com wrote:
Is this a bug or does the olcSpCheckpoint attribute use different units (seconds) than the syncprov-checkpoint option (minutes)?
Always, always report which version you are using...
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Sorry, Quanah.
I'm using 2.4.15. I realize I'm not using the latest version, but the changes made since 2.4.15 do not indicate any submissions relevant to syncprov checkpointing.
Kyle Blaney
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: November 9, 2009 2:21 PM To: Blaney, Kyle (BVW:9T16); openldap-software@openldap.org Subject: Re: Bug when converting syncprov-checkpoint to olcSpCheckpoint?
--On Monday, November 09, 2009 11:00 AM -0500 Kyle Blaney kblaney@nortel.com wrote:
Is this a bug or does the olcSpCheckpoint attribute use different units (seconds) than the syncprov-checkpoint option (minutes)?
Always, always report which version you are using...
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
--On Monday, November 09, 2009 2:39 PM -0500 Kyle Blaney kblaney@nortel.com wrote:
Sorry, Quanah.
I'm using 2.4.15. I realize I'm not using the latest version, but the changes made since 2.4.15 do not indicate any submissions relevant to syncprov checkpointing.
Well, if you use the power of the source:
case SP_CHKPT: .... si->si_chktime *= 60; ....
I'd say yes, it is internally changed into seconds.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
--On Monday, November 09, 2009 1:05 PM -0800 Quanah Gibson-Mount quanah@zimbra.com wrote:
--On Monday, November 09, 2009 2:39 PM -0500 Kyle Blaney kblaney@nortel.com wrote:
Sorry, Quanah.
I'm using 2.4.15. I realize I'm not using the latest version, but the changes made since 2.4.15 do not indicate any submissions relevant to syncprov checkpointing.
Well, if you use the power of the source:
case SP_CHKPT:.... si->si_chktime *= 60; ....
I'd say yes, it is internally changed into seconds.
... And that this is a bug, because that means it'll do it again when it runs (600*60 in your case) when it goes to run.
I suggest you file an ITS at http://www.openldap.org/its/
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Is this a bug or does the olcSpCheckpoint attribute use different units (seconds) than the syncprov-checkpoint option (minutes)?
It's a bug. Please file an ITS http://www.openldap.org/its. Thanks, p.
"Kyle Blaney" kblaney@nortel.com writes:
I am experiencing unexpected results when converting the syncprov-checkpoint option in file-based configuration to the olcSpCheckpoint attribute in online configuration.
To reproduce the unexpected results:
- Configure OpenLDAP using file-based configuration that contains the
following line:
syncprov-checkpoint 100 10
- Convert file-based configuration to online configuration using the
following command:
slapd -f slapd.conf -F slapd.d
My file-based configuration is converted to the cn=config database, but after conversion the value of the olcSpCheckpoint attribute in the olcOverlay={1} syncprov,olcDatabase={1}bdb,cn=config entry is "100 600" when I expect it to be the same as in my file-based configuration ("100 10").
Is this a bug or does the olcSpCheckpoint attribute use different units (seconds) than the syncprov-checkpoint option (minutes)?
It seems that the slapo-syncprov(5) defines minutes, but the parser converts minutes into seconds. Im am on 2.4.19 and get similar results
,----[ syncprov.ldif ] | dn: olcOverlay={3}syncprov | objectClass: olcOverlayConfig | objectClass: olcSyncProvConfig | olcOverlay: {3}syncprov | olcSpCheckpoint: 5 300 | olcSpReloadHint: TRUE | structuralObjectClass: olcSyncProvConfig `----
,----[ slapd.conf ] | overlay syncprov | syncprov-reloadhint true | syncprov-checkpoint 5 5 `----
but I wouldn't consider it a bug.
-Dieter
Dieter Kluenter wrote:
"Kyle Blaney" kblaney@nortel.com writes:
I am experiencing unexpected results when converting the syncprov-checkpoint option in file-based configuration to the olcSpCheckpoint attribute in online configuration.
To reproduce the unexpected results:
- Configure OpenLDAP using file-based configuration that contains the
following line:
syncprov-checkpoint 100 10
- Convert file-based configuration to online configuration using the
following command:
slapd -f slapd.conf -F slapd.d
My file-based configuration is converted to the cn=config database, but after conversion the value of the olcSpCheckpoint attribute in the olcOverlay={1} syncprov,olcDatabase={1}bdb,cn=config entry is "100 600" when I expect it to be the same as in my file-based configuration ("100 10").
Is this a bug or does the olcSpCheckpoint attribute use different units (seconds) than the syncprov-checkpoint option (minutes)?
It seems that the slapo-syncprov(5) defines minutes, but the parser converts minutes into seconds. Im am on 2.4.19 and get similar results
The bug is confirmed. I wait for the ITS submission to commit the fix with the ITS number.
p.
Thanks Pierangelo! I've raised ITS#6370.
Kyle Blaney
-----Original Message----- From: openldap-software-bounces+kblaney=nortel.com@OpenLDAP.org [mailto:openldap-software-bounces+kblaney=nortel.com@OpenLDAP.org] On Behalf Of Pierangelo Masarati Sent: November 10, 2009 3:21 AM To: Dieter Kluenter Cc: openldap-software@openldap.org Subject: Re: Bug when converting syncprov-checkpoint to olcSpCheckpoint?
Dieter Kluenter wrote:
"Kyle Blaney" kblaney@nortel.com writes:
I am experiencing unexpected results when converting the syncprov-checkpoint option in file-based configuration to the olcSpCheckpoint attribute in online configuration.
To reproduce the unexpected results:
- Configure OpenLDAP using file-based configuration that contains
the following line:
syncprov-checkpoint 100 10
- Convert file-based configuration to online configuration using
the following command:
slapd -f slapd.conf -F slapd.d
My file-based configuration is converted to the cn=config database, but after conversion the value of the olcSpCheckpoint attribute in the olcOverlay={1} syncprov,olcDatabase={1}bdb,cn=config entry is "100 600" when I expect it to be the same as in my file-based
configuration ("100 10").
Is this a bug or does the olcSpCheckpoint attribute use different units (seconds) than the syncprov-checkpoint option (minutes)?
It seems that the slapo-syncprov(5) defines minutes, but the parser converts minutes into seconds. Im am on 2.4.19 and get similar results
The bug is confirmed. I wait for the ITS submission to commit the fix with the ITS number.
p.
openldap-software@openldap.org
-
Dieter Kluenter -
Kyle Blaney -
masarati＠aero.polimi.it -
Pierangelo Masarati
-
Quanah Gibson-Mount