IOERROR: conversations_audit on store
Frederik Himpe
frederik at frehi.be
Mon Aug 24 04:22:56 EDT 2020
I am using Cyrus 3.2.2 on Debian Buster 10 (package from buster-
backports).
I am having lots of errors similar to these in the logs:
cyrus/imaps[24052]: IOERROR: conversations_audit on store: /var/lib/cyrus/user/e/example.conversations Bff62cd0852db22e1 0 (1452110 1 0 0 () ((1 1452109 1 1 0)) () foobar. 0 () 1452109)
The same problem happend with Cyrus 3.0.x and seems to happen often for
specific users, usually with big mailboxes (one of them 40GB+). When
upgrading to 3.2.2, I ran
reconstruct -V max
ctl_conversationsdb -b -r
quota -f
dav_reconstruct -a
as per the instructions given in the documentation.
/var/lib/cyrus and /var/spool/cyrus are on ext4, Linux kernel at this
moment is 5.4.48 (also happend with different kernels).
imapd.conf:
configdirectory: /var/lib/cyrus
proc_path: /run/cyrus/proc
mboxname_lockpath: /run/cyrus/lock
defaultpartition: default
partition-default: /var/spool/cyrus/mail
partition-news: /var/spool/cyrus/news
altnamespace: yes
unixhierarchysep: yes
lmtp_downcase_rcpt: yes
admins: cyradm
allowanonymouslogin: no
popminpoll: 1
autocreate_quota: 5000000
umask: 077
sieveusehomedir: false
sievedir: /var/spool/sieve
httpmodules: caldav carddav
hashimapspool: true
allowplaintext: yes
sasl_mech_list: PLAIN
sasl_saslauthd_path: /var/spool/postfix/var/run/saslauthd/mux
sasl_minimum_layer: 128
sasl_pwcheck_method: saslauthd
sasl_auto_transition: no
tls_server_cert: /etc/letsencrypt/live/ai.vub.ac.be/fullchain.pem
tls_server_key: /etc/letsencrypt/live/ai.vub.ac.be/privkey.pem
tls_client_ca_dir: /etc/ssl/certs
tls_session_timeout: 1440
tls_ciphers: TLSv1.2:+TLSv1:+HIGH:!aNULL:@STRENGTH
tls_versions: tls1_0 tls1_1 tls1_2
lmtpsocket: /run/cyrus/socket/lmtp
idlesocket: /run/cyrus/socket/idle
notifysocket: /run/cyrus/socket/notify
syslog_prefix: cyrus
delete_mode: delayed
expunge_mode: delayed
sync_log: on
sync_log_channels: squatter
conversations: 1
cyrus.conf:
START {
recover cmd="/usr/sbin/cyrus ctl_cyrusdb -r"
idled cmd="idled"
}
SERVICES {
imap cmd="imapd -U 30" listen="imap" prefork=0 maxchild=100
imaps cmd="imapd -s -U 30" listen="imaps" prefork=0 maxchild=100
pop3 cmd="pop3d -U 30" listen="pop3" prefork=0 maxchild=50
pop3s cmd="pop3d -s -U 30" listen="pop3s" prefork=0 maxchild=50
http cmd="httpd -U 30 -p 256" listen="localhost:8008" prefork=0 maxchild=100
lmtpunix cmd="lmtpd" listen="/var/spool/postfix/var/run/cyrus/socket/lmtp" prefork=0 maxchild=20
sieve cmd="timsieved" listen="sieve" prefork=0 maxchild=100
notify cmd="notifyd" listen="/run/cyrus/socket/notify" proto="udp" prefork=1
}
EVENTS {
checkpoint cmd="/usr/sbin/cyrus ctl_cyrusdb -c" period=30
delprune cmd="/usr/sbin/cyrus expire -E 3" at=0401
tlsprune cmd="/usr/sbin/cyrus tls_prune" at=0415
deleteprune cmd="/usr/sbin/cyrus expire -E 4 -D 28" at=0430
expungeprune cmd="/usr/sbin/cyrus expire -E 4 -X 28" at=0445
squatter1 cmd="/usr/bin/nice -n 19 /usr/sbin/cyrus squatter -i" period=120
squattera cmd="/usr/bin/nice -n 19 /usr/sbin/cyrus squatter -i" at=0517
}
Any idea what is going wrong?
--
Frederik Himpe <frederik at frehi.be>
More information about the Info-cyrus
mailing list