On Fri, Nov 23, 2012 at 08:36:37AM +0200, Timo Sirainen wrote:
On 9.11.2012, at 2.49, Kelsey Cummings wrote:
One of our dovecot backend servers ran into a problem with it's auth
process a few days ago. This doesn't appear to be the error logged when
dovecot hits its internal limit so I'm
On 26.11.2012, at 22.03, Kelsey Cummings wrote:
auth: Error: malloc: 58012: Cannot allocate memory
auth: Error: Unable to allocate memory for mutexes from the region
auth: Error: PANIC: Cannot allocate memory
auth: passwd(test,1.1.1.1,8HTlNHzNIQBAjhKC): unknown user
..
Memory leak maybe?
On 27.11.2012, at 8.39, Timo Sirainen wrote:
userdb {
driver = passwd
}
Both of these lookups should be done by auth-worker processes. So why is it
the auth process that complains?
Because of a bug in v2.0.16+ :(
http://hg.dovecot.org/dovecot-2.1/rev/8e5d9d88e250
As a workaround you
On 9.11.2012, at 2.49, Kelsey Cummings wrote:
One of our dovecot backend servers ran into a problem with it's auth
process a few days ago. This doesn't appear to be the error logged when
dovecot hits its internal limit so I'm not sure what is going on here.
auth: Error: malloc: 58012:
One of our dovecot backend servers ran into a problem with it's auth
process a few days ago. This doesn't appear to be the error logged when
dovecot hits its internal limit so I'm not sure what is going on here.
auth: Error: malloc: 58012: Cannot allocate memory
auth: Error: Unable to allocate
