Closed abbra closed 2 weeks ago
coredump: 45732.core.tar.gz
This is Fedora 40, 389-ds-base-3.0.4-3.fc40.x86_64
According to the stack trace no threads are executing some code that generates SIGABRT signal: the only active thread is writing a message in error log (and more exactly: flushing that message to the disk) slapi_log_err(SLAPI_LOG_REPL, buf->buf_agmt_name, "clcache_skip_change - Skipping %s because the consumer with Rid: [%d] is ignored\n", buf_cur_csn_str, rid); and buf->buf_agmt_name and buf_cur_csn_str are both valid strings and there is nor reason that the error message fails.
So at this point, everything looks like ns-slpad process was killed by an external signal (maybe too much memory was consumed on the VM and something decided to kill some processes ?)
On Wed, Oct 30, 2024 at 11:01 AM Alexander Bokovoy @.***> wrote:
This is Fedora 40, 389-ds-base-3.0.4-3.fc40.x86_64
— Reply to this email directly, view it on GitHub https://github.com/389ds/389-ds-base/issues/6389#issuecomment-2446400576, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARLA4LKN55KXEK2Q5W5NEG3Z6CU5RAVCNFSM6AAAAABQ3W2UZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBWGQYDANJXGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
389 Directory Server Development Team
SIGABRT can occur during failed memory allocation, so I would agree with @progier389 that freeipa is simply consuming too much memory.
Thank you. It is most likely the case. The VM in question has 6GB RAM and some swap space, we run multiple containers in parallel there and they might cause memory exhaustion. It is a good test bed to imitate high memory pressure in CI tasks, so I'll keep reporting individual issues in future.
I'm closing this one as it appears to be non-actionable here.
so I'll keep reporting individual issues in future.
I don't see the value in this. If you're running a machine to OOM, there is no bug in 389-ds. We can't allocate memory, when there is no memory to allocate. This is to say nothing of how memory overcommit works and how memory allocations only fail on first write, not on allocate.
If your intent is to "reduce the ram usage of freeipa" then there are more productive ways to go about this without reporting bugs like this.
EDIT: In the interest of clarity, I am saying "do not report bugs that are caused by OOM because you are wasting everyone's collective time".
FreeIPA upstream tests encountered a crash in clcache_skip_change:
45732.stacktrace.txt