The same thing again: Cyrus IMAP 3.12.4 was working fine before the restart, 
but after its certificate was updated, Cyrus did not recover: *couldn't dup fd 
0: Bad file descriptor*.

This time, reconstruct -r -f did not help nor with the stricter options 
--guid-mismatch-keep , --update-uniqueids , even --force-reparse, 
--guid-mismatch-discard, --delete-odd-files.

Right now, I am helplessly angry that Cyrus won't tell me which file it could 
not find (or does not have permission to access). I really have no idea where 
to look (it's like looking for a needle in a haystack). There is no trace of 
what's wrong in debug.log; the last entry there is
> Nov 15 10:45:01 sala cyrus/master[7736]: ready for work

Cyrus.conf, imapd.conf have not been touched in a long time, and the locations 
of other files and DBs have not changed either, it is probably just some minor 
glitch in the mail storage. It is disappointing that the entire IMAP service is 
shut down over such a minor issue without any reference.

By the way, why is not there (or am I just unaware of it?) a dry-run command to 
check in advance whether imapd will restart successfully?
------------------------------------------
Cyrus: Info
Permalink: 
https://cyrus.topicbox.com/groups/info/T1d59a96da231eba0-M6df2d307a1640aa859f18855
Delivery options: https://cyrus.topicbox.com/groups/info/subscription

Reply via email to