RE: slapd exiting with signal 6 and out of locker entries (ITS#2678)

[jsaint-rossy@associates.usss.treas.gov]

Thanks, that was it.  All my slaves are now running smoothly.  I've
updated the FAQ-O-Matic with this answer.

However, seems odd that this should cause slapd to die.  

-----Original Message-----
From: Howard Chu [mailto:hyc@highlandsun.com] 
Sent: Monday, September 15, 2003 3:32 PM
To: jsaint-rossy@associates.usss.treas.gov; openldap-its@OpenLDAP.org
Subject: RE: slapd exiting with signal 6 and out of locker entries
(ITS#2678)

It appears that someone is attempting to issue a MODIFY_PASSWORD
extended
operation to this slave. The result is a Referral error, since only the
master can perform write operations. Signal 6 is an Abort, which is
caused by
an assert() error which is triggered whenever an illegal/unexpected
state is
detected in the code. In this case, the assert() will fail if a Referral
error is returned with the actual referral being NULL/missing. It seems
you
don't have a proper updateref configured in slapd.conf.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of
> jsaint-rossy@associates.usss.treas.gov

> Using "-d 7" here is the ldas output before slapd terminated
> with signal 6.
>
> > ldap_read: want=8 error=Resource temporarily unavailable
> > ber_get_next on fd 19 failed errno=35 (Resource temporarily
> unavailable)
> > do_extended
> > ber_scanf fmt ({m) ber:
> > ber_scanf fmt (m) ber:
> > do_extended: oid=1.3.6.1.4.1.4203.1.11.1
> > send_ldap_extended: err=10 oid= len=0
> > send_ldap_response: msgid=2 tag=120 err=10
> > assertion "err != LDAP_REFERRAL" failed: file "result.c", line 300
> > Abort trap