Alan,
I have installed DBD::mysql and it still doesn't work. The install file says that DBD::mSQL is required and the options that I specified when we installed it was for mysql (as the mSQL diver is covers it as well).
It's funny though that AWL is logging to the DB. Also, something to note, is that in production we are running 3.0.1 and this is 3.0.2. Maybe it's not required and the code is just broken. Unfortunately my older dev environment is down otherwise I would try upgrading the 3.0.2 to see if it has the same problems.
Here is the specific error:
Apr 12 17:22:44 pxtoakdev04 spamd[3378]: Use of uninitialized value in
concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/BayesStore/SQL.pm line
157, <GEN2> line 2. Apr 12 17:22:44 pxtoakdev04 spamd[3378]: Use of uninitialized value in
numeric ne (!=) at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/BayesStore/SQL.pm line
159, <GEN2> line 2. Apr 12 17:22:44 pxtoakdev04 spamd[3378]: Use of uninitialized value in
concatenation (.) or string at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/BayesStore/SQL.pm line
160, <GEN2> line 2. Apr 12 17:22:44 pxtoakdev04 spamd[3378]: bayes: Database version is
different than we understand (3), aborting! at
/usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/BayesStore/SQL.pm line
160, <GEN2> line 2.
Local.cf
auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList user_awl_dsn DBI:mysql:spamassassin:10.0.0.41 user_awl_sql_username spamassassinuser user_awl_sql_password spamassassinpass
bayes_store_module Mail::SpamAssassin::BayesStore::SQL bayes_sql_dsn DBI:mysql:spamassassin:10.0.0.41 bayes_sql_username spamassassinuser bayes_sql_password spamassassinpass
Gary,
these calls (DBI:mysql:spamassassin....) are definitely telling the system to use DBD::mysql (not DBD::mSQL)
based on this line: Apr 12 17:22:44 pxtoakdev04 spamd[3378]: bayes: Database version is different than we understand (3), aborting! at
it looks like the database either isn't configured properly or it's corrupted.
try running sa-learn --dump magic to see what it reports, and assuming it fails you may then want to try sa-learn -D --lint
are both your production (3.0.1) and this new (3.0.2) machine pointing to the same database?
alan
