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.org>wrote: > 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:awill...@whitemice.org> GPG D95ED383 > Systems Administrator, Python Developer, LPI / NCLA > > ---- > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > -- My best regards, Fabio Soares Schmidt Linux Professional Institute - LPIC-3 Microsoft Certified Technology Specialist: Active Directory
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
