2.2.12 to 2.3.13 upgrade :

[Jeff Blaine]

Our happy and functioning 2.2.12 server setup shows the
following when switched over to 2.3.13.  The odd thing is
that we're using skiplist, not berkeley, for our dbs.

If anyone has comments, I'd love to hear them.

bash-2.05# cat /etc/imapd.conf
configdirectory:        /var/imap
defaultpartition:       default
partition-default:      /var/spool/imap
imap_admins:            root cyrus
sasl_pwcheck_method:    saslauthd
sieveusehomedir:        true
autocreatequota:        200000
duplicate_db:           skiplist
tlscache_db:    skiplist
annotation_db:  skiplist
tls_cert_file:  /var/imap/ca.crt
tls_key_file:   /var/imap/server.pem
tls_ca_file:    /var/imap/ca.crt
bash-2.05#

# /etc/init.d/imap stop
Cyrus: Shutting dowm imapd instances
Cyrus: Shutting down master process
# /etc/init.d/imap start
...
Jan 16 05:25:15 imapsrv ctl_cyrusdb[13271]: [ID 866726 local6.warning] 
DBERROR db4: Program version 4.3 doesn't match environment version
Jan 16 05:25:15 imapsrv ctl_cyrusdb[13271]: [ID 866726 local6.warning] 
DBERROR db4: Skipping log file /var/imap/db/log.0000000224: historic log 
version 7
Jan 16 05:25:16 imapsrv ctl_cyrusdb[13271]: [ID 866726 local6.warning] 
DBERROR db4: /var/imap/db/log.0000000225: log file open failed: No such 
file or directory
Jan 16 05:25:16 imapsrv ctl_cyrusdb[13271]: [ID 866726 local6.warning] 
DBERROR db4: PANIC: No such file or directory
Jan 16 05:25:16 imapsrv ctl_cyrusdb[13272]: [ID 866726 local6.warning] 
DBERROR db4: PANIC: fatal region error detected; run recovery