Problems with Cyrus IMAP 2.1.13

[Nikola Milutinovic]

Hi all.

Just upgraded our production server to 2.1.13. I must confess, yesterday afternoon and evening were full of Gremlins (those little creatures that screw up your, otherwise, perfect plan for upgrade).

Well, I got the Cyrus UP and RUNNING, but there are some subtle points which fail and make me nervous.

POINT 1: admin
-----------------

I have users "cyrus" and "root" listed as admins in the "imapd.conf" file. I can login as "root" via "cyradm", no problem (cyradm --auth=cram-md5 --user=root localhost). I can create mailboxes "cm user.nikola".

What I cannot do is: 

list mailboxes ("lm" just gives empty line), 
delete a mailbox ("dm user.ene" just gives "deletemailbox: " and the mailbox is still there)
list ACL for a mailbox (again, a blank line)
I CAN set ACL for mailbox ("sam user.ene root lrwp" gives "setaclmailbox: root: lrwp:")

What is going on here? I'd expect it to be some general ACL problem, but if someone can advise, I'd be grateful.

POINT 2: imapd complains
----------------------------
I am seeing this in "imap.log"

Jun  6 07:54:40 Mercury master[5235]: about to exec /usr/opt/Cyrus-IMAP-2.1.13/sbin/imapd
Jun  6 07:54:40 Mercury imaps[5235]: executed
Jun  6 07:54:40 Mercury imapd[5235]: accepted connection
Jun  6 07:54:40 Mercury imapd[5235]: mystore: starting txn 2147483707
Jun  6 07:54:40 Mercury imapd[5235]: mystore: committing txn 2147483707
Jun  6 07:54:40 Mercury imapd[5235]: starttls: TLSv1 with cipher RC4-MD5 (128/128 bits new) no authentication
Jun  6 07:54:40 Mercury imapd[5235]: login: Brigitte.ev.co.yu[192.168.61.110] nikola plaintext+TLS 
Jun  6 07:54:40 Mercury imapd[5235]: seen_db: user nikola opened /var/opt/Cyrus-IMAP-2.1.13/config/user/n/nikola.seen
Jun  6 07:54:40 Mercury imapd[5235]: open: user nikola opened INBOX
Jun  6 07:54:41 Mercury imapd[5235]: Connection reset by peer, closing connection
Jun  6 07:54:41 Mercury imapd[5235]: Could not shut down filedescriptor 0: Socket is not connected
Jun  6 07:54:41 Mercury imapd[5235]: Could not shut down filedescriptor 1: Socket is not connected
Jun  6 07:54:41 Mercury imapd[5235]: Could not shut down filedescriptor 2: Socket is not connected

Jun  6 08:00:52 Mercury master[5337]: about to exec /usr/opt/Cyrus-IMAP-2.1.13/sbin/lmtpd
Jun  6 08:00:52 Mercury lmtpunix[5337]: executed
Jun  6 08:00:53 Mercury lmtpd[5337]: accepted connection
Jun  6 08:00:53 Mercury lmtpd[5337]: lmtp connection preauth'd as postman
Jun  6 08:00:53 Mercury lmtpd[5337]: duplicate_check: <200306060600.h5660YU7021746 at Uprava.ev.co.yu> user.nikola          0
Jun  6 08:00:53 Mercury lmtpd[5337]: mystore: starting txn 2147483730
Jun  6 08:00:53 Mercury lmtpd[5337]: mystore: committing txn 2147483730
Jun  6 08:00:53 Mercury lmtpd[5337]: duplicate_mark: <200306060600.h5660YU7021746 at Uprava.ev.co.yu> user.nikola          1054879253
Jun  6 08:00:53 Mercury lmtpd[5337]: Could not shut down filedescriptor 0: Socket is not connected
Jun  6 08:00:53 Mercury lmtpd[5337]: Could not shut down filedescriptor 1: Socket is not connected
Jun  6 08:00:53 Mercury lmtpd[5337]: Could not shut down filedescriptor 2: Socket is not connected

POINT 3: (could be gone) IdleD problems.
-------------------------------------------

I was seeing complaints from both "imapd" and "lmtpd", that they couldn't connect to "idled socket", but those are gone at the moment. The log contained this:

Jun  6 06:57:43 Mercury master[3365]: about to exec /usr/opt/Cyrus-IMAP-2.1.13/sbin/imapd
Jun  6 06:57:43 Mercury imap[3365]: executed
Jun  6 06:57:44 Mercury imapd[3365]: accepted connection
Jun  6 06:57:44 Mercury imapd[3365]: login: webmaster.ev.co.yu[192.168.61.105] davor plaintext 
Jun  6 06:57:47 Mercury imapd[3676]: error sending to idled: 0
Jun  6 06:57:47 Mercury imapd[3676]: error sending to idled: 1
Jun  6 06:57:48 Mercury imapd[3676]: seen_db: user davor opened /var/opt/Cyrus-IMAP-2.1.13/config/user/d/davor.seen
Jun  6 06:57:48 Mercury imapd[3676]: error sending to idled: 0
Jun  6 06:57:48 Mercury imapd[3676]: error sending to idled: 1
Jun  6 06:57:48 Mercury imapd[3676]: Could not shut down filedescriptor 0: Socket is not connected
Jun  6 06:57:48 Mercury imapd[3676]: Could not shut down filedescriptor 1: Socket is not connected
Jun  6 06:57:48 Mercury imapd[3676]: Could not shut down filedescriptor 2: Socket is not connected
Jun  6 06:57:48 Mercury imapd[3676]: accepted connection
Jun  6 06:57:48 Mercury imapd[3676]: login: webmaster.ev.co.yu[192.168.61.105] davor plaintext 
Jun  6 06:57:49 Mercury master[2888]: about to exec /usr/opt/Cyrus-IMAP-2.1.13/sbin/pop3d
Jun  6 06:57:49 Mercury pop3[2888]: executed
Jun  6 06:57:49 Mercury pop3d[2888]: accepted connection
Jun  6 06:57:49 Mercury pop3d[2888]: login: Celeron2.ev.co.yu[192.168.1.135] draganal plaintext 
Jun  6 06:57:54 Mercury imapd[3365]: error sending to idled: 0
Jun  6 06:57:54 Mercury imapd[3365]: error sending to idled: 1
Jun  6 06:57:54 Mercury imapd[3365]: seen_db: user davor opened /var/opt/Cyrus-IMAP-2.1.13/config/user/d/davor.seen
Jun  6 06:57:54 Mercury imapd[3365]: open: user davor opened INBOX
Jun  6 06:57:54 Mercury imapd[3365]: error sending to idled: 0
Jun  6 06:57:58 Mercury imapd[3676]: error sending to idled: 0
Jun  6 06:57:58 Mercury imapd[3676]: error sending to idled: 1
Jun  6 06:57:58 Mercury imapd[3676]: open: user davor opened INBOX
Jun  6 06:57:58 Mercury imapd[3676]: error sending to idled: 0
Jun  6 06:57:58 Mercury imapd[3676]: error sending to idled: 1
Jun  6 06:57:59 Mercury pop3d[2888]: error sending to idled: 2
Jun  6 06:58:03 Mercury imapd[3676]: error sending to idled: 0
Jun  6 06:58:03 Mercury imapd[3676]: error sending to idled: 1
Jun  6 06:58:03 Mercury imapd[3676]: error sending to idled: 0
Jun  6 06:58:03 Mercury imapd[3676]: error sending to idled: 1
Jun  6 06:58:03 Mercury imapd[3676]: error sending to idled: 0
Jun  6 06:58:03 Mercury imapd[3676]: error sending to idled: 1

This was at a stage when TLS was not working and one of those Gremlins was around, so, I would not be surprized if that was the cause.

TYIA,
Nix.