RE: ./scripts/test008-concurrency failure - Tru64 5.1 (ITS#2489)

[hyc@highlandsun.com]

> -----Original Message-----
> From: owner-openldap-bugs@OpenLDAP.org
> [mailto:owner-openldap-bugs@OpenLDAP.org]On Behalf Of douglas@gpc.edu

> Full_Name: Douglas Jones
> Version: 2.1.17
> OS: Tru64 5.1
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (168.28.200.208)

> Where should I look to find a core or debugging logs so that
> I can track
> more of thi sdown. I could look for this, but I imagine it will take
> a while to go though all and find where this is happenning and I was
> hoping maybe someone has already been through this. It
> appears the LDAP
> server is dieing or something....
>
> Here is the relavent output from the test:
>
> >>>>> Starting test008-concurrency ...
> running defines.sh
> Datadir is ./data
> Cleaning up in ./test-db...
> Running slapadd to build slapd database...
> Waiting 5 seconds for slapadd to build slapd database...
> Starting slapd on TCP/IP port 9009...
> Using ldapsearch to check that slapd is running...
> Waiting 5 seconds for slapd to start...
> Using tester for concurrent server access...

The easiest thing to do is to attach a debugger to the running server; core
files tend to be corrupted already by the time they're written so they don't
always point to the right problem spot.

Run test008 manually with the following command; it will print the PID of the
slapd that it starts and then wait for you to hit Return before continuing.
Run a debugger in a separate terminal session and attach it to the slapd
process. Give a "continue" command to get the slapd running again, and then
press return on the test008 script:
	sh scripts/test008-concurrency . bdb no 1

(Assuming you're testing the back-bdb backend) When the process dies, get a
backtrace...

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