Again: DB ERROR: critical database situation

[Henning Holtschneider]

On Friday 12 August 2005 11:52, steven truppe wrote:

> yesterday i restored the mailboxes.db my hand (like Henning Holtschneider
> told me) and all went fine
> for some hours. Now i have near the same thing again. My users can get
> their mails, but they can not send any. I think the only solution is to
> reinstall kolab and recreate all users (only 8).

No. If the Cyrus databases break, the RAM on your server is faulty. It could 
be the filesystem, too. But unless you have very little RAM on the machine (< 
256 MB), regarding the small number of users, this is very unlikely.

I was told by the Cyrus developers that database problems are being caused by 
server memory errors. At first, I didn't want to believe them. I had the 
problem on three totally different servers. It turned out that one server had 
bad RAM (I had to run memtest86 for several days to reproduce the error), the 
other had a blown capacitor on the memory voltage regulator. I haven't been 
able to reproduce the problem on the third machine. After fixing the hardware 
problems, the DBERRORs are gone!

Regards,
Henning Holtschneider
--
LocaNet oHG - http://www.loca.net
Lindemannstrasse 81, D-44137 Dortmund
tel +49 231 91596-25, fax +49 231 91596-55
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20050812/62ab5692/attachment.sig>