Bug#398534: sasl2-bin: Failures also experienced in cyrus21

[Henrique de Moraes Holschuh]

On Thu, 16 Nov 2006, Michael Welsh Duggan wrote:
> This corruption occured under the following circumstances:  I was
> reading mail using an open imap connection.  While reading mail, the

Which means an imapd process was serving it (and it is 100% standalone). So
far, so good.

> sasl packages were updated.  After closing and restarting the imap
> connection later, the skiplists were corrupted.  I do not know if the

This is a bug.  I am completely lost on why it would happen, though, as the
Cyrus imapd processes are 100% stand-alone and self-contained.  They talk to
cyrmaster only to do fork accounting and to get new connections.  It
*really* shouldn't matter if half of them are running with one libsasl, and
the other half with another libsasl.  And they are not even multithreaded,
only mupdate is multithreaded in Cyrus 2.1.

Please review your cyrus logs, and find out if any cyrus children died with
non-zero status codes (cyrus will log this) during or shortly after the
update.  If any of them did, or if you find any anomaly in the logs, please
open a bug against cyrus21-imapd with the logs, as it is a cyrus imapd bug.
If none of them did, I have *no* idea whatsoever on what could have
happened.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh