SpamAssassin Update Fail

webfeatus · Unread post by **webfeatus** » Wed Feb 13, 2013 7:54 am

Cron = /usr/share/spamassassin/sa-update.cron 2>&1 | tee -a /var/log/sa-update.log

http: GET http://rules.yerp.org.s3.amazonaws.com/ ... 221.tar.gz request failed: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>C193E3DF74626A7A</RequestId><HostId>dSuZ/Lt19GirCsfEuanPRnePNqJX5t7dIETrEspihSwvkG8CxTZ1vmc9z8I7EebB</HostId></Error>
channel: could not find working mirror, channel failed

Feb 12 14:45:41 Updated: 1:spamassassin-3.3.2-7.el5.art.i386

Is this a one-off connection issue?

My server admin have reconfigured spamassassin in the server to fix the reported issue. Currently spamassassin sa-update is running on the server for updating spamassassin rules.

I do not know what they did and if they should have done it???

faris · Unread post by **faris** » Wed Feb 13, 2013 2:37 pm

I thought these rules were now part of the core ruleset, and there was no need to have a separate sa-update download?

However, when I did a google search I found this thread http://spamassassin.1065346.n5.nabble.c ... 44156.html which confuses the hell out of me.

webfeatus · Unread post by **webfeatus** » Wed Feb 13, 2013 9:42 pm

I am confused by this issue but today I received the same error message as above.

14-Feb-2013 05:59:28: SpamAssassin: Update available, but download or extract failed

Can anyone please help me understand what is going on?

stephan-zrh · Unread post by **stephan-zrh** » Thu Feb 14, 2013 3:17 am

We have the same issues. We didn't change anything regarding Spamassassin and it seems the errors started on February 9th (looks like the update on the 12th worked?):

Code: Select all

[root@host log]# more sa-update.log
02-Feb-2013 04:11:56: SpamAssassin: Update processed successfully
03-Feb-2013 04:19:44: SpamAssassin: Update processed successfully
04-Feb-2013 04:24:19: SpamAssassin: Update processed successfully
05-Feb-2013 04:52:06: SpamAssassin: Update processed successfully
06-Feb-2013 04:53:47: SpamAssassin: Update processed successfully
07-Feb-2013 04:35:07: SpamAssassin: Update processed successfully
08-Feb-2013 05:35:42: SpamAssassin: Update processed successfully
http: GET http://sa-update.secnap.net/1443890.tar.gz request failed: 404 Not Found: <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <ce
nter><h1>404 Not Found</h1></center> <hr><center>nginx/1.2.1</center> </body> </html> 
09-Feb-2013 05:39:59: SpamAssassin: Update processed successfully
/bin/bash: line 1:  7112 Terminated              spamd -u popuser -d -m 10 -x --virtual-config-dir=/var/qmail/mailnames/%d/%l --socketpath=/tmp/spamd_full.sock
 -r /var/run/spamd.pid
10-Feb-2013 05:25:33: SpamAssassin: Update processed successfully
http: GET http://sa-update.secnap.net/1444342.tar.gz request failed: 404 Not Found: <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <ce
nter><h1>404 Not Found</h1></center> <hr><center>nginx/1.2.1</center> </body> </html> 
11-Feb-2013 04:51:50: SpamAssassin: Update processed successfully
12-Feb-2013 04:19:57: SpamAssassin: Update processed successfully
http: GET http://rules.yerp.org.s3.amazonaws.com/rules/stage/3302013021221.tar.gz request failed: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?> <Error>
<Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>272987D4EB2B7388</RequestId><HostId>OgTZESIgn2O7fk/bCAGOt5YVxA3+maW7oNb5Dier23XgCm2Y+usMXW6
YtB/3266J</HostId></Error>
channel: could not find working mirror, channel failed
13-Feb-2013 04:18:28: SpamAssassin: Update processed successfully
http: GET http://rules.yerp.org.s3.amazonaws.com/rules/stage/3302013021221.tar.gz request failed: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?> <Error>
<Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>580D03748369F6E9</RequestId><HostId>cwrj50uTi9iyUMU9PERc/tCVRmyIQHkPpPmZZSPrZI0UrmfmFamn2cf
iBQn56Bhd</HostId></Error>
channel: could not find working mirror, channel failed
14-Feb-2013 04:31:43: SpamAssassin: Update processed successfully

Anybody know what to do? Is this an issue with Plesk or ASL?

regards

-Stephan

Dogs and things · Fri Feb 15, 2013 2:29 am

Hello,

I am reporting a problem with similar errors:

Code: Select all

http: GET http://rules.yerp.org.s3.amazonaws.com/rules/stage/3302013021221.tar.gz request failed: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>CB14432D3E9D76EE</RequestId><HostId>Ei6wMjiOyYIMXPB2G0vrVIN8lQzBAWoCEmOl5Mtqj1VHwA8GvBD+tm9bzwD0APJn</HostId></Error>
channel: could not find working mirror, channel failed

Code: Select all

01-Feb-2013 05:33:38: SpamAssassin: Update processed successfully
02-Feb-2013 05:27:16: SpamAssassin: Update processed successfully
03-Feb-2013 04:29:00: SpamAssassin: Update processed successfully
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
04-Feb-2013 04:41:27: SpamAssassin: Update processed successfully
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
05-Feb-2013 04:37:57: SpamAssassin: Update processed successfully
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
06-Feb-2013 04:21:39: SpamAssassin: Update processed successfully
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
07-Feb-2013 04:10:41: SpamAssassin: Update processed successfully
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
08-Feb-2013 04:33:23: SpamAssassin: Update processed successfully
http: GET http://sa-update.secnap.net/1443890.tar.gz request failed: 404 Not Found: <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.2.1</center> </body> </html> 
09-Feb-2013 06:02:59: SpamAssassin: Update processed successfully
10-Feb-2013 05:01:42: SpamAssassin: Update processed successfully
http: GET http://sa-update.secnap.net/1444342.tar.gz request failed: 404 Not Found: <html> <head><title>404 Not Found</title></head> <body bgcolor="white"> <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.2.1</center> </body> </html> 
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
11-Feb-2013 04:58:39: SpamAssassin: Update processed successfully
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
12-Feb-2013 04:36:42: SpamAssassin: Update processed successfully
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
http: GET http://rules.yerp.org.s3.amazonaws.com/rules/stage/3302013021221.tar.gz request failed: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>076008E2F35786D9</RequestId><HostId>1GPXRcUn1JMHkU1WD5cjSIJx9CJB67XSxeILz5X1J1On6RSmKAYK1/HwFjmhVsrW</HostId></Error>
channel: could not find working mirror, channel failed
13-Feb-2013 04:20:17: SpamAssassin: Update available, but download or extract failed
Shutting down psa-spamassassin service:  [  OK  ]
Starting psa-spamassassin service:  [  OK  ]
http: GET http://rules.yerp.org.s3.amazonaws.com/rules/stage/3302013021221.tar.gz request failed: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>116820D404EAB43F</RequestId><HostId>mjYFM8X1R8ZKdJLk17oLcIYR2OapdRxcVMBjyo4AGfyJEZY4q1Gtep+myus0mb6m</HostId></Error>
channel: could not find working mirror, channel failed
14-Feb-2013 05:52:34: SpamAssassin: Update processed successfully
http: GET http://rules.yerp.org.s3.amazonaws.com/rules/stage/3302013021221.tar.gz request failed: 403 Forbidden: <?xml version="1.0" encoding="UTF-8"?> <Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>CB14432D3E9D76EE</RequestId><HostId>Ei6wMjiOyYIMXPB2G0vrVIN8lQzBAWoCEmOl5Mtqj1VHwA8GvBD+tm9bzwD0APJn</HostId></Error>
channel: could not find working mirror, channel failed
15-Feb-2013 05:40:58: SpamAssassin: Update processed successfully

What might be wrong?

Greetings.

prupert · Unread post by **prupert** » Fri Feb 15, 2013 7:05 am

One of the update channels (http://rules.yerp.org.s3.amazonaws.com) for the SpamAssassin rules appears to be returning 403's. We have also seen this on our servers. This should not be problematic, and I hope it will be fixed soon. Whether or not the update channel is down is intentional or not I don't know. The configuration is part of the SpamAssassin package provided by the Atomic repository.

faris · Unread post by **faris** » Fri Feb 15, 2013 12:48 pm

I have no intention of derailing this topic, but I thought I'd mention that as well as getting these SA errors, I'm now also getting ClamAV errors of a similar nature. I'm using the default db.us.clamav.net although I'm aware there are other mirrors.

I'm mentioning this just in case there's some relation (e.g. same AWS data centre, or...I don't know).

breun · Unread post by **breun** » Fri Feb 15, 2013 7:07 pm

This issue has been reported on the spamassassin-users mailinglist as well and seems to concern "JM's SOUGHT rules": http://mail-archives.apache.org/mod_mbo ... CCC.com%3e

prupert · Unread post by **prupert** » Mon Feb 18, 2013 6:53 am

As of yet it does not appear to be clear why the Sought rules channel is down.

To prevent the errors you could disable the channel (temporarily) by moving /etc/mail/spamassassin/channel.d/sought.conf to something like /etc/mail/spamassassin/channel.d/sought.conf.disabled.

That said, it would be great if somebody responsible for this channel could announce if the channel being down is intentional or not and if this is going to get resolved.

See also:
http://taint.org/2007/08/15/004348a.html
http://mail-archives.apache.org/mod_mbo ... CCC.com%3e

breun · Unread post by **breun** » Mon Feb 18, 2013 7:22 am

prupert wrote:That said, it would be great if somebody responsible for this channel could announce if the channel being down is intentional or not and if this is going to get resolved.

Here's someone on the spamassassin-users mailinglist saying he cc'ed Justin Mason "to see if he can enlighten anyone": http://spamassassin.1065346.n5.nabble.c ... 03543.html

The error is about updating the SOUGHT rules. So far I haven't been able to find any statement on what the status of this issue is.

The configuration for this channel is indeed in /etc/mail/spamassassin/channel.d/sought.conf and this file belongs to the spamassassin package as distributed by the Atomic channel for EL5 and EL6. The sought.conf file doesn't exist in the spamassassin package distributed by EL5 (nor does the /etc/mail/spamassassin/channel.d directory for that matter), but it does exist in the spamassassin package distributed by EL6.

The SpamAssassin channel configuration files in /etc/mail/spamassassin/channel.d are processed by /usr/share/spamassassin/sa-update.cron which is executed daily from /etc/cron.d/sa-update.

prupert · Unread post by **prupert** » Tue Feb 19, 2013 7:20 am

Justin Mason (the guy behind the rules server) just announced that the SOUGHT channel is working again. Users on the SpamAssassin mailing list are also reporting it is working again.

See https://twitter.com/jmason/status/303636537646649345

Atomicorp

SpamAssassin Update Fail

SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail

Re: SpamAssassin Update Fail