Spamassasin: sa-update finds no working mirror, channel failed

Support
,
1

NethServer Version: NS 7.4
Module: email

Since some days I get this error messages:

Cron <root@ns7ad1> /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log
Freitag, November 24, 2017 05:46 CET
(Cron Daemon)
root@ns7ad1.domain.tld
An
root
channel: could not find working mirror, channel failed
24-Nov-2017 05:46:34: SpamAssassin: Unknown error code 3 from sa-update

from sa-update.log:

    channel: could not find working mirror, channel failed
    10-Nov-2017 05:48:03: SpamAssassin: Unknown error code 3 from sa-update
    channel: could not find working mirror, channel failed
    11-Nov-2017 04:54:21: SpamAssassin: Update available, but download or extract failed
    channel: could not find working mirror, channel failed
    12-Nov-2017 05:25:19: SpamAssassin: Update available, but download or extract failed
    channel: could not find working mirror, channel failed
    13-Nov-2017 05:40:27: SpamAssassin: Update available, but download or extract failed
    channel: could not find working mirror, channel failed
    14-Nov-2017 05:47:43: SpamAssassin: Update available, but download or extract failed
    channel: could not find working mirror, channel failed
    21-Nov-2017 04:35:49: SpamAssassin: Unknown error code 3 from sa-update
    channel: could not find working mirror, channel failed
    22-Nov-2017 04:57:23: SpamAssassin: Unknown error code 3 from sa-update
    channel: could not find working mirror, channel failed
    23-Nov-2017 05:00:01: SpamAssassin: Unknown error code 3 from sa-update
    channel: could not find working mirror, channel failed
    24-Nov-2017 05:46:34: SpamAssassin: Unknown error code 3 from sa-update

Anyone else has this problem?

2

No problems here:

[filippo@nethesis.it@nethservice ~]$ tail /var/log/sa-update.log
15-Nov-2017 05:17:11: SpamAssassin: No update available
16-Nov-2017 04:34:59: SpamAssassin: No update available
17-Nov-2017 04:44:07: SpamAssassin: No update available
18-Nov-2017 05:49:56: SpamAssassin: No update available
19-Nov-2017 05:02:32: SpamAssassin: Update processed successfully
20-Nov-2017 05:43:03: SpamAssassin: Update processed successfully
21-Nov-2017 04:41:20: SpamAssassin: Update processed successfully
22-Nov-2017 05:28:45: SpamAssassin: Update processed successfully
23-Nov-2017 04:41:20: SpamAssassin: Update processed successfully
24-Nov-2017 05:51:16: SpamAssassin: Update processed successfully
1 Like
3

I once had a problem with updates because of blocking POLICY category in suricata IPS…just an idea.

4

Thanks Markus for this hint. Will check it when back at work on Monday.
Have a nice w.e.

1 Like
5

@mrmarkuz it isn’t suricata.

I found this, when I try to update manually --debug:

/usr/bin/curl -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 3402014020421.tar.gz -- http://rules.yerp.org.s3.amazonaws.com/rules/stage/3402014020421.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 403 Forbidden

Other updatechannels (heinlein-support.de) seems working.
If I remove the sought.conf from /etc/mail/spamassasin/conf.d sa-update works.

EDIT: I found that sought ruleset is no longer active and shouldn’t be used. (since 12/2016)

image.png1602Ă—321 23.9 KB

1 Like