Re: mysql errors after 3.1.8 upgrade
On Thu, Feb 22, 2007 at 11:29:30AM -0500, Bowie Bailey wrote: spamd[16137]: Can't locate DBD/mysql.pm in @INC ... spamd[16137]: Can't locate Tie/Cache.pm in @INC ... spamd[16137]: Can't locate Tie/Cache.pm in @INC ... spamd[16137]: BEGIN failed--compilation aborted at (eval 759) line 1. My SA is not configured to use MySQL and I can't find any reference to it in the config files. Where are these errors coming from? Are you loading a plugin that uses these modules? You need to take a look at how you've configured SA to figure out where these modules are trying to be loaded. -- Randomly Selected Tagline: `Ford, you're turning into a penguin. Stop it.' - Arthur experiences the improbability drive at work. pgpYjdmToXGpy.pgp Description: PGP signature
RE: mysql errors after 3.1.8 upgrade
Theo Van Dinter wrote: On Thu, Feb 22, 2007 at 11:29:30AM -0500, Bowie Bailey wrote: spamd[16137]: Can't locate DBD/mysql.pm in @INC ... spamd[16137]: Can't locate Tie/Cache.pm in @INC ... spamd[16137]: Can't locate Tie/Cache.pm in @INC ... spamd[16137]: BEGIN failed--compilation aborted at (eval 759) line 1. My SA is not configured to use MySQL and I can't find any reference to it in the config files. Where are these errors coming from? Are you loading a plugin that uses these modules? You need to take a look at how you've configured SA to figure out where these modules are trying to be loaded. Ok. FuzzyOCR appears to be the culprit. And it was happening prior to the upgrade, I just didn't notice. The FuzzyOCR installation docs only list DBD::mysql as required if you are using it for the hash database and I've got that set to use digest_db. FuzzyOCR.cf: # 2 ... use digest_db w/digest_hash import (see requirements, # recommended) focr_enable_image_hashing 2 So why is it looking for DBD::mysql? -- Bowie
Re: mysql errors after 3.1.8 upgrade
Bowie Bailey wrote: [snip] The FuzzyOCR installation docs only list DBD::mysql as required if you are using it for the hash database and I've got that set to use digest_db. FuzzyOCR.cf: # 2 ... use digest_db w/digest_hash import (see requirements, # recommended) focr_enable_image_hashing 2 So why is it looking for DBD::mysql? You are using a very old pre-release of version 3.5. That problem was fixed a few months ago, before 3.5.1 came out. -- René Berber
RE: mysql errors after 3.1.8 upgrade
René Berber wrote: Bowie Bailey wrote: [snip] The FuzzyOCR installation docs only list DBD::mysql as required if you are using it for the hash database and I've got that set to use digest_db. FuzzyOCR.cf: # 2 ... use digest_db w/digest_hash import (see requirements, # recommended) focr_enable_image_hashing 2 So why is it looking for DBD::mysql? You are using a very old pre-release of version 3.5. That problem was fixed a few months ago, before 3.5.1 came out. No, I'm using the latest development build of 3.5.1 from http://fuzzyocr.own-hero.net/wiki/Downloads. I upgraded to 3.5.1 from 2.3b less than a month ago. -- Bowie
Re: mysql errors after 3.1.8 upgrade
Bowie Bailey wrote: [snip] No, I'm using the latest development build of 3.5.1 from http://fuzzyocr.own-hero.net/wiki/Downloads. I upgraded to 3.5.1 from 2.3b less than a month ago. Perhaps you didn't upgrade everything, the precise location of the error you are seeing is in file FuzzyOcr/Config.pm, I think you have the old one, or... Somebody else had a report just like yours (on the FuzzyOcr list), with the correct version, but it seems he was calling mySQL from somewhere else in the spamassassin configuration (Bayes perhaps?). -- René Berber
Re: mysql errors after 3.1.8 upgrade
Bowie Bailey wrote: [snip] No, I'm using the latest development build of 3.5.1 from http://fuzzyocr.own-hero.net/wiki/Downloads. I upgraded to 3.5.1 from 2.3b less than a month ago. Perhaps you didn't upgrade everything, the precise location of the error you are seeing is in file FuzzyOcr/Config.pm, I think you have the old one, or... Somebody else had a report just like yours (on the FuzzyOcr list), with the correct version, but it seems he was calling mySQL from somewhere else in the spamassassin configuration (Bayes perhaps?). The way to figure this out is by running `spamassassin -x -t -D FuzzyOcr sample.eml` and see if FuzzyOcr is really using the mySQL module or not. Leave out the -D part if you want to find who is using what. -- René Berber
RE: mysql errors after 3.1.8 upgrade
René Berber wrote: Bowie Bailey wrote: [snip] No, I'm using the latest development build of 3.5.1 from http://fuzzyocr.own-hero.net/wiki/Downloads. I upgraded to 3.5.1 from 2.3b less than a month ago. Perhaps you didn't upgrade everything, the precise location of the error you are seeing is in file FuzzyOcr/Config.pm, I think you have the old one, or... No, the FuzzyOcr/Config.pm file is identical to the one in the tarball. Somebody else had a report just like yours (on the FuzzyOcr list), with the correct version, but it seems he was calling mySQL from somewhere else in the spamassassin configuration (Bayes perhaps?). I'm open to the possibility that the problem may lie elsewhere, but the problem does not happen without FuzzyOcr. # service spamd restart (Produces errors in the log) # mv FuzzyOcr.cf FuzzyOcr.cf.hold # service spamd restart (no errors) # mv FuzzyOcr.cf.hold FuzzyOcr.cf # service spamd restart (Produces errors in the log) -- Bowie
Re: mysql errors after 3.1.8 upgrade
On 02/22/07 Bowie wrote: spamd[16137]: Can't locate DBD/mysql.pm in @INC ... spamd[16137]: Can't locate Tie/Cache.pm in @INC ... spamd[16137]: Can't locate Tie/Cache.pm in @INC ... spamd[16137]: BEGIN failed--compilation aborted at (eval 759) line 1. root# perl -MCPAN -e shell cpan[1] install DBD::mysql Tie::Cache maciek -- |_|0|_| Maciej Friedel [EMAIL PROTECTED] |_|_|0| http://wwv.pl - usługi hostingowe |0|0|0| http://eprogram.pl - projektowanie stron www
