I think you should now check dirsrv errors logs on both server and the replica.
It should have more info what went wrong with starting the replication.
Please also check
# systemctl status dirsrv@YOUR-REALM.service
to check there are no SASL buffer related error messages.
On 03/10/2015 12:58
On 03/09/2015 03:35 PM, Steven Jones wrote:
Any idea what is going on here please?
==
[root@vuwunicoipam004 mailto:root@vuwunicoipam004 ipa-certs]#
ipa-replica-install --setup-dns --forwarder=10.100.32.31 -U
replica-info-vuwunicoipam004.ods.vuw.ac.nz.gpg --skip-conncheck
Any idea what is going on here please?
==
[root@vuwunicoipam004mailto:root@vuwunicoipam004 ipa-certs]#
ipa-replica-install --setup-dns --forwarder=10.100.32.31 -U
replica-info-vuwunicoipam004.ods.vuw.ac.nz.gpg --skip-conncheck
Checking forwarders, please wait ...
WARNING: DNS
On 03/09/2015 05:35 PM, Steven Jones wrote:
Any idea what is going on here please?
==
[root@vuwunicoipam004 mailto:root@vuwunicoipam004 ipa-certs]#
ipa-replica-install --setup-dns --forwarder=10.100.32.31 -U
replica-info-vuwunicoipam004.ods.vuw.ac.nz.gpg --skip-conncheck
Why
It usually fails, hence I skip it.
Since I have no firewall either side and I know I have a simple network since I
built there is nothing possible blocking in-between.
I will double check the DNS zone file.
I had to rename the server to ipam004 as the replica attempt sulked if i
re-used an
==
2015-03-09T21:15:31Z DEBUG flushing ldap://vuwunicoipam002.ods.vuw.ac.nz:389
from SchemaCache
2015-03-09T21:15:31Z DEBUG retrieving schema for SchemaCache
url=ldap://vuwunicoipam002.ods.vuw.ac.nz:389
conn=ldap.ldapobject.SimpleLDAPObject instance at 0x4226cb0
2015-03-09T21:15:31Z DEBUG
=
Check connection from replica to remote master 'vuwunicoipam002.ods.vuw.ac.nz':
Directory Service: Unsecure port (389): OK
Directory Service: Secure port (636): OK
Kerberos KDC: TCP (88): OK
Kerberos Kpasswd: TCP (464): OK
HTTP Server: Unsecure port (80): OK
HTTP
