Bug 8122 - For more than 15 days I've been getting "no fresh updates were available"
Summary: For more than 15 days I've been getting "no fresh updates were available"
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: sa-update (show other bugs)
Version: 3.4.4
Hardware: PC Windows
: P2 major
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-25 21:55 UTC by sergiortc
Modified: 2023-03-27 20:02 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 sergiortc 2023-03-25 21:55:01 UTC 
I use Windows Server 2022 Standard and Spamassassin for Windows (JAM Software).
For over two years it has been working flawlessly.
But two weeks ago or so I began receiving the message "Update finished, no fresh updates were available"  when I run Sa-Update.
I run the command:
sa-update -v --nogpg -D
And the last 9 lines are:
[5884] dbg: channel: attempting channel updates.spamassassin.org

[5884] dbg: channel: using existing directory C:\Program Files\JAM Software\SpamAssassin for Windows\share\3.004004\updates_spamassassin_org

[5884] dbg: channel: channel cf file C:\Program Files\JAM Software\SpamAssassin for Windows\share\3.004004\updates_spamassassin_org.cf

[5884] dbg: channel: channel pre file C:\Program Files\JAM Software\SpamAssassin for Windows\share\3.004004\updates_spamassassin_org.pre

[5884] dbg: channel: metadata version = 1908044, from file C:\Program Files\JAM Software\SpamAssassin for Windows\share\3.004004\updates_spamassassin_org.cf

[5884] dbg: dns: 4.4.3.updates.spamassassin.org => 1908044, parsed as 1908044

[5884] dbg: channel: current version is 1908044, new version is 1908044, skipping channel

[5884] dbg: diag: updates complete, exiting with code 1
Update finished, no fresh updates were available.

I think it's hardly tru that there has not been rules updates for 15+ days.

Can anybody help?

Thanks!
Comment 1 Benny Pedersen 2023-03-25 22:40:58 UTC 
subscribe to users maillist, its not a bug, please close this ticket if you cant provide bug detals other then no updates
Comment 2 sergiortc 2023-03-25 23:56:10 UTC 
Somebody told me "its not a bug, please close this ticket if you
cant provide bug detals other then no updates".
Choosing status resolved invalid is my approach to "close it".
Maybe it is worth it to note the person did not helped me understand the lack of updates.
Comment 3 Benny Pedersen 2023-03-26 01:23:13 UTC 
Exit Status 9 is not zero for do-nightly-rescore-example.sh

=== tail of ~automc/tmp/do-stable-update-with-scores.log ===
 HAM: 359282 (100000 required)
+ echo 'SPAM: 5105 (60000 required)'
SPAM: 5105 (60000 required)
+ [[ 359282 -lt 100000 ]]
+ [[ 5105 -lt 60000 ]]
+ echo 'Insufficient spam corpus to generate scores; aborting.'
Insufficient spam corpus to generate scores; aborting.
+ exit 9
+ RV=9
+ '[' 9 -ne 0 ']'
+ echo 'Exit Status 9 is not zero for do-nightly-rescore-example'
Exit Status 9 is not zero for do-nightly-rescore-example
+ echo 'From: noreply@spamassassin.apache.org (automc Cron)'
+ echo 'Subject: [auto] do-nightly-rescore-example return code 9'
+ echo ''
+ echo 'Exit Status 9 is not zero for do-nightly-rescore-example.sh'
+ echo ''
+ echo '=== tail of ~automc/tmp/do-stable-update-with-scores.log ==='
+ tail -20 /usr/local/spamassassin/automc/tmp/do-stable-update-with-scores.log
+ /usr/sbin/sendmail -oi ruleqa@spamassassin.apache.org
Comment 4 Bill Cole 2023-03-27 19:05:42 UTC 
(In reply to sergiortc from comment #2)
> Somebody told me "its not a bug, please close this ticket if you
> cant provide bug detals other then no updates".
> Choosing status resolved invalid is my approach to "close it".
> Maybe it is worth it to note the person did not helped me understand the
> lack of updates.

Currently we have a disruption in the feed of data that allows us to do QA and rescoring. There are not enough recent mass-check spam sub missions to trust the results. This is the QA system operating as designed, avoiding the risk of basing new scores on a too-small sample. 

We've addressed the problem with getting fresh mass-check logs, so updates should resume in a few days after enough have been received.
Comment 5 sergiortc 2023-03-27 19:11:54 UTC 
Thank you very much for your answer and for the information about the disruption in the feed of data.
Is there anything else, other than setting the status to "resolved-invalid", I can do to close my report?
Tnak you again.
Comment 6 Bill Cole 2023-03-27 19:59:33 UTC 
(In reply to sergiortc from comment #5)

> Is there anything else, other than setting the status to "resolved-invalid",
> I can do to close my report?

No, that's all.