Re: Monitor time statistics wrong (ITS#1984)

[masarati@aero.polimi.it]

asparks@quris.com writes: 

> Seem to have a problem w/ this patch, but am working around it.  My
> monitoring script tried to access: 
> 
> /opt/ldap/bin/ldapsearch -h ns01 -s base -b
> cn=Current,cn=Time,cn=Monitor 'objectClass=*' description

First, if you stick with HEAD code now you need to access
"modifyTimeStamp" instead of "description" 

> 
> This caused the server to dump core (signal 9) with traceback:
> #0  0xff0c9cf0 in __sigprocmask () from /usr/lib/libthread.so.1
> #1  0xff0bf324 in _resetsig () from /usr/lib/libthread.so.1
> #2  0xff0bea48 in _sigon () from /usr/lib/libthread.so.1
> #3  0xff0c194c in _thrp_kill () from /usr/lib/libthread.so.1
> #4  0xff1395d8 in abort () from /usr/lib/libc.so.1
> #5  0x23e158 in __eprintf ()
> #6  0xb11d0 in monitor_subsys_time_update ()
> #7  0xde4fc in monitor_entry_update ()
> #8  0xaf5f8 in monitor_back_search ()
> #9  0x4430c in do_search ()
> #10 0x41410 in connection_done ()
> #11 0xf4c58 in ldap_pvt_thread_pool_destroy ()

I could not reproduce any failure, significantly assertion
triggering, using current HEAD code; you should send me a
backtrace of your failure, but first be sure you use HEAD
code. 

Pierangelo. 


Dr. Pierangelo Masarati               | voice: +39 02 2399 8309
Dip. Ing. Aerospaziale                | fax:   +39 02 2399 8334
Politecnico di Milano                 | mailto:pierangelo.masarati@polimi.it
via La Masa 34, 20156 Milano, Italy   | http://www.aero.polimi.it/~masarati