> On 9 Feb 2019, at 07:39, Zarko D wrote:
>
>> This doesn’t exactly sound like a sustainable situation …
>
> Yes, beside replica failing, I also can't do any work on this server, add
> user/host fails, but at least I have a RO server with all updates.
:S not a great situation.
>
>>
> This doesn’t exactly sound like a sustainable situation …
Yes, beside replica failing, I also can't do any work on this server, add
user/host fails, but at least I have a RO server with all updates.
> rreplication logging by setting the nsslapd-errorlog-level to 8192 which
> could
This
> On 5 Feb 2019, at 09:00, Zarko D wrote:
>
> Correct, I've run the command:
>
> ipa-replica-manage -v re-initialize --from=
>
> ... it completed successfully. The remaining problem is that this 'fixed'
> server doesn't get updates from another master, the error is :
> "Error (16) :
Correct, I've run the command:
ipa-replica-manage -v re-initialize --from=
... it completed successfully. The remaining problem is that this 'fixed'
server doesn't get updates from another master, the error is :
"Error (16) : Incremental update connection error. Backing off, will retry
> On 5 Feb 2019, at 04:50, Zarko D wrote:
>
> William, I've tried restoring key3.db, cert8.db and secmod.db but it didn't
> help.
> Since IPA server is a VM, I was able to try different things on VM's clone,
> and fortunately (with the luck) I fixed the problem.
> Basically I tried
William, I've tried restoring key3.db, cert8.db and secmod.db but it didn't
help.
Since IPA server is a VM, I was able to try different things on VM's clone, and
fortunately (with the luck) I fixed the problem.
Basically I tried different daily backups that I have, and with one of them,
after
> On 4 Feb 2019, at 17:07, Zarko D wrote:
>
> Thanks for reply William, I believe I restored db with command "ipa-restore
> -d --data /path/ipa-data-2018-12-30-20-12-00" but 389ds still fails to start .
>
>
> ns-slapd[3533]: [03/Feb/2019:22:55:04.336762406 -0800] attrcrypt - All
>
Thanks for reply William, I believe I restored db with command "ipa-restore -d
--data /path/ipa-data-2018-12-30-20-12-00" but 389ds still fails to start .
Restore final logs are:
[03/Feb/2019:22:49:54.229404539 -0800] import ipaca: Closing files...
[03/Feb/2019:22:50:21.082241726 -0800] All
> [02/Feb/2019:22:47:37.921288555 -0800] WARNING: userRoot: entry cache size
> 10485760 B is less than db size 16932864 B; We recommend to increase the
> entry cache size nsslapd-cachememsize.
> [02/Feb/2019:22:47:37.921943984 -0800] WARNING: ipaca: entry cache size
> 10485760 B is less than
