fre, 22.07.2005 kl. 02.22 skrev Gary V:
[...]
Nice work, looks like you have something in common with SuSE 9.1:
From http://www.ijs.si/software/amavisd/#faq-trouble :
Michael W Cocke writes: the reason DB_PRIVATE was enabled is that
SuSE 9.1 ships with BDB built wrong! Download BDB 4.2.52
Hi,
I updated some rpms and my kernel, and now Amavis won't start.
I was running 2.2.0, but since it stopped working, I tried to upgrade to
2.3.2, but got exactly the same error (only different line):
Jul 21 23:08:32 servername /usr/sbin/amavisd[13301]: No secondary av
scanner: KasperskyLab
Hi,
I updated some rpms and my kernel, and now Amavis won't start.
I was running 2.2.0, but since it stopped working, I tried to upgrade to
2.3.2, but got exactly the same error (only different line):
Jul 21 23:08:32 servername /usr/sbin/amavisd[13301]: No secondary av
scanner: KasperskyLab
Cariad wrote:
Hi,
I updated some rpms and my kernel, and now Amavis won't start.
I was running 2.2.0, but since it stopped working, I tried to upgrade to
2.3.2, but got exactly the same error (only different line):
Jul 21 23:08:32 servername /usr/sbin/amavisd[13301]: No secondary av
Hi,
I'm currently running Whitebox Linux, kernel 2.4.21-32.0.1.ELsmp.
I have seen some bdb errors on Whitebox after upgrading the db4 RPMs. The
problem seemed to be that the updates have been compiled with different
options. Downgrading the db4 RPMs solved the problem (in this case with
If you need to get your server running, you can set:
$enable_db = 0;
This will buy you some time until the cause of the problem can be
properly determined.
Gary V
Thank you Gary.
However, it seems like I already have solved the problem.
The problem lied in an updated db4 RPM package.
It
Cariad wrote:
If you need to get your server running, you can set:
$enable_db = 0;
This will buy you some time until the cause of the problem can be
properly determined.
Gary V
Thank you Gary.
However, it seems like I already have solved the problem.
The problem lied in an
