I'm now seeing these crashes in the indexing code:
May 10 12:22:32 tornado.reub.net dovecot: master: Dovecot v2.2.17.rc1
(3903badc4ee0+) starting up for imap, lmtp, sieve
...
May 10 13:07:50 tornado.reub.net dovecot: indexer: Error: Indexer worker
disconnected, discarding 1 requests for reuben
May 10 13:07:50 tornado.reub.net dovecot: indexer-worker(reuben): Fatal:
master: service(indexer-worker): child 18532 killed with signal 11 (core
not dumped)
Every time a delivery happens or mail is moved the indexer crashes out.
It doesn't seem to have any visible end user impact though.
How do I go about debugging this further? How do I go about getting a
backtrace on what is essentially a child process that doesn't produce a
core? (Note that my installation normally does produce cores when it
crashes, so there's something different about these indexer processes..)
Reuben
On 10/05/2015 3:41 AM, Timo Sirainen wrote:
http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig
