Ok, I unblocked that IP and started Dovecot with
ulimit -c unlimited && /usr/local/sbin/dovecot
and will see if that IP will return.
But I totally forgot I am using Google`s perf-tools (http://code.google.com/p/google-perftools/) tcmalloc library. Maybe that library is faulty and/or incompatible with Dovecot?
export LD_PRELOAD=/usr/local/lib/libtcmalloc.so
However, I switched to Google`s libtcmalloc.so long time ago, and dovecot was running just fine until today. MySQL, nginx, clamav and postfix are running fine too.
P.S. I got 2 responses from you :)
Timo Sirainen wrote:
Run ulimit -c unlimited before starting dovecot. And note that several distributions override the ulimit if you use /etc/init.d/dovecot to start it. Newer Dovecot versions (v1.1.9+) say at startup if core dumps are disabled.
On Thu, 2009-04-09 at 23:06 +0300, Martins Lazdans wrote:
No, there is no core dumps. I believe I can somehow enable to dump core?
Timo Sirainen wrote:
On Thu, 2009-04-09 at 21:37 +0300, Martins Lazdans wrote:
Hello!
I have used Dovecot for more than a year without problems, but today it just crashed with this message:
dovecot: Apr 09 21:23:38 Panic: file mempool-system.c: line 104 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Did Dovecot happen to write a core file somewhere? Should be in base_dir (e.g. /var/run/dovecot)? A gdb backtrace would be helpful.
-- Martins Lazdans