BIG PROBLEM: Need help with production box

[Henrique de Moraes Holschuh]

On Fri, 02 Apr 2004, Curtis Robinson wrote:
> The berkeley db version is 4.1.25.  This problem is new.  This system has been running for monthes
> with changing the software.  So, it is hard to say what the problem is.  I will try the debugging 
> route, but that is terrority I am not familiar with.  I will do the ulimit on memory and see what
> happens.

1. Stop cyrus
2. Go to the berkeley DB environment directory.
3. db_recover
4. Upgrade to BDB 4.2.something, **recompile cyrus against it**
5. db_upgrade
6. Configure the berkeley DB environment, it has precedence over
   anything Cyrus tries to set up.  Search the list archives for
   more hints.
7. db_recover (to reset the environment to your new DBCONFIG
   parameters).
8. start cyrus.

This is not guaranteed to fix your problem, but it just might. If your
machine is SMP on Linux, it is almost guaranteed that DB 4.1 will give you
severe headaches.

What you describe really looks like a severely fubar BDB setup (either the
lib, the DB environment, or the DB itself).  ltrace could tell you more,
I suppose.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html