On 19.8.2016 16:13, Tiemen Ruiten wrote:
> I did actually use a local dse.ldif in the end, but I forgot to stop dirsrv
> while replacing it, so maybe the nsslapd-localhost line got updated by the
> running dirsrv?
Yes, that is possible. dirsrv can write to dse.ldif at run-time.
>
> On 19 August
I did actually use a local dse.ldif in the end, but I forgot to stop dirsrv
while replacing it, so maybe the nsslapd-localhost line got updated by the
running dirsrv?
On 19 August 2016 at 15:59, Petr Spacek wrote:
> On 19.8.2016 15:26, Tiemen Ruiten wrote:
> > Managed to fix it: had to stop dirs
On 19.8.2016 15:26, Tiemen Ruiten wrote:
> Managed to fix it: had to stop dirsrv@IPA-RDMEDIA-COM and put the server's
> hostname on the line with nsslapd-localhost
Uh, this is quite brutal. There might be some other server-specific options.
If you can dig up older dse.ldif from the same server, I
Managed to fix it: had to stop dirsrv@IPA-RDMEDIA-COM and put the server's
hostname on the line with nsslapd-localhost
Then run ipa-replica-manage re-initialize --from
other-master.ipa.rdmedia.com
On 19 August 2016 at 12:14, Tiemen Ruiten wrote:
> I see lots of messages /var/log/dirsrv/slapd-IP
I see lots of messages /var/log/dirsrv/slapd-IPA-RDMEDIA-COM/errors, looks
definitely like an issue with dirsrv.
On 19 August 2016 at 11:43, Tiemen Ruiten wrote:
> I see I didn't use the right terminology: all four of my FreeIPA servers
> are masters.
>
> On 19 August 2016 at 11:36, Tiemen Ruite
I see I didn't use the right terminology: all four of my FreeIPA servers
are masters.
On 19 August 2016 at 11:36, Tiemen Ruiten wrote:
> Hello,
>
> I need some help getting one of my replica's to work. Assistance would be
> much appreciated.
>
> After the iSCSI volumes of two replicas of were br
Hello,
I need some help getting one of my replica's to work. Assistance would be
much appreciated.
After the iSCSI volumes of two replicas of were briefly unavailable, on one
of them DNS and LDAP stopped working and replication seems to have stopped.
The ipa service failed with a message that an