Re: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue
[Date Prev][Date Next] [Thread Prev][Thread Next]Re: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue
- From: "Trent W. Buck" <twb [at] cyber.com.au>
- To: Kokila Koks <kokilavaradhan [at] gmail.com>
- Cc: nss-pam-ldapd-users [at] lists.arthurdejong.org
- Subject: Re: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue
- Date: Mon, 25 May 2026 14:11:32 +1000
What does "sudo coredumpctl info nslcd" (or similar) say it was doing when it dumped core? You may need to install a -dbgsym package (or https://wiki.debian.org/Debuginfod + ExecStart=gdb nslcd) to get useful symbol names.
On 25/5/26 13:54, Kokila Koks wrote:
I'm experiencing reproducible core dumps with nslcd 0.9.8 when stopping the service.Issue: nslcd[945]: caught signal SIGTERM (15), shutting down nslcd[945]: thread 0 is still running, shutting down anyway systemd: nslcd.service: Main process exited, code=dumped, status=6/ABRT Reproduction: systemctl stop nslcd.service Core dump occurs every time Environment: nslcd 0.9.8, Linux/systemd Questions: Is this a known issue in 0.9.8? Fixed in newer versions? Any workarounds or config recommendations?The service restarts fine, but generates core dumps on every stop operation.
- nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue,
Kokila Koks
- Re: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue, Trent W. Buck
- Prev by Date: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue
- Next by Date: Re: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue
- Previous by thread: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue
- Next by thread: Re: nslcd 0.9.8 Core Dump (SIGABRT) on Service Stop - Thread Cleanup Issue