Twoskip DB files broken

Bron Gondwana brong at fastmail.fm
Thu Sep 29 18:00:13 EDT 2016 

A couple of things.

1. Why are you doing this? What do you hope to achieve?

2. Possibly kolab's Cyrus configuration stores files in other paths (tmpfs, data dirs) which are Berkeley dbs and don't expect their environment to be trashed under them.

On Thu, 29 Sep 2016, at 23:47, Tobias Brunner via Info-cyrus wrote:
> Hi,
> 
> I've discovered an odd behaviour which I don't understand: After a
> completely fresh Kolab 16 install on CentOS 7
> (cyrus-imapd-2.5.9.27-5.1.el7.kolab_wf.x86_64) everything looks fine. I
> can create mailboxes, stop/start Cyrus, all works as it should do. The
> contents of /var/lib/imap looks like this:
> 
> -rw------- 1 cyrus mail 3.8K Sep 29 14:48 annotations.db
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 backup
> drwxr-x--- 2 cyrus mail   22 Sep 29 14:48 db
> drwx------ 2 cyrus mail   46 Sep 29 14:48 db.backup1
> -rw------- 1 cyrus mail  336 Sep 29 14:48 deliver.db
> drwx------ 3 cyrus mail   14 Sep 29 14:48 domain
> drwx------ 5 cyrus mail   35 Sep 29 14:48 lock
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 log
> -rw------- 1 cyrus mail 3.7K Sep 29 14:48 mailboxes.db
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 md5
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 meta
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 msg
> drwxr-x--- 2 cyrus mail   18 Sep 29 14:56 proc
> drwxr-x--- 2 cyrus mail   37 Sep 29 14:48 ptclient
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 quota
> drwxr-x--- 2 cyrus mail   51 Sep 29 14:48 rpm
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 sieve
> drwxr-x--- 2 cyrus mail 4.0K Sep 29 14:56 socket
> -rw------- 1 cyrus mail  336 Sep 29 14:48 statuscache.db
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 sync
> -rw------- 1 cyrus mail  768 Sep 29 14:48 tls_sessions.db
> drwxr-x--- 2 cyrus mail    6 Sep 22 17:25 user
> 
> Then I do:
> 
> 1. Stop Cyrus: systemctl stop cyrus-imapd. Log says:
> 
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: attempting clean
> shutdown on signal
> Sep 29 14:57:59 kolabv.vagrant.dev pop3[16965]: graceful shutdown
> initiated by unexpected process 1 (/usr/lib/systemd/systemd
> --switched-root --system --deserialize 21)
> Sep 29 14:57:59 kolabv.vagrant.dev pop3[16971]: graceful shutdown
> initiated by unexpected process 1 (/usr/lib/systemd/systemd
> --switched-root --system --deserialize 21)
> Sep 29 14:57:59 kolabv.vagrant.dev lmtpunix[16967]: graceful shutdown
> initiated by unexpected process 1 (/usr/lib/systemd/systemd
> --switched-root --system --deserialize 21)
> Sep 29 14:57:59 kolabv.vagrant.dev systemd[1]: Stopping Cyrus-imapd
> IMAP/POP3 email server...
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:imap path:/usr/lib/cyrus-imapd/imapd age:561.385s pid:16959 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:imap path:/usr/lib/cyrus-imapd/imapd age:561.385s pid:16961 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3 path:/usr/lib/cyrus-imapd/pop3d age:561.385s pid:16963 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3 path:/usr/lib/cyrus-imapd/pop3d age:561.385s pid:16964 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3s path:/usr/lib/cyrus-imapd/pop3d age:561.385s pid:16966
> exited, status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:imap path:/usr/lib/cyrus-imapd/imapd age:561.387s pid:16958 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:imap path:/usr/lib/cyrus-imapd/imapd age:561.389s pid:16960 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3 path:/usr/lib/cyrus-imapd/pop3d age:561.389s pid:16965 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:lmtpunix path:/usr/lib/cyrus-imapd/lmtpd age:561.388s pid:16967
> exited, status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:notify path:/usr/lib/cyrus-imapd/notifyd age:561.388s pid:16968
> exited, status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3 path:/usr/lib/cyrus-imapd/pop3d age:561.388s pid:16969 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3 path:/usr/lib/cyrus-imapd/pop3d age:561.388s pid:16970
> signaled to death by signal 15 (Terminated)
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3 path:/usr/lib/cyrus-imapd/pop3d age:561.388s pid:16971 exited,
> status 75
> Sep 29 14:57:59 kolabv.vagrant.dev master[16944]: process type:SERVICE
> name:pop3s path:/usr/lib/cyrus-imapd/pop3d age:561.388s pid:16972
> exited, status 75
> Sep 29 14:57:59 kolabv.vagrant.dev systemd[1]: Stopped Cyrus-imapd
> IMAP/POP3 email server.
> 
> 2. Remove all content of /var/lib/imap: rm -rf /var/lib/imap/*
> 3. Start Cyrus, which automatically recreates the folder structure under
> /var/lib/imap. The folder content:
> 
> -rw------- 1 cyrus mail 3.8K Sep 29 15:00 annotations.db
> drwxr-xr-x 2 cyrus mail   22 Sep 29 15:00 db
> drwx------ 2 cyrus mail   46 Sep 29 15:00 db.backup1
> -rw------- 1 cyrus mail  336 Sep 29 15:00 deliver.db
> drwx------ 3 cyrus mail   14 Sep 29 15:00 domain
> drwx------ 5 cyrus mail   35 Sep 29 15:00 lock
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 log
> -rw------- 1 cyrus mail 3.6K Sep 29 15:00 mailboxes.db
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 msg
> drwxr-xr-x 2 cyrus mail   18 Sep 29 15:00 proc
> drwxr-xr-x 2 cyrus mail   37 Sep 29 15:00 ptclient
> drwxr-xr-x 2 cyrus mail   26 Sep 29 15:00 rpm
> drwxr-xr-x 2 cyrus mail 4.0K Sep 29 15:00 socket
> -rw------- 1 cyrus mail  336 Sep 29 15:00 statuscache.db
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 sync
> -rw------- 1 cyrus mail 1.3K Sep 29 15:00 tls_sessions.db
> 
> 4. Stop Cyrus again. This now leads to broken DBs, renamed to *.db.berkeley:
> 
> -rw------- 1 cyrus mail 3.8K Sep 29 15:00 annotations.db.berkeley
> drwxr-xr-x 2 cyrus mail   22 Sep 29 15:00 db
> drwx------ 2 cyrus mail   46 Sep 29 15:00 db.backup1
> -rw------- 1 cyrus mail  336 Sep 29 15:00 deliver.db.berkeley
> drwx------ 3 cyrus mail   14 Sep 29 15:00 domain
> drwx------ 5 cyrus mail   35 Sep 29 15:00 lock
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 log
> -rw------- 1 cyrus mail 3.6K Sep 29 15:00 mailboxes.db.berkeley
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 msg
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:01 proc
> drwxr-xr-x 2 cyrus mail   46 Sep 29 15:01 ptclient
> drwxr-xr-x 2 cyrus mail   46 Sep 29 15:01 rpm
> drwxr-xr-x 2 cyrus mail 4.0K Sep 29 15:01 socket
> -rw------- 1 cyrus mail  336 Sep 29 15:00 statuscache.db.berkeley
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 sync
> -rw------- 1 cyrus mail 1.5K Sep 29 15:00 tls_sessions.db.berkeley
> 
> 5. Start Cyrus again, files are recreated:
> 
> -rw------- 1 cyrus mail  336 Sep 29 15:01 annotations.db
> -rw------- 1 cyrus mail 3.8K Sep 29 15:00 annotations.db.berkeley
> drwxr-xr-x 2 cyrus mail   22 Sep 29 15:00 db
> drwx------ 2 cyrus mail   46 Sep 29 15:01 db.backup1
> drwx------ 2 cyrus mail   46 Sep 29 15:00 db.backup2
> -rw------- 1 cyrus mail  336 Sep 29 15:01 deliver.db
> -rw------- 1 cyrus mail  336 Sep 29 15:00 deliver.db.berkeley
> drwx------ 3 cyrus mail   14 Sep 29 15:00 domain
> drwx------ 5 cyrus mail   35 Sep 29 15:00 lock
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 log
> -rw------- 1 cyrus mail  336 Sep 29 15:01 mailboxes.db
> -rw------- 1 cyrus mail 3.6K Sep 29 15:00 mailboxes.db.berkeley
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 msg
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:01 proc
> drwxr-xr-x 2 cyrus mail   46 Sep 29 15:01 ptclient
> drwxr-xr-x 2 cyrus mail   46 Sep 29 15:01 rpm
> drwxr-xr-x 2 cyrus mail 4.0K Sep 29 15:01 socket
> -rw------- 1 cyrus mail  336 Sep 29 15:01 statuscache.db
> -rw------- 1 cyrus mail  336 Sep 29 15:00 statuscache.db.berkeley
> drwxr-xr-x 2 cyrus mail    6 Sep 29 15:00 sync
> -rw------- 1 cyrus mail 1.5K Sep 29 15:00 tls_sessions.db.berkeley
> 
> I even tried mkimap before step 3 which basically creates the same
> folder structure as Cyrus does on startup.
> 
> It seems to me that Cyrus is doing some bogus stuff or I'm missing an
> important step. Has anyone an explanation for this odd behaviour? What
> am I missing here? How is the initial folder structure created which
> seems to be fine?
> 
> Cheers,
> Tobias
> 
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
> Email had 1 attachment:
> + signature.asc
>   1k (application/pgp-signature)


-- 
  Bron Gondwana
  brong at fastmail.fm

More information about the Info-cyrus mailing list