Re: RE24 testing call #3 (OL 2.4.24)

[Dieter Kluenter <dieter@dkluenter.de>]

Am Sat, 15 Jan 2011 18:01:31 +0100 (CET)
schrieb masarati@aero.polimi.it:

> > Am Fri, 14 Jan 2011 12:38:31 -0800
> > schrieb Quanah Gibson-Mount <quanah@zimbra.com>:
> >
> >> --On Friday, January 14, 2011 6:25 PM +0100 Dieter Kluenter
> >> <dieter@dkluenter.de> wrote:
> >>
> >> > Am Thu, 13 Jan 2011 12:08:23 -0800
> >> > schrieb Quanah Gibson-Mount <quanah@zimbra.com>:
> >> >
> >> >> Fixes to the dreaded solaris hang with back-monitor included.
> >> >> Please test. :)
> >> >
> >> > ./scripts/test020-proxycache failed for hdb (exit 255)
> >> > make: *** [hdb-yes] Fehler 255
> >>
> >> While I appreciate you taking the time to test, this report
> >> provides no useful information.  Please provide some data that can
> >> actually be examined for issues.
> >
> > This submisssion was unintentional and too early, sorry
> >
> >>>>>> Starting test020-proxycache for hdb...
> > Starting master slapd on TCP/IP port 9011...
> > Using ldapsearch to check that master slapd is running...
> > Using ldapadd to populate the master directory...
> > Starting proxy cache on TCP/IP port 9012...
> > Using ldapsearch to check that proxy slapd is running...
> > Waiting 5 seconds for slapd to start...
> > Waiting 5 seconds for slapd to start...
> > Waiting 5 seconds for slapd to start...
> > Waiting 5 seconds for slapd to start...
> > Waiting 5 seconds for slapd to start...
> > Waiting 5 seconds for slapd to start...
> > ldapsearch failed (255)!
> >>>>>> ./scripts/test020-proxycache failed for hdb (exit 255)
> > make: *** [hdb-yes] Fehler 255
> >
> > slapd.2.log doesn't show much, the last lines where
> >
> > put_filter: simple
> > put_simple_filter:
> > "namingContexts:distinguishedNameMatch:=dc=example,dc=com"
> > ber_scanf fmt ({mm}) ber:
> > ber_scanf fmt ({mm}) ber:
> > ber_scanf fmt ({t) ber:
> > ber_scanf fmt (m) ber:
> > ber_scanf fmt (t) ber:
> > ber_scanf fmt (m) ber:
> > ber_scanf fmt (t) ber:
> > ber_scanf fmt (m) ber:
> > ber_scanf fmt (}) ber:
> >>>> dnPretty: <dc=example,dc=com>
> > <<< dnPretty: <dc=example,dc=com>
> >>>> dnNormalize: <dc=example,dc=com>
> > <<< dnNormalize: <dc=example,dc=com>
> > => monitor_back_search
> >>>> dnNormalize: <dc=example,dc=com>
> > <<< dnNormalize: <dc=example,dc=com>
> > send_ldap_result: conn=-1 op=0 p=0
> >
> > The core doesn't provide much information either:
> >
> > Core was generated by
> > `/home/dieter/build/openldap/servers/slapd/.libs/lt-slapd -s0
> > -f /home/dieter/bu'. Program terminated with signal 11, Segmentation
> > fault. #0  0x00002b8afa89117d in ?? ()
> > (gdb) bt
> > #0  0x00002b8afa89117d in ?? ()
> 
> Maybe you can start slapd manually (-h ldap://:9012 -f
> tesrtrun/slapd.2.conf -dargs,trace,stats) and see if it becomes
> responsive and so.  What you show is the result of an internal
> operation (conn=-1), and there seems to be no logging related to the
> ldapsearch that's checking if it started correctly.

I did run both slapd manually -with -d256,
this is the outcome:
<server 1>
../servers/slapd/.libs/lt-slapd -h ldap://:9010/ -f
testrun/slapd.1.conf -d256
 @(#) $OpenLDAP: slapd 2.4.X (Jan 15 2011
16:45:59) $ dieter@rubin:/home/dieter/build/openldap/servers/slapd
hdb_db_open: warning - no DB_CONFIG file found in
directory /home/dieter/build/openldap/tests/testrun/db.1.a: (2). Expect
poor performance for suffix "dc=example,dc=com".
slapd starting

<server 2>
 ../servers/slapd/.libs/lt-slapd -h ldap://:9011/ -f
testrun/slapd.2.conf -d256 @(#) $OpenLDAP: slapd 2.4.X (Jan 15 2011
16:45:59) $ dieter@rubin:/home/dieter/build/openldap/servers/slapd
hdb_db_open: database "dc=example,dc=com":
unclean shutdown detected; attempting recovery. hdb_db_open:
warning - no DB_CONFIG file found in
directory /home/dieter/build/openldap/tests/testrun/db.2.a: (2).
Expect poor performance for suffix "dc=example,dc=com".

and than the process hangs infinitely
a strace attached throws constantly

sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0
sched_yield()                           = 0

only a kill -9 killed this process.

running server 2 with -d-1 show the last lines

> access_allowed: search access to "cn=Database
> 2,cn=Databases,cn=Monitor" "monitoredInfo" requested
=> slap_access_allowed: backend default search access granted to
"(anonymous)" => access_allowed: search access granted by read(=rscxd)
<= test_filter 5
<= test_filter_and 5
<= test_filter 5
send_ldap_result: conn=-1 op=0 p=0
send_ldap_result: err=0 matched="" text=""

and here it hangs

-Dieter

-- 
Dieter Klünter | Systemberatung
http://dkluenter.de
GPG Key ID:DA147B05
53°37'09,95"N
10°08'02,42"E