Replication is broken with modseq issue in 2.3.6

David S. Madole david at
Thu Jul 6 17:17:39 EDT 2006

On 05 Jul 2006, at 02:54, Bron Gondwana wrote:

>If you're running replication on any post 2.3.3 cyrus, your replica
>contains indexes with '0' as the modseq value.  This means that your
>messages will not be fetchable until you either fix that value or
>patch Cyrus.  Reconstruct from 2.3.6+ is one option for fixing it

Interesting, I discovered the same problem right around the same time
you did.

I submitted a patch that does actually replicate the modseq value,
although unfortunately my first effort was done a little too quickly
and I neglected conversion to/from network byte order as used in the
index files, meaning that the values are not replicated correctly on
x86 machines.

Ken did fix my patch, however, and put it into CVS so I expect this
will be working in the next release. I also fixed my own patch with
the needed ntonl and ntohl etc and re-uploaded into Bugzilla for 
anyone who wants it before then:

Make sure you get the fixed version.


More information about the Info-cyrus mailing list