search for: refreshandpersist

...(2.3) as a slave. This is relevant part of my slapd.conf on LDAP 2.3: # syncrepl directives syncrepl rid=101 provider=ldap://192.168.1.86 bindmethod=simple binddn="uid=zimbra,cn=admins,cn=zimbra" credentials=PASSword searchbase="dc=company,dc=com" schemachecking=on type=refreshAndPersist retry="60 +" syncdata=accesslog # Refer updates to the master updateref ldap://192.168.1.86 Replication works OK, when I first start LDAP, it populates automatically. But after that initial data, it just doesn't pull anything anymore. I have to restart it, or it won't pull dat...

...prov-sessionlog 100 LDAP Server mirror moduleload syncprov syncrepl rid=001 provider=ldap://ldap.domain.com:389 bindmethod=simple binddn="cn=admin,dc=domain,dc=com" credentials=<password> searchbase="dc=domain,dc=com" schemachecking=off type=refreshAndPersist retry="60 +" mirrormode on when i've configured like above then i restart ldap service the service cannot start and when i check on my /usr/lib/openldap/modules i can't find module with the name syncprov. Is there any clue about this...

...From what I gather, OpenLDAP on Centos 5.x pulls LDAP changes from central LDAP server to a secondary LDAP server. So in other words, you can have your second LDAP server pull the db based on either; type=refreshOnly which mean the pull interval will happen when ever you specify or; type=refreshAndPersist which mean after a pull, keep the pipe open for any changes made. Now in Ubuntu one can have there primary LDAP push the changes to all the secondaries. Can I somehow enable push in Centos OpenLDAP because pull seems pretty lame in this case. I tried but to no avail. Hope the answer isn...

...es between the our PDC and BDC LDAP servers. Here are the details Servers: Name: LIN-PDC1.LIN Role: PDC SLAPD: openldap-2.4.28 Samba: 3.6.25 Name: LIN-PDC2.LIN Role: BDC SLAPD: 2.4.31 Samba: 4.3.11 LDAP Method: cn=config with smbldap tools Database: HDB Management: PHPLAMDIN Replication Method: refreshAndPersist Replication: After importing the LDIFs for Provider and consumer, we found that the in the PDC the oldDatabase(1)HDB was converted from a file to a folder. The contents of the which are below. In BDC it remained a file. BDC: LDAP sync related bits from olCDatabase(1)HDB olcSyncrepl: {0}rid=0...

...grate from slurpd to syncrepl. And so far everything is working fine in my test environments. This is what I have configured on the master: overlay syncprov syncprov-checkpoint 1 10 syncprov-sessionlog 100 And on the slave: syncrepl rid=1 provider=ldap://ldap1.mydomain.com type=refreshAndPersist searchbase="dc=mydomain,dc=com" schemachecking=off bindmethod=simple binddn="cn=Manager,dc=mydomain,dc=com" credentials=xxxxxxxxxxx updateref ldap://ldap1.mydomain.com/ It works with queries, and when I do an update on the master, it re...

Hi Guys, We're trying to add a BDC in Samb4 classic domain setup. The Samba 3 How -To and Samb3 by Example covers this but uses the old slapd.conf option, we are using the slapd.d config. I couldn't find a similar document for Samba4 Can you please advise that the following steps will work? LDAP in the existing PDC is working using the smbldap tools - Setup the LDAP in BDC

Hello, I have a PDC with master ldap backend and a BDC with slave ldap backend (both are SaMBa 3.2 on Debian Lenny). I want to install an additional SaMBa server on an another site (on Debian Squeeze). The two sites is connected with VPN (on not so reliable ADSL lines). I read an interesting network scenario in the Samba Guide chapter 6: theoretically it is possible to install one PDC on both