Hi, Thanks for the reply. I have a rootdn,How to query the updateref setting ?
waiting for your inputs
Regards, Pramod
On Sat, Aug 24, 2013 at 12:51 AM, Quanah Gibson-Mount quanah@zimbra.comwrote:
--On Friday, August 23, 2013 3:53 PM +0530 pramod kulkarni < pammu.kulkarni@gmail.com> wrote:
I am trying to notify a system to check if the openLDAP server is provider or consumer.I can do this by getting a referral error on the consumer side whenever I try to write something on the server , but is their any other way to check if OpenLDAP is provider or consumer without writing to it ? .
You could query for the updateref setting if you are using cn=config out of the config DB, but that'd require the rootdn? Or, you could just set up slapo-chain on your replica, and then it doesn't matter.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
Hi!
I have a related question: How is the updateref expected to be for a multi-master server with replicated config database? None, one, or one for each server?
Regards, Ulrich
pramod kulkarni pammu.kulkarni@gmail.com schrieb am 26.08.2013 um 07:46 in
Nachricht CANyT8D=MrpVDvRQdZ8FZcj0Oa=EHbZfdYfLcq_skhy5=HUMipw@mail.gmail.com:
Hi, Thanks for the reply. I have a rootdn,How to query the updateref setting ?
waiting for your inputs
Regards, Pramod
On Sat, Aug 24, 2013 at 12:51 AM, Quanah Gibson-Mount quanah@zimbra.comwrote:
--On Friday, August 23, 2013 3:53 PM +0530 pramod kulkarni < pammu.kulkarni@gmail.com> wrote:
I am trying to notify a system to check if the openLDAP server is provider or consumer.I can do this by getting a referral error on the consumer side whenever I try to write something on the server , but is their any other way to check if OpenLDAP is provider or consumer without writing to it ? .
You could query for the updateref setting if you are using cn=config out of the config DB, but that'd require the rootdn? Or, you could just set up slapo-chain on your replica, and then it doesn't matter.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
--On Monday, August 26, 2013 4:16 PM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi!
I have a related question: How is the updateref expected to be for a multi-master server with replicated config database? None, one, or one for each server?
Why would a master have an updateref statement? Then it wouldn't be a master.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
Quanah Gibson-Mount quanah@zimbra.com schrieb am 26.08.2013 um 17:21 in
Nachricht <564FB11DDFEE88059AA204C7@[192.168.1.22]>:
--On Monday, August 26, 2013 4:16 PM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi!
I have a related question: How is the updateref expected to be for a multi-master server with replicated config database? None, one, or one for each server?
Why would a master have an updateref statement? Then it wouldn't be a master.
I haven't fully investigated, but in SLES11 SP2 YaST seems to refuse updates (users and groups) on multi-master if either "mirrormode: true" is missing, or "updateref". It's a bug in YaST, yes, but I have to live with it. I could do updates with LDIF, but other people want to use YaST...
BTW, the manpage says: --- updateref <url> Specify the referral to pass back when slapd(8) is asked to modify a replicated local database. If specified multiple times, each url is provided. ---
So one could guess you'll have to specify all your masters using updateref...
Maybe the clarification would be to state that "replicated" means "slave copy". Also on "local": Can slapd modify and database that is not local?
Regards, Ulrich
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
--On Tuesday, August 27, 2013 8:06 AM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Quanah Gibson-Mount quanah@zimbra.com schrieb am 26.08.2013 um 17:21 in
Nachricht <564FB11DDFEE88059AA204C7@[192.168.1.22]>:
--On Monday, August 26, 2013 4:16 PM +0200 Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de wrote:
Hi!
I have a related question: How is the updateref expected to be for a multi-master server with replicated config database? None, one, or one for each server?
Why would a master have an updateref statement? Then it wouldn't be a master.
I haven't fully investigated, but in SLES11 SP2 YaST seems to refuse updates (users and groups) on multi-master if either "mirrormode: true" is missing, or "updateref". It's a bug in YaST, yes, but I have to live with it. I could do updates with LDIF, but other people want to use YaST...
Sounds like there is something seriously broken with YaST. How does it talk to a regular master if it doesn't have updateref incorrectly set? I.e., how does it "know" the difference between a single or multi-master configuration?
In any case, I always advise avoiding SLES. They can't release SP's without breaking backwards compatibility. SP2 broke SP1 backwards compat. SP3 breaks SP2 backwards compat. It's insane. How that can be considered "enterprise" is beyond me.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
--On Monday, August 26, 2013 11:16 AM +0530 pramod kulkarni pammu.kulkarni@gmail.com wrote:
Hi, Thanks for the reply. I have a rootdn,How to query the updateref setting ?
waiting for your inputs
If you use cn=config, you can search for olcUpdateRef being set. Again, it would be simpler to set up slapo-chain, or MMR and get rid of replicas entirely.
--Quanah
--
Quanah Gibson-Mount Lead Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org
-
pramod kulkarni -
Quanah Gibson-Mount -
Ulrich Windl