Re: Problems with Cyrus IMAP 2.1.13

2003-06-06 Thread Gareth Bult
... Completely clean install ... Cyrus+Postfix+SASL+SA On Fri, 2003-06-06 at 14:30, Rob Siemborski wrote: On Fri, 6 Jun 2003, Gareth Bult wrote: > > You shouldn't ever need to reconstruct unless a mailbox is corrupted (And > > that can be done live). ctl_cyrusdb -r should *always* be run b

Re: Problems with Cyrus IMAP 2.1.13

2003-06-06 Thread Rob Siemborski
On Fri, 6 Jun 2003, Gareth Bult wrote: > > You shouldn't ever need to reconstruct unless a mailbox is corrupted (And > > that can be done live). ctl_cyrusdb -r should *always* be run becfore > > cyrus starts (it should be in the START section of master.conf). > > Ok, so what would you make of thi

Re: Problems with Cyrus IMAP 2.1.13

2003-06-06 Thread Gareth Bult
> Means your client has dropped out 'uncleanly'. Its a harmless log message, and if you're logging at LOG_DEBUG you should expect to see a lot of harmless log messages. Sure.  However I have noted that I "only" see this when my client dies, not when it exits.. [!] In the next version of c

Re: Problems with Cyrus IMAP 2.1.13

2003-06-06 Thread Rob Siemborski
On Fri, 6 Jun 2003, Gareth Bult wrote: > >Jun 6 06:57:48 Mercury imapd[3676]: Could not shut down filedescriptor > 0: Socket is not connected > > Means your client has dropped out 'uncleanly'. Its a harmless log message, and if you're logging at LOG_DEBUG you should expect to see a lot of harmle

Re: Problems with Cyrus IMAP 2.1.13

2003-06-06 Thread Ken Murchison
Nikola Milutinovic wrote: 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 subtl

Re: Problems with Cyrus IMAP 2.1.13

2003-06-06 Thread Gareth Bult
Hi, I've seen similar things here. >Jun  6 06:57:59 Mercury pop3d[2888]: error sending to idled: 2 Means that something has crashed badly. >Jun  6 06:57:48 Mercury imapd[3676]: Could not shut down filedescriptor 0: Socket is not connected Means your client has dropped out 'uncleanly'. Or

Problems with Cyrus IMAP 2.1.13

2003-06-05 Thread 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 m