Lukas
Perhaps I should explain the design a bit and see if FreeIPA even supports
this.Our replica is in a separate network and all the appropriate ports are
opened between the master and the replica. The "replica" got created
successfully and is in sync with the master (except the CA services wh
Dave Jablonski wrote:
FreeIPA Server: Fedora 16, freeipa 2.1.4
Latest CentOS 6.5 client
When running:
ipa-client-install --mkhomedir --enable-dns-updates
The install fails with:
trying https:///ipa/xml
Forwarding 'env' to server u'https:///ipa/xml'
Traceback (most recent call last):
File
Even though I already have a ntp server, I setup my newly
created freeipa kdc to do that too (it is a slave to my primary ntp).
I then build a centos host to be the test client. Just to make sure it
can see and use auth's ntp, I tested with ntpdate:
[root@centos64 ~]# ntpdate auth
8 Feb 08
On (06/02/14 18:33), Shree wrote:
>First of all, the ipa-replica-install did not allow me to use the --setup-ca
> option complaining that a cert already exists, replicate creation was
> successful after I skipped the option.
>Seems like the replica is one except
>1) There is no CA Service running
