Spamassassin unknown error code 3 from sa update

Why has this just started happening? OS CentOS Linux 7.9.2009 (Core) Plesk Obsidian Version 18.0.34, last updated on Mar 12, 2021 07:00 PM Started happening 11 Mar 2021 with Plesk 18.0.33. Upgraded to 18.0.34 and still happening. There have been no other changes. Email subject: Cron...

OS CentOS Linux 7.9.2009 (Core)
Plesk Obsidian
Version 18.0.34, last updated on Mar 12, 2021 07:00 PM

Started happening 11 Mar 2021 with Plesk 18.0.33.
Upgraded to 18.0.34 and still happening.
There have been no other changes.

Email subject:
Cron <[email protected]********> /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log
Email Message:
channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed
13-Mar-2021 05:20:29: SpamAssassin: Unknown error code 3 from sa-update
File /var/log/sa-update.log Contents

Mar 13 03:46:29.497 [11735] dbg: logger: adding facilities: all
Mar 13 03:46:29.497 [11735] dbg: logger: logging level is DBG
Mar 13 03:46:29.497 [11735] dbg: generic: SpamAssassin version 3.4.0
Mar 13 03:46:29.497 [11735] 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
Mar 13 03:46:29.497 [11735] dbg: config: timing enabled
Mar 13 03:46:29.497 [11735] dbg: config: score set 0 chosen.
Mar 13 03:46:29.499 [11735] dbg: generic: sa-update version svn1475932
Mar 13 03:46:29.499 [11735] dbg: generic: using update directory: /var/lib/spamassassin/3.004000
Mar 13 03:46:29.539 [11735] dbg: diag: perl platform: 5.016003 linux
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Digest::SHA1, version 2.13
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: HTML::parser, version 3.71
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Net::DNS, version 0.72
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: NetAddr::IP, version 4.069
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Time::HiRes, version 1.9725
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Archive::Tar, version 1.92
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: IO::Zlib, version 1.10
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Digest::SHA1, version 2.13
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: MIME::Base64, version 3.13
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: DB_File, version 1.83
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Net::SMTP, version 2.31
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Mail::SPF, version v2.008
Mar 13 03:46:29.539 [11735] dbg: diag: […] module not installed: Geo::IP (‘require’ failed)
Mar 13 03:46:29.539 [11735] dbg: diag: […] module not installed: Razor2::Client::Agent (‘require’ failed)
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: IO::Socket::IP, version 0.21
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: IO::Socket::INET6, version 2.69
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: IO::Socket::SSL, version 1.94
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Compress::Zlib, version 2.061
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Mail::DKIM, version 0.39
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: DBI, version 1.627
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Getopt::Long, version 2.4
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: LWP::UserAgent, version 6.05
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: HTTP::Date, version 6.02
Mar 13 03:46:29.539 [11735] dbg: diag: […] module installed: Encode::Detect, version 1.01
Mar 13 03:46:29.539 [11735] dbg: diag: […] module not installed: Net::patricia (‘require’ failed)
Mar 13 03:46:29.539 [11735] dbg: gpg: Searching for ‘gpg’
Mar 13 03:46:29.539 [11735] dbg: util: current PATH is: /sbin:/bin:/usr/sbin:/usr/bin
Mar 13 03:46:29.540 [11735] dbg: util: executable for gpg was found at /bin/gpg
Mar 13 03:46:29.540 [11735] dbg: gpg: found /bin/gpg
Mar 13 03:46:29.540 [11735] dbg: gpg: release trusted key id list: 5E541DC959CB8BAC7C78DFDC4056A61A5244EC45 0C2B1D7175B852C64B3CDC716C55397824F434CE
Mar 13 03:46:29.540 [11735] dbg: channel: attempting channel updates.spamassassin.org
Mar 13 03:46:29.540 [11735] dbg: channel: using existing directory /var/lib/spamassassin/3.004000/updates_spamassassin_org
Mar 13 03:46:29.540 [11735] dbg: channel: channel cf file /var/lib/spamassassin/3.004000/updates_spamassassin_org.cf
Mar 13 03:46:29.540 [11735] dbg: channel: channel pre file /var/lib/spamassassin/3.004000/updates_spamassassin_org.pre
Mar 13 03:46:29.540 [11735] dbg: channel: metadata version = 1887469, from file /var/lib/spamassassin/3.004000/updates_spamassassin_org.cf
Mar 13 03:46:29.544 [11735] dbg: dns: 0.4.3.updates.spamassassin.org => 1887469, parsed as 1887469
Mar 13 03:46:29.544 [11735] dbg: channel: current version is 1887469, new version is 1887469, skipping channel
Mar 13 03:46:29.544 [11735] dbg: diag: updates complete, exiting with code 1
channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed
13-Mar-2021 05:20:29: SpamAssassin: Unknown error code 3 from sa-update

Источник

Topic: Daily Spamassassin update reports error  (Read 7585 times)

0 Members and 1 Guest are viewing this topic.

Hi, seems the spamassassin source in the script is offline.

I see we have Version 3.4.0 but there is already 3.4.4 or 3.4.5 out

i get the daily mails from the update report and it tells me:

channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed
13-M�r-2021 06:08:30: SpamAssassin: Unknown error code 3 from sa-update
Any way to fix this, i know we can play around and manually install and update spamassassin but i don’t think this is what we should do, maybe there is a reason for the old version in the repo.

Maybe this could be fixed/updated in one of the CWP updates we get.

Thanks


Logged

Offline

*

i have the same issue since 5 days or so

channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed
14-Mar-2021 04:52:56: SpamAssassin: Unknown error code 3 from sa-update

running centos 7 with latests updates.

« Last Edit: March 14, 2021, 02:11:22 PM by Dutch_Mike »


Logged

Hi, I would disable the mirror in the config in /etc/mail/spamassassin/


Logged

Ok thanks, i will give it a try.


Logged

Offline

*

Hi, I would disable the mirror in the config in /etc/mail/spamassassin/

Hello, is that the only fix right now? Would that somehow mess up the spamassassin updates after disabling the mirror?


Logged

The problem has arisen because CWP uses an outdated version of Spamassasin.  The Sought server pulled all updates for this old version, as they no longer support it.  CWP needs to update to the latest version of SA to correct this error.  The only option to disable the errors at this point, is to delete the mirror.


Logged

Offline

*

Spamassassin in CWP is v3.4.0?
According to this:
https://spamassassin.apache.org/news.html
3.4.0 was released on 2014!!!

Why CWP don’t update this things? I mean, 7 years has passed….
And I can see that Postfix is old, too.

Uh….  :(


Logged


Logged


Logged

Источник
  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Official Flavours Support
  • General Help
  • Spamassassin, daily error — sa-update failed for unknown reasons

  1. Spamassassin, daily error — sa-update failed for unknown reasons

    Hello

    Ubuntu 14.04 LTS.

    For the last couple of weeks I’ve received a daily email:

    /etc/cron.daily/spamassassin:
    channel: could not find working mirror, channel failed sa-update failed for unknown reasons

    If I run /etc/cron.daily/spamassassin manually it succeeds. if I run it via the cron job (copy the /etc/cron.daily/spamassassin to a new folder /tmp/x/ and then run run-parts —report /tmp/x/) it fails:

    Code:

    Jul  9 11:26:00.311 [20148] dbg: channel: file /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY is too old, refreshing mirrors file
Jul  9 11:26:00.311 [20148] dbg: channel: DNS lookup on mirrors.updates.spamassassin.org
Jul  9 11:26:00.503 [20148] dbg: http: url: http://spamassassin.apache.org/updates/MIRRORED.BY
Jul  9 11:26:00.503 [20148] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY, replace
Jul  9 11:26:00.503 [20148] dbg: util: executable for curl was found at /usr/bin/curl
Jul  9 11:26:00.503 [20148] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o MIRRORED.BY -- http://spamassassin.apache.org/updates/MIRRORED.BY
Jul  9 11:26:00.730 [20148] dbg: http: process [20149], exit status: 5888
Jul  9 11:26:00.730 [20148] dbg: channel: no mirror data available for channel updates.spamassassin.org from http://spamassassin.apache.org/updates/MIRRORED.BY
error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file
Jul  9 11:26:00.730 [20148] dbg: channel: reading MIRRORED.BY file /var/lib/spamassassin/3.004000/updates_spamassassin_org/MIRRORED.BY
Jul  9 11:26:00.730 [20148] dbg: channel: parsing MIRRORED.BY file for channel updates.spamassassin.org
Jul  9 11:26:00.731 [20148] dbg: channel: found mirror http://sa-update.dnswl.org/ weight=1
Jul  9 11:26:00.731 [20148] dbg: channel: found mirror http://www.sa-update.pccc.com/ weight=5
Jul  9 11:26:00.731 [20148] dbg: channel: found mirror http://sa-update.secnap.net/ weight=5
Jul  9 11:26:00.731 [20148] dbg: channel: found mirror http://sa-update.space-pro.be/ weight=1
Jul  9 11:26:00.731 [20148] dbg: channel: selected mirror http://www.sa-update.pccc.com
Jul  9 11:26:00.732 [20148] dbg: http: url: http://www.sa-update.pccc.com/1608691.tar.gz
Jul  9 11:26:00.732 [20148] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1608691.tar.gz, new
Jul  9 11:26:00.732 [20148] dbg: util: executable for curl was found at /usr/bin/curl
Jul  9 11:26:00.732 [20148] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1608691.tar.gz -- http://www.sa-update.pccc.com/1608691.tar.gz
Jul  9 11:26:01.102 [20148] dbg: http: process [20151], exit status: 5888
Jul  9 11:26:01.102 [20148] dbg: channel: selected mirror http://sa-update.secnap.net
Jul  9 11:26:01.103 [20148] dbg: http: url: http://sa-update.secnap.net/1608691.tar.gz
Jul  9 11:26:01.103 [20148] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1608691.tar.gz, new
Jul  9 11:26:01.103 [20148] dbg: util: executable for curl was found at /usr/bin/curl
Jul  9 11:26:01.103 [20148] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1608691.tar.gz -- http://sa-update.secnap.net/1608691.tar.gz
Jul  9 11:26:01.538 [20148] dbg: http: process [20153], exit status: 5888
Jul  9 11:26:01.538 [20148] dbg: channel: selected mirror http://sa-update.dnswl.org
Jul  9 11:26:01.539 [20148] dbg: http: url: http://sa-update.dnswl.org/1608691.tar.gz
Jul  9 11:26:01.539 [20148] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1608691.tar.gz, new
Jul  9 11:26:01.539 [20148] dbg: util: executable for curl was found at /usr/bin/curl
Jul  9 11:26:01.539 [20148] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1608691.tar.gz -- http://sa-update.dnswl.org/1608691.tar.gz
Jul  9 11:26:01.651 [20148] dbg: http: process [20155], exit status: 5888
Jul  9 11:26:01.651 [20148] dbg: channel: selected mirror http://sa-update.space-pro.be
Jul  9 11:26:01.652 [20148] dbg: http: url: http://sa-update.space-pro.be/1608691.tar.gz
Jul  9 11:26:01.652 [20148] dbg: http: downloading to: /var/lib/spamassassin/3.004000/updates_spamassassin_org/1608691.tar.gz, new
Jul  9 11:26:01.652 [20148] dbg: util: executable for curl was found at /usr/bin/curl
Jul  9 11:26:01.652 [20148] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1608691.tar.gz -- http://sa-update.space-pro.be/1608691.tar.gz
Jul  9 11:26:01.843 [20148] dbg: http: process [20157], exit status: 5888
channel: could not find working mirror, channel failed
Jul  9 11:26:01.843 [20148] dbg: generic: cleaning up temporary directory/files
Jul  9 11:26:01.844 [20148] dbg: generic: cleaning directory /tmp/.spamassassin20148LqkbM6tmp
Jul  9 11:26:01.844 [20148] dbg: diag: updates complete, exiting with code 4
sa-update failed for unknown reasons

    I’ve spent a week or so rummaging around but haven’t found any solutions, and nor have I tried to tweak anything for fear of breaking it. Does anyone have any thoughts please?

    Many thanks

    Jim

    Last edited by oldos2er; July 9th, 2014 at 11:54 PM.

    Reason: Added code tags.

  2. Re: Spamassassin, daily error — sa-update failed for unknown reasons

    Hello,

    I detected this problem today, it is a permission problem.
    try to chown the /var/lib/spamassassin/* files with the appropriate user.

    # chown -R debian-spamd:debian-spamd /var/lib/spamassassin

  3. Re: Spamassassin, daily error — sa-update failed for unknown reasons

  4. Re: Spamassassin, daily error — sa-update failed for unknown reasons

    Thank you, both of you, for your replies. The post by mobidyc-gmail seems to have worked, I’ve run the command manually and this time it’s exited with 0.

    Thanks again

    Jim

  5. Re: Spamassassin, daily error — sa-update failed for unknown reasons

    This post has been extremely helpful. I spent many hours troubleshooting the problem and found the solution here. mobidyc-gmail was on target…. Thanks

Bookmarks

Bookmarks


Posting Permissions

Источник
[[email protected] ~] # /usr/local/cpanel/scripts/sa-update_wrapper
[*] Cleaning up from previous updates.....
[*] Running sa-update (/usr/local/cpanel/3rdparty/perl/528/bin/sa-update).....
[*] Please note that 'IO::Socket::IP' and 'Net::Patricia' are not needed by our implementation of SpamAssassin.
[*] The warnings related to them can be safely ignored.

Mar 4 17:48:03.777 [2466] dbg: logger: adding facilities: all
Mar 4 17:48:03.777 [2466] dbg: logger: logging level is DBG
Mar 4 17:48:03.777 [2466] dbg: generic: SpamAssassin version 3.4.2
Mar 4 17:48:03.777 [2466] dbg: generic: Perl 5.028000, PREFIX=/usr/local/cpanel/3rdparty/perl/528/lib/perl5, DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/mail/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin
Mar 4 17:48:03.778 [2466] dbg: config: timing enabled
Mar 4 17:48:03.779 [2466] dbg: config: score set 0 chosen.
Mar 4 17:48:03.789 [2466] dbg: generic: sa-update version 3.4.2 / svn1840377
Mar 4 17:48:03.789 [2466] dbg: generic: using update directory: /var/lib/spamassassin/3.004002
Mar 4 17:48:04.017 [2466] dbg: diag: perl platform: 5.028000 linux
Mar 4 17:48:04.017 [2466] dbg: diag: [...] module installed: Digest::SHA, version 6.01
Mar 4 17:48:04.017 [2466] dbg: diag: [...] module installed: HTML::Parser, version 3.72
Mar 4 17:48:04.018 [2466] dbg: diag: [...] module installed: Net::DNS, version 1.17
Mar 4 17:48:04.018 [2466] dbg: diag: [...] module installed: NetAddr::IP, version 4.079
Mar 4 17:48:04.018 [2466] dbg: diag: [...] module installed: Time::HiRes, version 1.9759
Mar 4 17:48:04.018 [2466] dbg: diag: [...] module installed: Archive::Tar, version 2.30
Mar 4 17:48:04.018 [2466] dbg: diag: [...] module installed: IO::Zlib, version 1.10
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Digest::SHA1, version 2.13
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: MIME::Base64, version 3.15
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: DB_File, version 1.84
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Net::SMTP, version 3.11
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Mail::SPF, version v2.009
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Geo::IP, version 1.51
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Net::CIDR::Lite, version 0.21
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Razor2::Client::Agent, version 2.84
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: IO::Socket::IP, version 0.39
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: IO::Socket::INET6, version 2.72
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: IO::Socket::SSL, version 2.060
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Compress::Zlib, version 2.074
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Mail::DKIM, version 0.53
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: DBI, version 1.641
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Getopt::Long, version 2.50
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: LWP::UserAgent, version 6.35
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: HTTP::Date, version 6.02
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Encode::Detect::Detector, version 1.01
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module not installed: Net::Patricia ('require' failed)
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: Net::DNS::Nameserver, version 1692
Mar 4 17:48:04.018 [2466] dbg: diag: [...] optional module installed: BSD::Resource, version 1.2911
Mar 4 17:48:04.019 [2466] dbg: gpg: Searching for 'gpg'
Mar 4 17:48:04.019 [2466] dbg: util: current PATH is: /usr/local/cpanel/3rdparty/lib/path-bin:/usr/local/cpanel/3rdparty/lib/path-bin:/usr/local/cpanel/3rdparty/lib/path-bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/opt/cpanel/composer/bin:/usr/local/bin:/root/.wp-cli/bin
Mar 4 17:48:04.020 [2466] dbg: util: executable for gpg was found at /usr/bin/gpg
Mar 4 17:48:04.020 [2466] dbg: gpg: found /usr/bin/gpg
Mar 4 17:48:04.021 [2466] dbg: gpg: release trusted key id list: 5E541DC959CB8BAC7C78DFDC4056A61A5244EC45 0C2B1D7175B852C64B3CDC716C55397824F434CE
Mar 4 17:48:04.022 [2466] dbg: util: secure_tmpfile created a temporary file /tmp/.spamassassin2466lFcc6ztmp
Mar 4 17:48:04.022 [2466] dbg: channel: attempting channel updates.spamassassin.org
Mar 4 17:48:04.022 [2466] dbg: channel: using existing directory /var/lib/spamassassin/3.004002/updates_spamassassin_org
Mar 4 17:48:04.022 [2466] dbg: channel: channel cf file /var/lib/spamassassin/3.004002/updates_spamassassin_org.cf
Mar 4 17:48:04.022 [2466] dbg: channel: channel pre file /var/lib/spamassassin/3.004002/updates_spamassassin_org.pre
Mar 4 17:48:04.023 [2466] dbg: channel: metadata version = 1854245, from file /var/lib/spamassassin/3.004002/updates_spamassassin_org.cf
Mar 4 17:48:04.037 [2466] dbg: dns: 2.4.3.updates.spamassassin.org => 1854677, parsed as 1854677
Mar 4 17:48:04.037 [2466] dbg: channel: preparing temp directory for new channel
Mar 4 17:48:04.038 [2466] dbg: channel: created tmp directory /tmp/.spamassassin2466M1E07Rtmp
Mar 4 17:48:04.038 [2466] dbg: generic: lint checking site pre files once before attempting channel updates
Mar 4 17:48:04.038 [2466] dbg: generic: SpamAssassin version 3.4.2
Mar 4 17:48:04.038 [2466] dbg: generic: Perl 5.028000, PREFIX=/usr/local/cpanel/3rdparty/perl/528/lib/perl5, DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/mail/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin
Mar 4 17:48:04.038 [2466] dbg: config: timing enabled
Mar 4 17:48:04.040 [2466] dbg: config: score set 0 chosen.
Mar 4 17:48:04.042 [2466] dbg: ignore: using a test message to lint rules
Mar 4 17:48:04.042 [2466] dbg: config: using "/etc/mail/spamassassin" for site rules pre files
Mar 4 17:48:04.049 [2466] dbg: config: read file /etc/mail/spamassassin/init.pre
Mar 4 17:48:04.050 [2466] dbg: config: read file /etc/mail/spamassassin/v310.pre
Mar 4 17:48:04.052 [2466] dbg: config: read file /etc/mail/spamassassin/v312.pre
Mar 4 17:48:04.054 [2466] dbg: config: read file /etc/mail/spamassassin/v320.pre
Mar 4 17:48:04.055 [2466] dbg: config: read file /etc/mail/spamassassin/v330.pre
Mar 4 17:48:04.057 [2466] dbg: config: read file /etc/mail/spamassassin/v340.pre
Mar 4 17:48:04.058 [2466] dbg: config: read file /etc/mail/spamassassin/v341.pre
Mar 4 17:48:04.058 [2466] dbg: config: using "/tmp/.spamassassin2466M1E07Rtmp/doesnotexist" for sys rules pre files
Mar 4 17:48:04.058 [2466] dbg: config: using "/tmp/.spamassassin2466M1E07Rtmp/doesnotexist" for default rules dir
Mar 4 17:48:04.065 [2466] dbg: config: using "/tmp/.spamassassin2466M1E07Rtmp/doesnotexist/doesnotexist" for user prefs file
config: failed to parse line, skipping, in "/etc/mail/spamassassin/init.pre":
config: failed to parse line, skipping, in "/etc/mail/spamassassin/v310.pre":
config: failed to parse line, skipping, in "/etc/mail/spamassassin/v312.pre":
Mar 4 17:48:04.065 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::Check from @INC
Mar 4 17:48:04.074 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::HTTPSMismatch from @INC
Mar 4 17:48:04.079 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::URIDetail from @INC
Mar 4 17:48:04.081 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::Shortcircuit from @INC
Mar 4 17:48:04.083 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::Bayes from @INC
Mar 4 17:48:04.094 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::BodyEval from @INC
Mar 4 17:48:04.098 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::DNSEval from @INC
Mar 4 17:48:04.102 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::HTMLEval from @INC
Mar 4 17:48:04.105 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::HeaderEval from @INC
Mar 4 17:48:04.112 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::MIMEEval from @INC
Mar 4 17:48:04.116 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::RelayEval from @INC
Mar 4 17:48:04.121 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::URIEval from @INC
Mar 4 17:48:04.124 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::WLBLEval from @INC
Mar 4 17:48:04.128 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::VBounce from @INC
Mar 4 17:48:04.130 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::Rule2XSBody from @INC
Mar 4 17:48:04.136 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::ImageInfo from @INC
config: failed to parse line, skipping, in "/etc/mail/spamassassin/v330.pre":
Mar 4 17:48:04.140 [2466] dbg: plugin: loading Mail::SpamAssassin::Plugin::AskDNS from @INC
Mar 4 17:48:04.143 [2466] dbg: config: finish parsing
Mar 4 17:48:04.143 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::Rule2XSBody=HASH(0x53fe3a8) implements 'finish_parsing_end', priority 0
Mar 4 17:48:04.144 [2466] dbg: zoom: loading compiled ruleset from /var/lib/spamassassin/compiled/5.028/3.004002
Mar 4 17:48:04.144 [2466] dbg: config: score set 0 chosen.
Mar 4 17:48:04.144 [2466] dbg: dns: EDNS, UDP payload size 4096
Mar 4 17:48:04.144 [2466] dbg: dns: servers obtained from Net::DNS : [200.58.117.74]:53, [200.58.122.8]:53
Mar 4 17:48:04.144 [2466] dbg: dns: nameservers set to 200.58.117.74, 200.58.122.8
Mar 4 17:48:04.144 [2466] dbg: dns: using socket module: IO::Socket::IP version 0.39
Mar 4 17:48:04.144 [2466] dbg: dns: is Net::DNS::Resolver available? yes
Mar 4 17:48:04.144 [2466] dbg: dns: Net::DNS version: 1.17
Mar 4 17:48:04.145 [2466] dbg: config: time limit 300.0 s
Mar 4 17:48:04.145 [2466] dbg: message: main message type: text/plain
Mar 4 17:48:04.145 [2466] dbg: message: ---- MIME PARSER START ----
Mar 4 17:48:04.145 [2466] dbg: message: parsing normal part
Mar 4 17:48:04.145 [2466] dbg: message: storing a body to memory
Mar 4 17:48:04.145 [2466] dbg: message: ---- MIME PARSER END ----
Mar 4 17:48:04.145 [2466] dbg: check: pms new, time limit in 300.000 s
Mar 4 17:48:04.145 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::DNSEval=HASH(0x50eda20) implements 'check_start', priority 0
Mar 4 17:48:04.145 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::Rule2XSBody=HASH(0x53fe3a8) implements 'check_start', priority 0
Mar 4 17:48:04.146 [2466] dbg: check: using scoreset 0 in M:S:Pms
Mar 4 17:48:04.146 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::Check=HASH(0x4fafe38) implements 'check_main', priority 0
Mar 4 17:48:04.146 [2466] dbg: config: trusted_networks are not configured; it is recommended that you configure trusted_networks manually
Mar 4 17:48:04.146 [2466] dbg: metadata: X-Spam-Relays-Trusted:
Mar 4 17:48:04.146 [2466] dbg: metadata: X-Spam-Relays-Untrusted:
Mar 4 17:48:04.146 [2466] dbg: metadata: X-Spam-Relays-Internal:
Mar 4 17:48:04.146 [2466] dbg: metadata: X-Spam-Relays-External:
Mar 4 17:48:04.147 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::AskDNS=HASH(0x546cee0) implements 'extract_metadata', priority 0
Mar 4 17:48:04.147 [2466] dbg: dns: is DNS available? 0
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag AUTHORDOMAIN is now ready, value: compiling.spamassassin.taint.org
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag RELAYSTRUSTED is now ready, value:
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag RELAYSUNTRUSTED is now ready, value:
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag RELAYSINTERNAL is now ready, value:
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag RELAYSEXTERNAL is now ready, value:
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag LANGUAGES is now ready, value: <UNDEF>
Mar 4 17:48:04.147 [2466] dbg: message: no encoding detected
Mar 4 17:48:04.147 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::Shortcircuit=HASH(0x50af8e0) implements 'parsed_metadata', priority 0
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag SC is now ready, value: CODE(0x54cfd50)
Mar 4 17:48:04.147 [2466] dbg: check: tagrun - tag SCRULE is now ready, value: CODE(0x54d00b0)
Mar 4 17:48:04.148 [2466] dbg: check: tagrun - tag SCTYPE is now ready, value: CODE(0x54d0140)
Mar 4 17:48:04.148 [2466] dbg: rules: local tests only, ignoring RBL eval
Mar 4 17:48:04.148 [2466] dbg: check: check_main, time limit in 299.997 s
Mar 4 17:48:04.150 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::Shortcircuit=HASH(0x50af8e0) implements 'have_shortcircuited', priority 0
Mar 4 17:48:04.150 [2466] dbg: dns: harvest_dnsbl_queries
Mar 4 17:48:04.151 [2466] dbg: check: is spam? score=0 required=5
Mar 4 17:48:04.151 [2466] dbg: check: tests=
Mar 4 17:48:04.151 [2466] dbg: check: subtests=
Mar 4 17:48:04.151 [2466] dbg: timing: total 108 ms - init: 102 (94.5%), parse: 0.44 (0.4%), extract_message_metadata: 1.53 (1.4%), get_uri_detail_list: 2.6 (2.4%)
Mar 4 17:48:04.151 [2466] dbg: plugin: Mail::SpamAssassin::Plugin::Check=HASH(0x4fafe38) implements 'finish_tests', priority 0
Mar 4 17:48:04.152 [2466] dbg: generic: lint of site pre files failed, cannot continue
Mar 4 17:48:04.152 [2466] dbg: generic: cleaning up temporary directory/files
Mar 4 17:48:04.152 [2466] dbg: generic: cleaning directory /tmp/.spamassassin2466M1E07Rtmp
Mar 4 17:48:04.152 [2466] dbg: diag: updates complete, exiting with code 2
Cpanel::Exception::ProcessFailed::Error/(XID 3ykzsz) ?/usr/local/cpanel/3rdparty/perl/528/bin/sa-update? reported error code ?2? when it ended:
at /usr/local/cpanel/Cpanel/ChildErrorStringifier.pm line 149.
Cpanel::ChildErrorStringifier::die_if_error(Cpanel::SafeRun::Object=HASH(0x28fb9c8)) called at /usr/local/cpanel/scripts/sa-update_wrapper line 53
main::run_saupdate() called at /usr/local/cpanel/scripts/sa-update_wrapper line 98
Источник

Skip to forum content

iRedMail

Works on CentOS, Rocky, Debian, Ubuntu, FreeBSD, OpenBSD

You are not logged in. Please login or register.

Sep 30, 2022: iRedMail-1.6.2 has been released.



  • Spider Email Archiver: Lightweight on-premises email archiving software, developed by iRedMail team.
  • Join our Telegram group (@iredmail_chat) to get help from other iRedMail users.

Pages 1

You must login or register to post a reply

1 2021-03-17 02:35:31

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 241

Topic: Cron issues with clamav

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
— iRedMail version (check /etc/iredmail-release):
— Deployed with iRedMail Easy or the downloadable installer?
— Linux/BSD distribution name and version:
— Store mail accounts in which backend (LDAP/MySQL/PGSQL):
— Web server (Apache or Nginx):
— Manage mail accounts with iRedAdmin-Pro?
— [IMPORTANT] Related original log or error message is required if you’re experiencing an issue.
====

Hello,
Thank you for the replies in advance. 

CentOS7 system with MariaDB * iRedAdmin-Pro

Recently getting errors related to clamav
ERROR: downloadFile: Unexpected response (429) from https://database.clamav.net/daily-26107.cdiff
ERROR: getpatch: Can’t download daily-26107.cdiff from https://database.clamav.net/daily-26107.cdiff
ERROR: downloadFile: Unexpected response (429) from https://database.clamav.net/daily.cvd
ERROR: getcvd: Can’t download daily.cvd from https://database.clamav.net/daily.cvd
ERROR: Update failed for database: daily
ERROR: Database update process failed: HTTP GET failed (11)
ERROR: Update failed.

Suspect the system is being blocked from too many calls via the API given the (429) code.  How do I confirm and correct that is the case?

—-

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Stable release is out.

2 Reply by ZhangHuangbin 2021-03-17 10:30:17

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,081

Re: Cron issues with clamav

Might be just a temporary clamav mirror site issue. Keep trying regularly.

3 Reply by pbf343 2021-03-18 19:15:03

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 241

Re: Cron issues with clamav

ZhangHuangbin wrote:

Might be just a temporary clamav mirror site issue. Keep trying regularly.

No it continues.  Additionally, a manual wget from the mail host fails as well.   However, can manually download via a browser on local system once CloudFlare allows us.   

It may be tied to a timeout issue due to Cloudflare redirect.  Example of the browser display.

Where are the configuration values for the process configured?

Post’s attachments

Screen Shot 2021-03-18 at 7.13.39 AM.png 96.49 kb, file has never been downloaded. 

You don’t have the permssions to download the attachments of this post.

4 Reply by pbf343 2021-03-18 20:04:17

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 241

Re: Cron issues with clamav

pbf343 wrote:

ZhangHuangbin wrote:

Might be just a temporary clamav mirror site issue. Keep trying regularly.

No it continues.  Additionally, a manual wget from the mail host fails as well.   However, can manually download via a browser on local system once CloudFlare allows us.   

It may be tied to a timeout issue due to Cloudflare redirect.  Example of the browser display.

Where are the configuration values for the process configured?

Ah — found another message:
channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed
18-Mar-2021 05:18:02: SpamAssassin: Unknown error code 3 from sa-update

5 Reply by diespezialisten 2021-03-31 19:33:08

  • diespezialisten
  • Member
  • Offline
  • Registered: 2019-04-30
  • Posts: 7

Re: Cron issues with clamav

Anything new to this?

I still get the error message:

channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed
31-Mär-2021 04:57:42: SpamAssassin: Update available, but download or extract failed

6 Reply by pbf343 2021-04-01 00:39:09

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 241

Re: Cron issues with clamav

diespezialisten wrote:

Anything new to this?

I still get the error message:

channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed
31-Mär-2021 04:57:42: SpamAssassin: Update available, but download or extract failed

Nothing on our end as far as configuration to my knowledge but have done kernel update and am about to update software packages soon. 

The original error message on our end until March 23, 2021. 

On March 24, 2021 — started getting this error.

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

Body: channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed
24-Mar-2021 04:21:07: SpamAssassin: Unknown error code 3 from sa-update

No response from Zhang or crew.  Was probably going to open a new ticket given the color scheme displayed on the forum.

7 Reply by ZhangHuangbin 2021-04-01 11:02:36

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,081

Re: Cron issues with clamav

diespezialisten wrote:

channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed

It’s a temporarily SpamAssassin mirror site issue, i’m afraid that nothing we can do on our side. Just let SpamAssassin (sa-update) keep trying with other mirror sites.

8 Reply by pbf343 2021-04-01 21:34:39 (edited by pbf343 2021-04-01 21:37:01)

  • pbf343
  • Member
  • Offline
  • Registered: 2013-05-30
  • Posts: 241

Re: Cron issues with clamav

ZhangHuangbin wrote:

diespezialisten wrote:

channel: no ‘mirrors.sought.rules.yerp.org’ record found, channel failed

Yes saw that but it is the first time — it was not the previous error. 

ZhangHuangbin wrote:

It’s a temporarily SpamAssassin mirror site issue, i’m afraid that nothing we can do on our side. Just let SpamAssassin (sa-update) keep trying with other mirror sites.

OK Thank you.  However, where are the «other mirror sites» setting to adjust?   Or where do we find the various settings operating the software?   FYI: I’m under the impression that iRedAPD plays a role in antivirus and spam operations.

9 Reply by ms2504 2021-04-01 22:41:19

  • ms2504
  • Member
  • Offline
  • Registered: 2019-06-15
  • Posts: 56

Re: Cron issues with clamav

I removed /etc/mail/spamassassin/channel.d/sought.conf   which is now switched off.

They dropped it because it’s obsolete.

Updates are now running using  spamassassin-official.conf  for me.

10 Reply by diespezialisten 2021-04-01 22:58:01

  • diespezialisten
  • Member
  • Offline
  • Registered: 2019-04-30
  • Posts: 7

Re: Cron issues with clamav

ms2504 wrote:

I removed /etc/mail/spamassassin/channel.d/sought.conf   which is now switched off.

They dropped it because it’s obsolete.

Updates are now running using  spamassassin-official.conf  for me.

Thank you. Iwill try with this. :-)

Posts: 10

Pages 1

You must login or register to post a reply

Generated in 0.008 seconds (69% PHP — 31% DB) with 8 queries

Источник

Should I be worried about the below message ?

/etc/cron.daily/sa_update:

channel: no 'mirrors.updates.spamassassin.org' record found, channel failed
channel: no 'mirrors.sought.rules.yerp.org' record found, channel failed


Kindest regards
Taco


Logged

twijtzes

No

AFAIUI these are temporary «glitches»

Watch for any future messages though.


Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Hi Janet,

These Cron messages appear daily, therefore I tried to find similar issues on the forum or in the bugs list. So far I have not been able to find these messages on the forums, so I think it might be a local thing. If this is an issue with more users, we might need something more drastic.

As my system is updated from version 7, it might have something to do with that. I will set up a fresh SME server to see if the problem persists. If so, I will raise a bug.

Regards,
Taco

« Last Edit: January 07, 2014, 09:06:08 AM by twijtzes »


Logged

twijtzes

A Google search on the second error message found

Bug 7661
&
http://spamassassin.1065346.n5.nabble.com/sought-rules-yerp-org-site-down-td59535.html

As I said these are likely to be temporary problems, DNS related.

Have you specified a particular DNS server or do you have other problems with your ISP ?

I would not waste your time building another server, just change the DNS server you are using (if you can), or delete it from sme server if one is specified, or complain to your ISP


Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

In case it helps, on my system, the files below have the content indicated:

#!/bin/bash
# Only restart spamd if sa-update returns 0, meaning it updated the rules
export HOME=/var/lib/spamassassin
cd $HOME
(/usr/bin/sa-update
  --gpgkeyfile /etc/mail/spamassassin/gpgkeys
  --channelfile /etc/mail/spamassassin/channels
  && service spamassassin condrestart > /dev/null) 2>&1
  | tee -a /var/log/sa-update.log

updates.spamassassin.org
sought.rules.yerp.org

26C900A46DD40CD5AD24F6D7DEE01987265FA05B
D8099BC79E17D7E49BC21E31FDE52F40F7D39814
5E541DC959CB8BAC7C78DFDC4056A61A5244EC45
8D25B5E91DAF0F715F60B588DC85341F6C6191E3

And here’s what I get when I run sa-update manually (the bin, not the cronjob):

# HOME=/var/lib/spamassassin
# cd $HOME
# /usr/bin/sa-update   --gpgkeyfile /etc/mail/spamassassin/gpgkeys   --channelfile /etc/mail/spamassassin/channels -v
Update finished, no fresh updates were available


Logged

Thanks,

If it has to do with DNS, I have a clue where to begin. It will probably have to do with a new network router and double ADSL connection over here, does spam assassin update require additional ports to be opened ?


Logged

recommendation
I think you need to edit this file:
/etc/mail/spamassassin/channels

And make it match mine (see my first post, or take  ‘mirrors.’ out of each hostname).   There is no associated template, so you need to edit the file directly.

Whether this works or not, there is stil a question of how/why your spamassassin channel file acquired incorrect settings.

background
I re-ran the manual update this morning from my previous post:

HOME=/var/lib/spamassassin
cd $HOME
/usr/bin/sa-update   --gpgkeyfile /etc/mail/spamassassin/gpgkeys   --channelfile /etc/mail/spamassassin/channels -v
Today I get this result (convincing me that my system is successfully finding the update channels):

Update available for channel sought.rules.yerp.org
Update was available, and was downloaded and installed successfully

Since I couldn’t find any A record using nslookup for ‘sought.rules.yerp.org’ or ‘updates.spamassassin.org’, I looked up exactly how spamassassin looks for updates:
http://wiki.apache.org/spamassassin/PublishingRuleUpdates

According to that page, sa-update reverses the spamassassin version number and prepends the result to each «channel» supplied when the command is run.

On my system, the channels (from —channelfile /etc/mail/spamassassin/channels) are:

updates.spamassassin.org
sought.rules.yerp.org

…and my spamassassin version (from

spamassassin -V

) is 3.3.2

… so sa-update is looking for the latest rules version using:

# nslookup -type=txt 2.3.3.updates.spamassassin.org
Server:      …
Address:   …#53

Non-authoritative answer:
2.3.3.updates.spamassassin.org   text = «1556147»

# nslookup -type=txt 2.3.3.sought.rules.yerp.org
Server:      …
Address:   …#53

Non-authoritative answer:
2.3.3.sought.rules.yerp.org   text = «3302014010811»

However, when I try to look for versions using the hostnames you seem to have on your system, I get:

# nslookup -type=txt 2.3.3.mirrors.updates.spamassassin.org
Server:      …
Address:   …#53

** server can’t find 2.3.3.mirrors.updates.spamassassin.org: NXDOMAIN

[root@office ~]# nslookup -type=txt 2.3.3.mirrors.sought.rules.yerp.org
Server:      …
Address:   …#53

** server can’t find 2.3.3.mirrors.sought.rules.yerp.org: NXDOMAIN


Logged

twijtzes

As my system is updated from version 7….

I wonder if your system is updating correctly, & whether the repos are set correctly.
Show output of
/sbin/e-smith/audittools/repositories


Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.


Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Hi Janet,

below please find the output of /sbin/e-smith/audittools/repositories

addons: disabled
base: enabled
centos-testing: disabled
centosplus: disabled
contrib: disabled
extras: disabled
smeaddons: enabled
smecontribs: disabled
smedev: disabled
smeextras: enabled
smeos: enabled
smetest: disabled
smeupdates: enabled
smeupdates-testing: enabled
updates: enabled

« Last Edit: January 19, 2014, 03:14:13 PM by twijtzes »


Logged

twijtzes

smeupdates-testing: enabled

That repo should normally be disabled.
You may have rpms installed that are still under test & not ready for release, & could still be buggy.

The db setting for that repo should be

db yum_repositories show smeupdates-testing

smeupdates-testing=repository
    EnableGroups=yes
    GPGCheck=yes
    MirrorList=http://mirrorlist.contribs.org/mirrorlist/smeupdates-testing-8
    Name=SME Server — updates testing
    Visible=yes
    status=disabled

To fix yours do
db yum_repositories setprop smeupdates-testing status disabled
signal-event yum-modify

See
http://wiki.contribs.org/SME_Server:Documentation:FAQ:Section01#Which_repositories_should_be_enabled


Logged

Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Источник

Понравилась статья? Поделить с друзьями:
  • Spacedesk error duet display
  • Spacedesk error code 2 5
  • Spacedesk error 2503
  • Space engineers ошибка сохранения
  • Space engineers как изменить цвет блока