On 5.1.2012, at 2.24, Daniel L. Miller wrote: > I thought I had cleared out the corruption I had before - perhaps I was > mistaken. What steps should I take to help locate these issues? Currently > using 2.1rc1. I see the following errors in my logs, including out of memory > and message size issues (at 15:30): .. > Jan 4 05:17:17 bubba dovecot: master: Error: service(indexer-worker): child > 10896 returned error 83 (Out of memory (vsz_limit=256 MB, you may need to > increase it)) > Jan 4 06:17:17 bubba dovecot: indexer-worker(us...@domain.com): Fatal: > pool_system_realloc(134217728): Out of memory
The problem is clearly that index-worker's vsz_limit is too low. Increase it (or default_vsz_limit).
