Thought I'd mention an odd problem with idled which I've worked around
so that it gets into the list archive.
Running 2.3.16, the master starts idled without error. However, all of
the services initially started by master would fail to contact idled and
give the following error:
imap[23494]: e
Raphael Jaffey wrote:
>
> Dietmar Rieder wrote:
>> Hi,
>>
>> we just updated our master + replication servers from 2.3.13 to 2.3.16
>> and discovered, that the sync_client is dying with a segfault when it
>> connects to the replication server which has set "allowplaintext: no".
>>
>> We manage
On 28 Mar 2010, at 20:04, karen turner wrote:
> Mar 26 15:38:28 zysv01 mupdate[31564]: attempt to delete unknown
> mailbox
> user.xxaabb
>
> Where the mailbox is actually on a different server. I assume that
> this is an
> issue with replication and will go away when all servers are on
> 2.3
On 27 Mar 2010, at 20:55, Jason L Tibbitts III wrote:
> I had guessed, though perhaps I had hoped that something would simply
> tell me that instead of giving odd errors that made me think that I
> had
> misconfigured something.
I agree. I think it's probably in the release notes, but since it'
Dietmar Rieder wrote:
> Hi,
>
> we just updated our master + replication servers from 2.3.13 to 2.3.16
> and discovered, that the sync_client is dying with a segfault when it
> connects to the replication server which has set "allowplaintext: no".
>
> We managed to trace down the problem and
Hi
Has any one had any experience in going from 2.3.12p2 to 2.3.16.
It appears to work. I can create and delete mailboxes on a 2.3.12p2 or 2.3.16
and it replicates out to the other version.
I do get messages on the 2.3.16 server like
Mar 26 15:38:28 zysv01 mupdate[31564]: attempt to delete unk
On Fri, Mar 26, 2010 at 12:01:01PM -0400, Greg A. Woods wrote:
> on "return" paths, perhaps, but not exit() paths -- there is no leak on
> exit() :-)
The leak of course happens much before exit(). But memory profilers
report unfreed memory after the process exits, and there is definite
difference
> "BG" == Bron Gondwana writes:
BG> The advantage of reconstructing (if you choose that
BG> path instead, heaps more IO use though) is that you'll get real SHA1
BG> GUIDs rather than padded GUIDs. Not a huge deal - though I'll
BG> probably force the SHA1 calculation in the 2.4 upgrade, becau
