Jason Williams wrote:
Jan 14 15:08:05 obsidian ctl_cyrusdb[180]: DBERROR: error listing log files: DB_NOTFOUND: No matching key/data pair found
Jan 14 15:08:05 obsidian ctl_cyrusdb[180]: DBERROR: archive
I restarted cyrus to see more information:
[--8<--]
Jan 14 15:21:30 obsidian master[279]: process started
Jan 14 15:21:30 obsidian ctl_cyrusdb[280]: recovering cyrus databases
Jan 14 15:21:30 obsidian ctl_cyrusdb[280]: skiplist: recovered /var/imap/mailboxes.db (2 records, 488 bytes) in 0 seconds
Jan 14 15:21:30 obsidian ctl_cyrusdb[280]: done recovering cyrus databases
So now, no db errors?
Looking closer at the original DB error message, I noticed it was not looking in the right place: /var/imap/mailboxes.db
You can see in the log above, that it is looking at the correct location and DB and no errors.
So my question is, why is that? Why does it first start off with an error message, then after some playing around, it finds it?
Is that a bug? Something on my end?
I have the suspicion that cyrus (actually, ctl_cyrusdb) gets a bit confused when you start it from another directory than /var/imap, which in turn means that you have to start master from that directory. I even had some truss-output that seems to indicate this, but can't get at those from home at the moment. I've basically 'fixed' this by putting a 'cd /var/imap' in the startup-script.
Regards, Paul Boven.
