Bug 7011 - Rules Update for 3.4.0 not working and/or not updating DNS
Summary: Rules Update for 3.4.0 not working and/or not updating DNS
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: RuleQA (show other bugs)
Version: 3.4.0
Hardware: PC Windows 7
: P2 blocker
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 22:31 UTC by Kevin A. McGrail
Modified: 2014-06-17 21:06 UTC (History)
2 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin A. McGrail 2014-02-17 22:31:51 UTC 
On 2/17/2014 5:22 PM, Bob Proulx wrote:
> After the upgrade to 3.4.0 I persistently get the following error from
> sa-update.
>
>   channel: could not find working mirror, channel failed
>
> If I run it with --debug then it looks like it gets everything that it
> needs but then still fails.  Here is the small snippet.
>
>   Feb 17 14:56:38.859 [7333] dbg: http: /usr/bin/curl -s -L -O --remote-time -g --max-redirs 2 --connect-timeout 30 --max-time 300 --fail -o 1567423.tar.gz -- http://www.sa-update.pccc.com/1567423.tar.gz
>   Feb 17 14:56:39.130 [7333] dbg: http: process [7337], exit status: 5632
>
> Of course that location is 404 Not Found.
>
>   Feb 17 14:56:37.483 [7333] dbg: dns: 0.4.3.updates.spamassassin.org => 1567423, parsed as 1567423
>
>   $ dig 0.4.3.updates.spamassassin.org +short txt
>   "1567423"
>
> Is there a mirror sync issue?  That serial number seems old.  A
> previous version 3.3.2 is up to 1568594.
>
>   $ dig 2.3.3.updates.spamassassin.org +short txt
>   "1568594"
>
> Unfortunately the mirrors are configured such that it isn't possible
> to list what files are actually there so I can't tell anything
> further.  Any ideas?
>
> Bob


Thanks for posting this.  I will work on the issue and open a bug.  This is the first time we've switched the minor version (i.e. 3.3 to 3.4) and there is likely a publishing script I have to find and update.

From checking the 3.4.0 was last updated on 2/11 the day of the release.
Comment 1 Frank Urban 2014-02-19 08:28:25 UTC 
Should this not get a higher Prio?
As far as I can see its not possible to install Version 3.4 at this time, because nobody is able to get a fitting rules set for this version.
Comment 2 Kevin A. McGrail 2014-02-19 11:20:14 UTC 
You can install 3.4.0 with the rules that are available on the website downloads.

But I've made it so at least it points to update 1568906 which should allow sa-update to run, thanks for the idea.
Comment 3 Frank Urban 2014-02-19 11:33:38 UTC 
Thanks for the help.
Where can I download the rules without knowing the version no?
Are the rules different for 3.3.2 and 3.4? Or are they equal?
Look like that I need to wait until the DNS returns the new version no. UNtil now is still get
# dig 0.4.3.updates.spamassassin.org +short txt
"1567423"
Comment 4 Kevin A. McGrail 2014-02-19 12:11:39 UTC 
(In reply to Frank Urban from comment #3)
> Thanks for the help.
> Where can I download the rules without knowing the version no?
> Are the rules different for 3.3.2 and 3.4? Or are they equal?
> Look like that I need to wait until the DNS returns the new version no.
> UNtil now is still get
> # dig 0.4.3.updates.spamassassin.org +short txt
> "1567423"

I didn't check the TTL on the zone, but you should see this soon 0.4.3.updates.spamassassin.org. 3440 IN TXT     "1568906"

Beyond that, the project has 3.4.0 for download along with rules at http://spamassassin.apache.org/downloads.cgi?update=201402111327

regards,
KAM
Comment 5 Kevin A. McGrail 2014-02-20 15:20:21 UTC 
Status Update: I got the SSL certs working last night and we did get a rules update.

I also manually set 3.4.0 to match 3.4.1 (trunk) so updates are going out.  More work to find out why 3.4.0 isn't getting updates but things are progressing again!
Comment 6 Kevin A. McGrail 2014-06-17 21:06:14 UTC 
This was resolved prior to the box crash