On 12/13/05, Mark Martinec [EMAIL PROTECTED] wrote:
Looks like a problem with berkeley db (libdb). What version of libdb are you
using - it is logged during startup like:
amavis[xxx]: Creating db in /var/amavis/db/; BerkeleyDB 0.27, libdb 4.3
Looks like I've got an older version- it must
Hello,
I've got several postfix/amavis filtering types of installs setup. On
my most recent one, I've hit a snag that I haven't yet been able to
figure out. This particular server handles about 70k messages per day,
which is generally fine. Anyhow, things will churn along fine for days
and then
falz,
I've got several postfix/amavis filtering types of installs setup. On
my most recent one, I've hit a snag that I haven't yet been able to
figure out. This particular server handles about 70k messages per day,
which is generally fine. Anyhow, things will churn along fine for days
and
Mark Martinec wrote:
using - it is logged during startup like:
amavis[xxx]: Creating db in /var/amavis/db/; BerkeleyDB 0.27, libdb 4.3
The last time this was reported it turned out it was with an old version
of libdb. If this is also true in your case, try with a more recent version
Chris,
Is there some sort of compile time arg to use? Just I removed my older
db port, and installed 4.3 - recompliled Postfix to use it, then rebuilt
Amavis. Seems Ami still calls in db3
You may need to reinstall Perl module BerkeleyDB after upgrading libdb.
No changes and no reinstall on
Mark Martinec wrote:
Chris,
Is there some sort of compile time arg to use? Just I removed my older
db port, and installed 4.3 - recompliled Postfix to use it, then rebuilt
Amavis. Seems Ami still calls in db3
You may need to reinstall Perl module BerkeleyDB after upgrading libdb.
No
