I've found at least a partial explanation: I forgot to mount the partition with /var/spool/cyrus. I had installed cyrus onto the file system beneath the mount, but the mount was in effect when I created user.ross.* So it wasn't there to open.
Does that explain the errors under /var/lib/cyrus as well (DBERROR: opening /var/lib/cyrus/tls_sessions.db: cyrusdb error)? There was no mount on top of it.
Both before an after the mount all files at and under /var/lib/cyrus and /var/spool/cyrus are owned by cyrus.
Is there a way I can retrigger the jobs that caused the errors shown in the log? Do I run them as root or cyrus?
cryus.conf has
# this is only necessary if using duplicate delivery suppression
delprune cmd="/usr/sbin/cyrus expire -E 3" at=0401
# this is only necessary if caching TLS sessions
tlsprune cmd="/usr/sbin/cyrus tls_prune" at=0401
I'm guessing I run the commands in quotes.
Ross
* In more detail I installed cyrus without the mount, shut it down (I think), cp -a the files in /var/spool/cyrus to the new partition, and then mounted that partition over /var/spool/cyrus. I forgot to stop cyrus before performing the mount this time, but I have subsequently stopped and restarted it.
________________________________________
From: Andrew Morgan [morgan@xxxxxxxx]
Sent: Wednesday, October 29, 2014 1:23 PM
To: Boylan, Ross
Cc: info-cyrus@xxxxxxxxxxxxxxxxxxxx
Subject: Re: Various errors from cyrus maintenance processes
On Wed, 29 Oct 2014, Boylan, Ross wrote:
> I recently installed Cyrus2.4.16-4+deb7u2 on a new Debian wheezy system. After an extended period of difficulties authenticating I can now access it. sasldb has 2 users, ross and cyrus. The only mailbox I created was user.ross.
> Now I see this in my logs (from after the authentication trouble was fixed):
> Oct 28 04:01:00 wheezy4 cyrus/cyr_expire[26711]: DIGEST-MD5 common mech free
> Oct 28 04:01:00 wheezy4 cyrus/tls_prune[26710]: DBERROR: opening /var/lib/cyrus/tls_sessions.db: cyrusdb error
> Oct 28 04:01:00 wheezy4 cyrus/master[7760]: process 26710 exited, status 1
> Oct 28 04:01:00 wheezy4 cyrus/cyr_expire[26711]: IOERROR: opening index user.ross: System I/O error
> Oct 28 04:01:00 wheezy4 cyrus/cyr_expire[26711]: unable to open mailbox user.ross
> Oct 28 04:01:00 wheezy4 cyrus/cyr_expire[26711]: Expunged 0 out of 0 messages from 0 mailboxes
>
> Do these messages indicate any real problems? If so, how can I diagnose
> or fix them?
Yes, those are real problems. They look suspiciously like the errors you
would get if the files in /var/lib/cyrus are owned by root instead of
cyrus.
Andy
----
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
