A strange disaster after years of flawless Cyrus work.

After replacing an expiring certificate, I had to reload Cyrus IMAP 3.12.1 on FreeBSD 14.3-RELEASE-p7. Unfortunately, this time Cyrus has shut down and refuses to start without a clear reason:

*couldn't dup fd 0: Bad file descriptor*

The last lines from maillog:

Dec 22 18:30:00 … cyrus/imap[51173]: graceful shutdown
Dec 22 18:30:00 … cyrus/imap[6908]: graceful shutdown
Dec 22 18:30:00 … cyrus/imap[40383]: graceful shutdown
Dec 22 18:30:00 … cyrus/notify[4142]: graceful shutdown
Dec 22 18:30:00 … cyrus/imap[42239]: graceful shutdown
Dec 22 18:30:00 … cyrus/imap[40389]: graceful shutdown
Dec 22 18:30:00 … cyrus/imap[40141]: graceful shutdown
Dec 22 18:30:00 … cyrus/idled[4144]: graceful shutdown
Dec 22 18:30:00 … cyrus/imap[40407]: graceful shutdown
Dec 22 18:30:00 … cyrus/master[4127]: All children have exited, closing down
Dec 22 18:30:01 … master[67928]: couldn't dup fd 0: Bad file descriptor
Dec 22 18:30:01 … master[67928]: exiting
Dec 22 18:30:01 … username[67932]: /usr/local/etc/rc.d/imapd: WARNING: failed to
start cyrus_imapd
Dec 22 18:30:43 … master[68279]: couldn't dup fd 0: Bad file descriptor
Dec 22 18:30:43 … master[68279]: exiting
Dec 22 18:30:43 … usernam[68283]: /usr/local/etc/rc.d/imapd: WARNING: failed to
start cyrus_imapd

debug.log no errors at all, the last line is:

Dec 22 18:30:00 … cyrus/master[4127]: ready for work

What “couldn't dup fd 0: Bad file descriptor” mean, where to look for the snag, how to fix it?

Vladas

------------------------------------------
Cyrus: Info
Permalink: 
https://cyrus.topicbox.com/groups/info/T1d59a96da231eba0-M8caa708ca958e0b2a1326fd9
Delivery options: https://cyrus.topicbox.com/groups/info/subscription

Reply via email to