what i don't understand is why dbmail-lmtpd crashs once each day
around the same time, even if i restart it at 3:00 AM, in case of
imap/pop3 that could be a scheduled client always doing the same
bad thing but hardly for LMTP

dbmail-utils runs at a completly different time

frankly i guess i could start strace with a cronjob between 13:00 and 14:00
to a file with date/time because it's that predictable

Apr  5 13:16:06 mail systemd[1]: dbmail-lmtpd.service holdoff time over, 
scheduling restart.
Apr  5 13:16:05 mail systemd[1]: Unit dbmail-lmtpd.service entered failed state.
Apr  4 13:14:32 mail systemd[1]: dbmail-lmtpd.service holdoff time over, 
scheduling restart.
Apr  4 13:14:31 mail systemd[1]: Unit dbmail-lmtpd.service entered failed state.

Am 03.04.2014 20:45, schrieb Reindl Harald:
> Am 03.04.2014 20:09, schrieb Peter Milesson:
>> I'm quite sure it's not the size of the mailbox. I've got a few servers 
>> using dbmail for years, and the largest
>> mailbox yet holds about 60GB of mail. The other ones ranging from about one 
>> GB up to about 35GB.
>>
>> I'm using postfix (2.11 stable) + dbmail (3.1.13) + MariaDB (5.5.34) + 
>> amavis + spamassassin. I must say dbmail
>> 3.1.13 is rock solid, as is postfix
> 
> dbmail-lmtpd is not, but it does not happen often enough
> to debug it further nor that it becomes a large problem
> 
> at least if you have some monitoring with auto-restart
> the interesting is that this started on 2014-03-30 and
> dbmail 3.1.13 was updated 2014-03-13 on that machine
> 
> see logs below
> 
> maybe it has something to do with that ones, maybe not
> there is a thread from me where it affected 4 messages
> with today it has grown to 6 messages
> EEEEEEOk. Found [6] missing envelope values.
> EEEEEEOk. Found [6] un-cached physmessages.
> 
> ____________________________________________________________
> 
> 03.04.2014
> 2014-04-03 13:10:10   dbmail-lmtpd.service holdoff time over, scheduling 
> restart.
> 2014-04-03 13:10:09   Unit dbmail-lmtpd.service entered failed state.
> 2014-04-03 13:10:09   dbmail-lmtpd.service: main process exited, code=killed, 
> status=11/SEGV
> 
> 02.04.2014
> 2014-04-02 13:07:33   dbmail-lmtpd.service holdoff time over, scheduling 
> restart.
> 2014-04-02 13:07:32   Unit dbmail-lmtpd.service entered failed state.
> 2014-04-02 13:07:32   dbmail-lmtpd.service: main process exited, code=killed, 
> status=11/SEGV
> 
> 01.04.2014
> 2014-04-01 13:01:13   dbmail-lmtpd.service holdoff time over, scheduling 
> restart.
> 2014-04-01 13:01:12   Unit dbmail-lmtpd.service entered failed state.
> 2014-04-01 13:01:12   dbmail-lmtpd.service: main process exited, code=killed, 
> status=11/SEGV
> 
> 31.03.2014
> 2014-03-31 13:00:10   dbmail-lmtpd.service holdoff time over, scheduling 
> restart.
> 2014-03-31 13:00:09   Unit dbmail-lmtpd.service entered failed state.
> 2014-03-31 13:00:09   dbmail-lmtpd.service: main process exited, code=killed, 
> status=11/SEGV
> 
> 30.03.2014
> 2014-03-30 13:13:38   dbmail-lmtpd.service holdoff time over, scheduling 
> restart.
> 2014-03-30 13:13:37   Unit dbmail-lmtpd.service entered failed state.
> 2014-03-30 13:13:37   dbmail-lmtpd.service: main process exited, code=killed, 
> status=11/SEGV
> 2014-03-30 12:56:31   dbmail-lmtpd.service holdoff time over, scheduling 
> restart.
> 2014-03-30 12:56:30   Unit dbmail-lmtpd.service entered failed state.
> 2014-03-30 12:56:30   dbmail-lmtpd.service: main process exited, code=killed, 
> status=11/SEGV

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Reply via email to