Hello Karl,
man imapd.conf shows the default database types, e.g. check for
annotation_db, duplicate_db… You likely have there explicit or
implicit berkeley database. With cvt_cyrusdb you can switch between
database formats. You use the latter to convert to e.g. twoskip and
then update
This just happened again, on a different server...
Having spent more time looking at this - the error:
Nov 21 07:45:30 imaps[72501]: DBERROR db5: BDB1581 File handles still
open at environment close
I'm guessing "db5" is indeed Berkeley DB5 - so even though in our
imapd.conf we don't
--On 16 November 2018 13:52 +1100 ellie timoney wrote:
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
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
--On 12 November 2018 at 08:40:39 + Karl Pielorz
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
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