Hi Karl, I'm not sure if you're aware, but we've removed support for Berkeley DB from 3.0+. It remains in the 2.5 series mainly for legacy reasons, but no-one's specifically maintaining support for it (especially not for newer versions like db5).
Since you've recently upgraded from 2.3 to 2.5, it might be a good opportunity to migrate your Cyrus databases to one of the other database backends such as twoskip or skiplist? It looks like the problems you are having are specifically in the berkeley backend so I think they should be resolved just by switching to other backends. The 'cvt_cyrusdb' tool is able to convert database formats, and you'll also want to update your various foo_db settings in imapd.conf to specify your new database format. If you need to stick with Berkeley DB for some reason, the info-cyrus list might have active subscribers that use this database and might be able to provide guidance (though I'm not directly aware of any) Hope this helps :) ellie On Fri, Nov 16, 2018, at 6:39 AM, Karl Pielorz wrote: > > > --On 12 November 2018 at 08:40:39 +0000 Karl Pielorz > <kpielorz_...@tdx.co.uk> wrote: > > > It'll be a few weeks now (typically) before this happens again. > > This just happened again - but doesn't appear to be related to connections > we just had logged: > > " > Nov 15 18:31:00 imap[84552]: DBERROR db5: pthread suspend failed: Invalid > argument > Nov 15 18:31:00 imap[84552]: DBERROR db5: BDB0061 PANIC: Invalid argument > Nov 15 18:31:00 imap[84552]: DBERROR: critical database situation > ... > Nov 15 18:31:00 imap[84554]: DBERROR db5: BDB0060 PANIC: fatal region error > detected; run recovery > " > > Again, shutdown, clear out 'db/*' and restart - and it's back. The files > 'db': > > -rw------- 1 cyrus cyrus 14770176 Nov 15 19:14 __db.001 > -rw------- 1 cyrus cyrus 32768 Nov 15 19:14 __db.002 > -rw------- 1 cyrus cyrus 49152 Nov 15 19:14 __db.003 > -rw------- 1 cyrus cyrus 4 Nov 15 19:14 skipstamp > > Appear to just be 'binary' - i.e. 'files' against them shows binary - are > these really the files likely to be causing the problem? > > Or is the 'DBERROR db5' still relating to a .db file somewhere? - Be handy > if the 'fatal region' error [or any of them] could list the file the > problem is in :) > > Just really looking for any hints where to look next... > > -Karl
