SpamAssassin: Problem applying update

Wanabo

Verified User
Joined
Jan 19, 2013
Messages
339
Since a couple of days I noticed these mail messages:

Cron <root@server> /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log

Use of uninitialized value in regexp compilation at /usr/share/perl5/Mail/SpamAssassin/Plugin/HashBL.pm line 76, <DATA> line 717.
config: failed to parse line, skipping, in "/etc/mail/spamassassin/v342.pre": parse_dkim_uris 1
12-Nov-2018 06:06:40: SpamAssassin: Problem applying update - pre files failed lint check


Anyone else has this too? How to fix this?
 
Hello,

Try and see whether or not it helps:

Code:
cd /usr/local/directadmin/custombuild
./build update
./build set spamassassin yes
./build set sa_update daily
./build spamassassin


sa-update -D
 
Hi Alex,

Thanks for helping!
Executed your suggested steps.

[root@join custombuild]# sa-update -D
Nov 12 19:58:53.725 [32202] dbg: logger: adding facilities: all
Nov 12 19:58:53.725 [32202] dbg: logger: logging level is DBG
Nov 12 19:58:53.726 [32202] dbg: generic: SpamAssassin version 3.4.2
Nov 12 19:58:53.726 [32202] dbg: generic: Perl 5.016003, PREFIX=/usr, DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/mail/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin
Nov 12 19:58:53.726 [32202] dbg: config: timing enabled
Nov 12 19:58:53.728 [32202] dbg: config: score set 0 chosen.
Nov 12 19:58:53.732 [32202] dbg: generic: sa-update version 3.4.2 / svn1840377
Nov 12 19:58:53.732 [32202] dbg: generic: using update directory: /var/lib/spamassassin/3.004002
Nov 12 19:58:53.869 [32202] dbg: diag: perl platform: 5.016003 linux
Nov 12 19:58:53.869 [32202] dbg: diag: [...] module installed: Digest::SHA, version 5.95
Nov 12 19:58:53.869 [32202] dbg: diag: [...] module installed: HTML::parser, version 3.71
Nov 12 19:58:53.869 [32202] dbg: diag: [...] module installed: Net::DNS, version 0.72
Nov 12 19:58:53.869 [32202] dbg: diag: [...] module installed: NetAddr::IP, version 4.079
Nov 12 19:58:53.869 [32202] dbg: diag: [...] module installed: Time::HiRes, version 1.9725
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: Archive::Tar, version 2.06
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: IO::Zlib, version 1.10
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: Digest::SHA1, version 2.13
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: MIME::Base64, version 3.13
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: DB_File, version 1.835
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: Net::SMTP, version 2.31
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: Mail::SPF, version v2.008
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: Geo::IP, version 1.45
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: Net::CIDR::Lite, version 0.21
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: Razor2::Client::Agent, version 2.84
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: IO::Socket::IP, version 0.37
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: IO::Socket::INET6, version 2.72
Nov 12 19:58:53.870 [32202] dbg: diag: [...] module installed: IO::Socket::SSL, version 2.027
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: Compress::Zlib, version 2.061
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: Mail::DKIM, version 0.39
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: DBI, version 1.636
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: Getopt::Long, version 2.4
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: LWP::UserAgent, version 6.05
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: HTTP::Date, version 6.02
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: Encode::Detect::Detector, version 1.01
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: Net::patricia, version 1.22
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module installed: Net::DNS::Nameserver, version 1096
Nov 12 19:58:53.871 [32202] dbg: diag: [...] module not installed: BSD::Resource ('require' failed)
Nov 12 19:58:53.872 [32202] dbg: gpg: Searching for 'gpg'
Nov 12 19:58:53.872 [32202] dbg: util: current PATH is: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Nov 12 19:58:53.872 [32202] dbg: util: executable for gpg was found at /usr/bin/gpg
Nov 12 19:58:53.872 [32202] dbg: gpg: found /usr/bin/gpg
Nov 12 19:58:53.872 [32202] dbg: gpg: release trusted key id list: 5E541DCFDC4056A61A5244EC45 0C2B1D7175B85297824F434CE
Nov 12 19:58:53.873 [32202] dbg: util: secure_tmpfile created a temporary file /tmp/.spamassassin32202r5rCqhtmp
Nov 12 19:58:53.873 [32202] dbg: channel: attempting channel updates.spamassassin.org
Nov 12 19:58:53.873 [32202] dbg: channel: using existing directory /var/lib/spamassassin/3.004002/updates_spamassassin_org
Nov 12 19:58:53.873 [32202] dbg: channel: channel cf file /var/lib/spamassassin/3.004002/updates_spamassassin_org.cf
Nov 12 19:58:53.873 [32202] dbg: channel: channel pre file /var/lib/spamassassin/3.004002/updates_spamassassin_org.pre
Nov 12 19:58:53.873 [32202] dbg: channel: metadata version = 1846340, from file /var/lib/spamassassin/3.004002/updates_spamassassin_org.cf
Nov 12 19:58:53.883 [32202] dbg: dns: 2.4.3.updates.spamassassin.org => 1846340, parsed as 1846340
Nov 12 19:58:53.883 [32202] dbg: channel: current version is 1846340, new version is 1846340, skipping channel
Nov 12 19:58:53.883 [32202] dbg: diag: updates complete, exiting with code 1
[root@server custombuild]#

(trusted key modified)
All seems well except for module not installed: BSD::Resource

Thank you.


Edit: installed BSD::Resource just in case.
Nov 12 20:18:31.660 [1114] dbg: diag: [...] module installed: BSD::Resource, version 1.2907
 
Last edited:
I was hoping everything was fixed now.

Tonight this mail message came:

Cron <root@server> /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log

/bin/sh: /usr/share/spamassassin/sa-update.cron: No such file or directory
 
You should delete spamassassin installed from a package of your OS. And then re-install it with custombuild.


Code:
yum remove -y spamassassin

Code:
cd /usr/local/directadmin/custombuild
./build update
./build set spamassassin yes
./build set sa_update daily
./build spamassassin
 
I don't remember to installed spamassassin with yum, but this was indeed the case. (I've got 2 identical servers setup and the other server spamassassin was not installed with yum.)
Followed the above steps. I'll check my mail tomorrow to see if the system throws a message.

Thanks for the great support.
 
Yesterday I wasn't focused to check for "fail" messages. But if there there was one, I would have spotted it.
Today I was extra focused on finding a fail message, but there was none.

Problem solved! ;)

Tanks for the help.
 
Back
Top