Bug#686110: cyrus-imapd: Corrupted databases can exhaust logging diskspace

[Henrique de Moraes Holschuh]

On Wed, 29 Aug 2012, Ondřej Surý wrote:
> On Tue, Aug 28, 2012 at 7:46 PM, Jamie Thompson
> <bugs.debian at jamie-thompson.co.uk> wrote:
> > Following a power failure my tls_sessions.db file became corrupted (UPS
> > is currently out of commission - anyway). When the server restarted, I
> > did not notice this fact and would not do so until my next logcheck
> > email (or an attempt to check my mail). Unfortunately, within a few
> > hours my logfiles ended up being full of cyrus's infinite unsuccessful
> > startup attempts, resulting in 6GB of logfiles, which so happened to
> > take my server down.
> >
> > Ideally Cyrus should try to recover the databases, if that fails,
> > delete the session-specific recreateable ones (i.e. tls_sessions.db)
> > and try again, and if it is still unable to start, stop trying as
> > without intervention it's just wasting electricity and disk space.
> 
> Well, ideally you should check your system, deamons and logs after a
> power failure.
> 
> I don't think upstream would want to waste development cycles on
> something which can be easily circumvented by human operator.

That depends.  Cyrus master has a controlled respawn system, which may or
may not be active by default.  *IF* it was enabled, and master still filled
the log quicky, THEN it is certainly a bug upstream will want to fix.

"man cyrus.conf" will tell you more about it.

-- 
  "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