If you don't want to restart the service manually by hand to recover
from a crash you can always take advantage of daemon tools, by dj
berstien. It is a set of tools that monitor a process and restart it
in the event that the process stops working.
That is a temporary fix until a patch is released to fix the
problem....
cr.yp.to/daemontools.html
On 04/02/2012 at 6:43 AM, ITronic Harald Leithner wrote:hmm... daily
restarting is a good workaround for now.
thx
Harald
Am 02.04.2012, 12:32 Uhr, schrieb Reindl Harald :
> imapd has currently memory leaks and is growing over
> some hundret MB up to > 1 GB memory after few days
>
> the crash is easy to solve by systemd-autorestart
> last sunday it stopped accepting connections around
> 12AM and i happily was in front of my machine for
> restart the daemon - in this state all mail-clients
> start to ask for the password again :-(
>
> i am restarting the dbmail-imapd currently each night
> at 3:00 AM since this day to have it rock stable
> there is dovecot as proxy in front reconnect without
> users notice anything
>
> Am 02.04.2012 12:27, schrieb ITronic Harald Leithner:
>> Hi,
>>
>> today my imapd crashed with the following message:
>> Apr 2 12:10:26 mailstore kernel: [4393934.966925]
dbmail-imapd[21452]:
>> segfault at 0 ip 00007faead3468ea sp
>> 00007fae9b5b1c20 error 4 in libdbmail.so.0.0.0[7faead329000+5c000]
>>
>> I think with this informations no body can help me, so its just for
the
>> record.
>>
>> Regards,
>> Harald
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
