On 20.9.2013, at 9.07, /dev/rob0 wrote:
> This issue still occurs. It varies which of the four director
> instances gets it, but it seems that once one of them does, the only
> fix is to restart all four.
Do you see any other errors or warnings besides this? Are any of the directors
restarted
This issue still occurs. It varies which of the four director
instances gets it, but it seems that once one of them does, the only
fix is to restart all four.
On Mon, Sep 09, 2013 at 07:41:10AM -0500, /dev/rob0 wrote:
> On Mon, Sep 09, 2013 at 11:13:36AM +0200, Patrick Westenberg wrote:
> > on S
On Mon, Sep 09, 2013 at 11:13:36AM +0200, Patrick Westenberg wrote:
> on Saturday I upgraded two dovecot servers from squeeze to wheezy
> and dovecot from 2.1.x to 2.2.5 (compiled from sources). After the
> upgrade everything worked fine at first.
>
> On Sunday Morning I recognized these errors
Hi @all,
on Saturday I upgraded two dovecot servers from squeeze to wheezy and
dovecot from 2.1.x to 2.2.5 (compiled from sources). After the upgrade
everything worked fine at first.
On Sunday Morning I recognized these errors (they occured after a reload
for logging purpose on midnight) on one
