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
Hi Adam ! Thanks for the answer.
The users are not complaining about the Sieve service and the clients are
able to connect after these messages.
Sorry, I didn't understand what you said about a core file.
On 28 February 2014 18:40, Adam Tauno Williams awill...@whitemice.orgwrote:
On Thu,
Hi !
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
What does this mean? Do I have to increase the maxchild for the sieve
service or my clients are doing something wrong?
--
My
