Author: Leonardo Boselli Date: To: J. CC: exim-users@exim.org Subject: Re: [exim] Failed to get write lock for
/var/spool/exim4/db/retry.lockfile: timed out
Simple reply: just delete /var/log/exim4/paniclog .
such file is kept to be read by admin to take action.
But even if the error occurred only once the messge is sent untill the log
has not been cleared.
On Sat, 21 Mar 2015, J. wrote: > Hello exim peeps,
> Sorry to bug you with a likely non-issue, but I've been getting this message from root every day:
> Subject:exim paniclog on me.myserver.com has non-zero size
> Body:
> exim paniclog /var/log/exim4/paniclog on me.myserver.com has non-zero size, mail system might be broken. The last 10 lines are quoted below.
>
> 2015-03-04 06:29:05 1YUEMX-0002oW-Fs Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed out
> ------Any suggestions on how to address the issue? Thanks!
--
Leonardo Boselli
Dipartimento ingegneria Civile e Ambientale UNIFI
tel +39 0552758808