[Date Prev][Date Next]
Re: slapd crashing
Alex Hebra wrote:
> # gdb /usr/local/libexec/slapd
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)...
> (gdb) run -h ldaps://10.138.138.216 <http://10.138.138.216> ldap://127.0.0.1 <http://127.0.0.1> ldaps://127.0.0.1 <http://127.0.0.1> -u ldap -g ldap
> Starting program: /usr/local/libexec/slapd -h ldaps://10.138.138.216 <http://10.138.138.216> ldap://127.0.0.1 <http://127.0.0.1> ldaps://127.0.0.1
> <http://127.0.0.1> -u ldap -g ldap
> (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...usage: /usr/local/libexec/slapd options
> Program exited with code 01.
> Current language: auto; currently minimal
> Am I missing something?
Apparently. Re-read the slapd(8) manpage for proper option syntax.
Also, if you had actually done what I said - attach to an already running slapd - you
wouldn't have had this problem. Following instructions is a pretty fundamental skill.
If you want to start under gdb you're also going to need a debug flag, otherwise it
will just fork/exit out from under you.
> On Thu, Jul 18, 2019 at 7:44 PM Howard Chu <email@example.com <mailto:firstname.lastname@example.org>> wrote:
> Alex Hebra wrote:
> > Hi there,
> > I've MMR running on two FreeBSD servers with OpenLDAP 2.4.47. After few days one node always crash with signal 11.
> > The last log I got from slapd is:
> > Jul 17 18:04:19 slapd: syncprov_matchops: skipping original sid 001
> > When I try to restart the slapd process it eats all the ram memory, until the server become irresponsible. I have to delete the database and re-sync
> > to make it works again.
> > Is there a way to find out how can I fix this issue?
> Attach to the running slapd with gdb and let it run, then examine the stack trace when it
> gets the SIGSEGV,
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/