41720 sendto(3, "<165>Aug 27 15:36:40 slapd[41718]: ppm: entry
uid=kmart,ou=people,dc=lecpq,dc=com", 87, MSG_NOSIGNAL, NULL, 0) = 87
41720 getpid() = 41718
41720 sendto(3, "<165>Aug 27 15:36:40 slapd[41718]: ppm: Reading
pwdCheckModuleArg attribute", 75, MSG_NOSIGNAL, NULL, 0) = 75
41720 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x8} ---
41718 <... futex resumed>) = ?
41720 +++ killed by SIGSEGV +++
41719 <... epoll_wait resumed> <unfinished ...>) = ?
41719 +++ killed by SIGSEGV +++
41718 +++ killed by SIGSEGV +++
still now coredump file. I'll try changing the kernel.core_pattern and see
if we get something somewhere.
---
Regards,
Kevin Martin
On Fri, Aug 27, 2021 at 10:37 AM kevin martin <[email protected]> wrote:
> Well, I now know WHAT caused the coredump; a passwd change request. and I
> was stracing the slapd process while it happened so I have that as well.
>
>
> ---
>
>
> Regards,
>
> Kevin Martin
>
>
> On Fri, Aug 27, 2021 at 10:33 AM Maucci, Cyrille <[email protected]>
> wrote:
>
>> Definitely core dumps are hooked to system-coredump.
>>
>> I don’t know this subsystem but I’m sure google knows.
>>
>> If I was like you, facing such a situation an unable to figure out where
>> system-coredump throws the thing, I’d change kernel.core_pattern to a good
>> old core.%p and have the core being reproduced.
>>
>>
>>
>> *From:* kevin martin [mailto:[email protected]]
>> *Sent:* Friday, August 27, 2021 5:28 PM
>> *To:* Maucci, Cyrille <[email protected]>
>> *Cc:* [email protected]
>> *Subject:* Re: OpenLDAP 2.5.7 dies
>>
>>
>>
>> Sorry, didn't finish:
>>
>>
>>
>> kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t
>> %c %h %e
>>
>>
>>
>> yet no coredump under systemd/coredump...
>>
>> ---
>>
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Kevin Martin
>>
>>
>>
>>
>>
>> On Fri, Aug 27, 2021 at 10:27 AM kevin martin <[email protected]> wrote:
>>
>> on systems that are RHEL 8 or equivalent, isn't systemd-coredump used if
>> kernel.core_pattern is set as such (thereby not needing abrt) or am I
>> mistaken? my ulimit -c says unlimited and my sysctl setting is:
>>
>> ---
>>
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Kevin Martin
>>
>>
>>
>>
>>
>> On Fri, Aug 27, 2021 at 10:20 AM Maucci, Cyrille <[email protected]>
>> wrote:
>>
>> Linux basics…
>>
>>
>>
>> Check kernel.core_pattern using sysctl -a
>>
>> Check ulimit -c
>>
>> Check if you have abrt installed..
>>
>>
>>
>> ++Cyrille
>>
>>
>>
>> *From:* kevin martin [mailto:[email protected]]
>> *Sent:* Friday, August 27, 2021 5:16 PM
>> *To:* Maucci, Cyrille <[email protected]>
>> *Cc:* [email protected]
>> *Subject:* Re: OpenLDAP 2.5.7 dies
>>
>>
>>
>> hmm, where might the core dump be?
>>
>>
>> ---
>>
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Kevin Martin
>>
>>
>>
>>
>>
>> On Fri, Aug 27, 2021 at 10:03 AM Maucci, Cyrille <[email protected]>
>> wrote:
>>
>> Grab the core dump and extract the stack traces ?
>>
>>
>>
>> *From:* kevin martin [mailto:[email protected]]
>> *Sent:* Friday, August 27, 2021 5:01 PM
>> *To:* [email protected]
>> *Subject:* OpenLDAP 2.5.7 dies
>>
>>
>>
>> Aug 27 14:25:38 newldap0.mgt.ch3.bmi slapd[38335]: ppm: Reading
>> pwdCheckModuleArg attribute
>> Aug 27 14:25:38 newldap0.mgt.ch3.bmi systemd[1]: slapd.service: Main
>> process exited, code=killed, status=11/SEGV
>> Aug 27 14:25:38 newldap0.mgt.ch3.bmi systemd[1]: slapd.service: Failed
>> with result 'signal'.
>>
>>
>>
>> is this a known issue? Oracle Linux 8. what can I do to help determine
>> what occurred?
>>
>>
>>
>> ---
>>
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Kevin Martin
>>
>>
