Hi,
No I have made no changes to exim but FreeBSD has been patched using the
new binary update tool. Though I do not recall having applied any
updates during the last week or two.
So far a I have applied the latest patches to FreeBSD bringing it to
7.1-p4, rebooted and dumped the exim db files and so far this looks to
have stabilised the system but then it was stable for some time before
this problem occurred.
David
Graeme Fowler wrote:
> [snipped growing list of subscribers getting copies...]
>
> On Thu, 2009-04-30 at 07:52 +0900, Randy Bush wrote:
>> nope. still fails on a number of systems.
>
> Damn.
>
>> i am assuming there is a freebsd problem under this and filed pr/134011.
>
> Useful, thanks.
>
>> but exim_tidydb is the only code which tickles it. so i have to wonder.
>
> Perhaps it's the only binary you've got which accesses the DB files in
> the way which tickles them? Just a thought. It's interesting that David
> Robertson is reporting a similar problem, but the symptoms differ -
> probably due to the number of read/write ops to the affected DB file,
> triggered by differences in volume of mail, queue runners and their
> frequency, and his retry rules.
>
> I assume that neither of you have changed Exim in any way at all
> immediately before these errors started happening?
>
> Graeme
>
>
>
>
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.287 / Virus Database: 270.12.9/2087 - Release Date: 04/29/09 18:03:00
>
