db5 / PANIC errors under 2.5.12?

[Karl Pielorz]

Hi,

I've recently upgraded a system from Cyrus IMAP 2.5.3 I think it was to 
2.5.12 - and started seeing problems with the __db.00* files.

In the logs we see:

Nov 11 22:43:15 imaps[26220]: imaps TLS negotiation failed: 
some.isp.domain.com [a.b.c.d]
Nov 11 22:43:15 imaps[26221]: imaps TLS negotiation failed: 
some.isp.domain.com [a.b.c.d]
Nov 11 22:43:15 imaps[26223]: imaps TLS negotiation failed: 
some.isp.domain.com [a.b.c.d]
Nov 11 22:43:15 imaps[26226]: imaps TLS negotiation failed: 
some.isp.domain.com [a.b.c.d]
Nov 11 22:43:15 imaps[26226]: DBERROR db5: BDB1581 File handles still open 
at environment close
Nov 11 22:43:15 imaps[26226]: DBERROR db5: BDB1582 Open file handle: 
/vol/host/imap/db/__db.001
Nov 11 22:43:15 imaps[26226]: DBERROR db5: BDB1582 Open file handle: 
/vol/host/imap/db/__db.002
Nov 11 22:43:15 imaps[26226]: DBERROR db5: BDB1582 Open file handle: 
/vol/host/imap/db/__db.003
Nov 11 22:43:15 imaps[26225]: DBERROR db5: BDB0061 PANIC: Invalid argument
Nov 11 22:43:15 imaps[26226]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery
Nov 11 22:43:15 imaps[26225]: DBERROR: critical database situation
Nov 11 22:43:15 imaps[26226]: DBERROR: critical database situation
Nov 11 22:43:15 imaps[26232]: inittls: Loading DH parameters from file
Nov 11 22:43:15 master[1152]: process type:SERVICE name:imaps 
path:/usr/local/cyrus/bin/imapd age:0.184s pid:26225 exited, status 75
Nov 11 22:43:15 master[1152]: process type:SERVICE name:imaps 
path:/usr/local/cyrus/bin/imapd age:0.169s pid:26226 exited, status 75
Nov 11 22:43:15 imaps[26233]: DBERROR db5: BDB0060 PANIC: fatal region 
error detected; run recovery


The a.b.c.d IP address is nothing to do with the server - I think it's 
someone 'trying' to log in with incorrect / guessed credentials.

What I can't tell is:

  - Are the failed logins causing PID 26226 to die in someway that is 
corrupting the database?

  - Or is the database just getting itself corrupt?


We're running FreeBSD 11.2 - there's no dmesg / disk issues I can see. I 
don't currently get any core dumps either. The fix for the above is to 
shutdown Cyrus, 'rm /vol/host/imap/db/*' - and restart it.

It'll be a few weeks now (typically) before this happens again.

Anyone got any suggests as to where to look for more info / possible causes 
/ solutions?


Thanks,

-Karl