Re: (ITS#5745) slapcat doesn't return correct error status for bdb fatal error

[Guillaume.Rousse@inria.fr]

Howard Chu a écrit :
> Guillaume.Rousse@inria.fr wrote:
>> Full_Name: Guillaume Rousse
>> Version: 2.4.12
>> OS:
>> URL:
>> Submission from: (NULL) (193.55.250.67)
>>
>>
>> [root@etoile ~]# slapcat -b dc=msr-inria,dc=inria,dc=fr
>> ...
>> bdb(dc=msr-inria,dc=inria,dc=fr): pthread lock failed: Invalid argument
>> bdb(dc=msr-inria,dc=inria,dc=fr): PANIC: Invalid argument
>> bdb(dc=msr-inria,dc=inria,dc=fr): PANIC: DB_RUNRECOVERY: Fatal error, run
>> database recovery
>> bdb(dc=msr-inria,dc=inria,dc=fr): PANIC: fatal region error detected; run
>> recovery
>> bdb_db_close: database "dc=msr-inria,dc=inria,dc=fr": close failed:
>> DB_RUNRECOVERY: Fatal error, run database recovery (-30975)
>> [root@etoile ~]# echo $?
>> 0
>>
>> It makes a bit difficult to know if slapcat-based backup were successful.
> 
> How did you create this situation? I can't test a fix without some way 
> to break the DB in the first place, and generally the DB doesn't fail...
I just upgraded to 2.4.12, as described at 
http://www.openldap.org/lists/openldap-software/200810/msg00087.html.
-- 
Guillaume Rousse
Service des Moyens Informatiques
INRIA Saclay - Ile de France
Tel: 01 69 35 69 62