Sieve service terminated abnormally

[Adam Tauno Williams]

On Thu, 2014-02-27 at 15:34 -0300, Fabio S. Schmidt wrote:

> I'm running Cyrus 2.4.14 with Aggregator and this messages appears
> several times on my frontend logs: 
> service sieve pid 10238 in BUSY state: terminated abnormally

I have not seen that message.  Do you end up with a core file?

> What does this mean? Do I have to increase the maxchild for the sieve
> service or my clients are doing something wrong?

Are you clients unable to connect after this message?

-- 
Adam Tauno Williams <mailto:awilliam at whitemice.org> GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA