On 12/13/2018 1:37 PM, Jan Kowalsky wrote:
Well, we just added a new database on runtime which worked fine - 389ds was still running. After changing a replica I wanted to restart and resulted in the error.
Also try turning up the logging verbosity to the max. From memory the
How can I achive this? In dse.ldif I have:
nsslapd-errorlog-level: 32768
The details are here : https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/8.2/h... but I'd try 65535. That will get you everything useful, I think.
I don't assume - since it worked all the time... What I could imagine is that cangelogdb files had been smaller last reboot - so any memory limit didn't took effect.
It could be something like : the VM host changed (guest may have been migrated live) such that the physical memory is much larger. This combined with situation I mentioned earlier where the cache size is computed from the host physical memory not the guest might explain the symptoms. I'd definitely look at a) cache auto size (should be printed in the log somewhere, and you can just disable it by configuring fixed size caches that are appropriate in size) and b) strace the process to see why it is failing -- for example you may see an sbrk() call for a zillion bytes or an mmap() call for a huge region, that fails. I think strace might have an option to log only failing syscalls.