From: Greg Matthews
Date: 2006-07-20 05:47:15 -0400
Subject: Re: Experiences with caching and milter-ahead
More information..: http://www.milter.info/#Support
Sebastian Hagedorn wrote:
> One other thing: We use four servers for the milter in a load-balanced
> cluster. On one of of these I had a corrupted cache, i.e. all updates
> failed. We use RHEL 3 with its db4-4.1.25-8.1 RPM. db_verify shows:
not had any problem with cache corruption. I have come across the issue
of a target MTA rejecting a mail due to a config problem and then that
reject is cached at my relay after the problem is solved on the target
MTA until the ttl expires. This is unavoidable AFAICT.
The only other problem I've seen with milter-ahead is resource
exhaustion. Unless there are tight limits on connection rates and number
of connections etc setup within the sendmail.cf, milter-ahead can run
out of process space and die. This is a sendmail config issue rather
than a milter-ahead one tho.
> db_verify /tmp/milter-ahead.db
> db_verify: Page 2053: hash page has bad prev_pgno
> db_verify: Page 514: hash page has bad prev_pgno
> db_verify: Page 2054: hash page has bad prev_pgno
> db_verify: Page 2036: non-empty page in unused hash bucket 2032
> db_verify: Page 0: page 2053 encountered a second time on free list
> db_verify: DB->verify: /tmp/milter-ahead.db: DB_VERIFY_BAD: Database
> verification failed
> I just deleted it, but I wonder if this is a common problem?
> Cheers, Sebastian Hagedorn
Greg Matthews 01491 692445
Head of UNIX/Linux, iTSS Wallingford
This message (and any attachments) is for the recipient only. NERC
is subject to the Freedom of Information Act 2000 and the contents
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.
Copyright 2009, 2012 by SnertSoft. All rights reserved.