ctl_cyrusdb using 99& CPU
sb at dod.no
Thu Nov 15 15:33:32 EST 2007
Platform: Intel Pentium II,
When starting up cyrus with
the only cyrus process running is
and it's running using ~99% CPU, but with little memory and disk use
What's printed in /var/log/syslog is:
Nov 15 21:16:04 doohan cyrus/master: process started
Nov 15 21:16:04 doohan cyrus/master: about to exec /usr/sbin/ctl_cyrusdb
Nov 15 21:16:04 doohan cyrus/ctl_cyrusdb: recovering cyrus databases
I've left the process for the entire day today, and it still didn't
When I stop cyrus with
ctl_cyrusdb continues to run with the same high CPU use.
When I start cyrus again with
I see the following in the syslog:
Nov 15 21:29:11 doohan cyrus/master: process started
Nov 15 21:29:11 doohan cyrus/master: about to exec /usr/sbin/ctl_cyrusdb
Nov 15 21:29:11 doohan cyrus/ctl_cyrusdb: recovering cyrus databases
Nov 15 21:29:12 doohan cyrus/ctl_cyrusdb: DBERROR: dbenv->open '/var/lib/cyrus/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Nov 15 21:29:12 doohan cyrus/ctl_cyrusdb: DBERROR: init /var/lib/cyrus/db: cyrusdb error
Nov 15 21:29:12 doohan cyrus/ctl_cyrusdb: done recovering cyrus databases
and the only process running is a new ctl_cyrusdb process (with a new
PID), still with a high CPU usage.
I've run cyrrecover as user cyrus, and it ran without an error, but it
didn't help with the problem. Still the only process that runs is
ctl_cyrusdb, and the same DBERROR message in syslog when starting cyrus
after stopping it.
Does anyone know what causes this? Is there some diagnosis or log I
havent found? I've run cyrreconstruct without any argument, and it
seemed to work on all IMAP folders. Should I have used an argument?
More information about the Info-cyrus