Re: [Dovecot] (new) director issues in 2.1.10

2012-10-22 Thread Timo Sirainen
On 26.9.2012, at 21.06, Kelsey Cummings wrote: 09:25:21 .. User X host lookup failed: Timeout - queued for 30 secs (Ring synced for 5032 secs) 09:25:55 .. User X host lookup failed: Timeout - queued for 30 secs (Ring synced for 5066 secs, weak user, user refreshed 64 secs ago) 09:26:28 ..

Re: [Dovecot] (new) director issues in 2.1.10

2012-10-22 Thread Kelsey Cummings
On Mon, Oct 22, 2012 at 03:39:34PM +0300, Timo Sirainen wrote: On 26.9.2012, at 21.06, Kelsey Cummings wrote: 09:25:21 .. User X host lookup failed: Timeout - queued for 30 secs (Ring synced for 5032 secs) 09:25:55 .. User X host lookup failed: Timeout - queued for 30 secs (Ring

[Dovecot] (new) director issues in 2.1.10

2012-09-26 Thread Kelsey Cummings
Timo - I upgraded to 2.1.10 on our director servers two nights ago and apart from errors associated with the directors processes restarting everything looked great for ~24 hours until I failed our the real servers last night to update the nfs mount options for the spools. I followed the

Re: [Dovecot] (new) director issues in 2.1.10

2012-09-26 Thread Timo Sirainen
On 26.9.2012, at 20.34, Kelsey Cummings wrote: The following errors on the directors that started after this went unnoticed until this AM. director: User bb host lookup failed: Timeout - queued for 30 secs (Ring synced for 36 secs) director: User cc host lookup failed: Timeout - queued

Re: [Dovecot] (new) director issues in 2.1.10

2012-09-26 Thread Kelsey Cummings
On Wed, Sep 26, 2012 at 08:57:58PM +0300, Timo Sirainen wrote: On 26.9.2012, at 20.34, Kelsey Cummings wrote: The following errors on the directors that started after this went unnoticed until this AM. director: User bb host lookup failed: Timeout - queued for 30 secs (Ring synced

Re: [Dovecot] (new) director issues in 2.1.10

2012-09-26 Thread Kelsey Cummings
On 09/26/12 11:06, Kelsey Cummings wrote: No, there continued to be a mix of both. The pattern seems to look like this. I'll run some stats later but it looks like a pretty significant number of users where affected. Timo, it looks like the total number of affected users was only about 250