[elephant-devel] BDB Run recovery errors seen after switching to ELEPHANT-1-0-A2

Ian Eslick eslick at media.mit.edu
Tue Mar 10 21:50:25 UTC 2009


Unfortunately that's not a highly informative backtrace.  Did you  
upgrade to the latest, and this caused it, or did something suddenly  
change that caused the January '09 version to work?

Some possible sources of these problems:

1) Somehow the 'register' flag that helps support multiple processes  
is causing problems; it is no longer set by default I believe.   
(Leslie may know more)

2) The store-controller is not being opened properly.  Are all the  
slots set in the controller after the second process is opened?

Can you be more specific about what changed between January and now?

Ian

On Mar 10, 2009, at 5:31 PM, Yarek Kowalik wrote:

> Hi folks,
>
> I have two processes accessing the same BDB.  One process manages  
> weblocks requests on port 80, the other on port 443. In the elephant  
> from last January, I was able to start, connect and use BDB from  
> both processes.  Now, when I the user is redirected to port 443 and  
> the process tries to retrieve data from the BDB, I get a  
> DB_RUNRECOVERY error (see trace below).   This happens when the port  
> 443 porcess connects for the very first time to BDB.
>
> I think I have seen this before, and I think it had to do with some  
> default configuration on the controler, some argument  that forced  
> the BDB into the recovery mode when process first starts up.
>
> Any idea how to resolve this? It's killing my secure connection on  
> my web app - it's urgent.
>
> Thanks,
>
> Yarek
>
>
>
> Berkeley DB error #-30974: DB_RUNRECOVERY: Fatal error, run database  
> recovery
>    [Condition of type ELEPHANT:BDB-DB-ERROR]
>
> Restarts:
>  0: [TERMINATE-THREAD] Terminate this thread (#<THREAD "hunchentoot- 
> worker-6" RUNNING {B6CD101}>)
>
> Backtrace:
>   0: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN)) #<FUNCTION (LAMBDA  
> #) {AD4FBA5}>)
>   1: (SWANK::DEBUG-IN-EMACS #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)
>   2: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION  
> SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {B729FED}>)
>   3: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {AF23819}>  
> #<CLOSURE (LAMBDA #) {B729FFD}>)
>   4: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {AF23819}>  
> #<CLOSURE (LAMBDA #) {B729FED}>)
>   5: (SWANK:INVOKE-SLIME-DEBUGGER #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)
>   6: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION  
> SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {B729FCD}>)
>   7: (INVOKE-DEBUGGER #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)
>   8: (INVOKE-DEBUGGER #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)[:EXTERNAL]
>   9: ((SB-PCL::FAST-METHOD HUNCHENTOOT:MAYBE-INVOKE-DEBUGGER (T))  
> #<unavailable argument> #<unavailable argument> #<ELEPHANT:BDB-DB- 
> ERROR {B729BF9}>)
>  10: (SIGNAL #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)[:EXTERNAL]
>  11: (ERROR #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)[:EXTERNAL]
>  12: ((FLET #:LAMBDA43) #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)
>  13: ((FLET #:LAMBDA43) #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)[:EXTERNAL]
>  14: (SIGNAL #<ELEPHANT:BDB-DB-ERROR {B729BF9}>)[:EXTERNAL]
>  15: (ERROR ELEPHANT:BDB-DB-ERROR)[:EXTERNAL]
>       Locals:
>         SB-DEBUG::ARG-0 = 3
>         SB-DEBUG::ARG-1 = ELEPHANT:BDB-DB-ERROR
>  16: ((SB-PCL::FAST-METHOD ELEPHANT:GET-VALUE (T DB-BDB::BDB-BTREE))  
> #<unavailable lambda list>)
>       [No Locals]
>  17: (ELEPHANT::ENSURE-SLOT-DEF-INDEX #<unavailable argument>  
> #<unavailable argument>)
>       Locals:
>         SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
>  18: ((SB-PCL::FAST-METHOD ELEPHANT:FIND-INVERTED-INDEX  
> (ELEPHANT:PERSISTENT-METACLASS T)) #<unavailable argument>  
> #<unavailable argument> #<unavailable argument> #<unavailable  
> argument>)[:EXTERNAL]
>       Locals:
>         SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-2 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-3 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-4 = :<NOT-AVAILABLE>
>  19: (ELEPHANT:MAP-INVERTED-INDEX #<unavailable argument>  
> #<unavailable argument> #<unavailable argument>)[:EXTERNAL]
>       Locals:
>         SB-DEBUG::ARG-0 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-1 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-2 = :<NOT-AVAILABLE>
>         SB-DEBUG::ARG-3 = :<NOT-AVAILABLE>
>
>
>
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel





More information about the elephant-devel mailing list