Spamassassin Update Error Message

Today the anacron email of my mailinabox contained an error message starting with:

etc/cron.daily/spamassassin:
Cannot open file /var/lib/spamassassin/3.004002/updates_spamassassin_org/1895535.tar.gz: No such file or directory at /usr/bin/sa-update line 1599.
Dec  4 07:05:35.501 [21816] dbg: logger: adding facilities: all
Dec  4 07:05:35.502 [21816] dbg: logger: logging level is DBG
Dec  4 07:05:35.502 [21816] dbg: generic: SpamAssassin version 3.4.2
Dec  4 07:05:35.502 [21816] dbg: generic: Perl 5.026001, PREFIX=/usr, DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin
Dec  4 07:05:35.502 [21816] dbg: config: timing enabled
Dec  4 07:05:35.505 [21816] dbg: config: score set 0 chosen.
Dec  4 07:05:35.509 [21816] dbg: util: running in taint mode? yes
Dec  4 07:05:35.509 [21816] dbg: util: taint mode: deleting unsafe environment variables, resetting PATH
Dec  4 07:05:35.509 [21816] dbg: util: PATH included '/usr/local/sbin', keeping
Dec  4 07:05:35.509 [21816] dbg: util: PATH included '/usr/local/bin', keeping
Dec  4 07:05:35.509 [21816] dbg: util: PATH included '/sbin', keeping
Dec  4 07:05:35.509 [21816] dbg: util: PATH included '/bin', keeping
Dec  4 07:05:35.509 [21816] dbg: util: PATH included '/usr/sbin', keeping
Dec  4 07:05:35.509 [21816] dbg: util: PATH included '/usr/bin', keeping
Dec  4 07:05:35.509 [21816] dbg: util: final PATH set to: /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Dec  4 07:05:35.665 [21816] dbg: diag: perl platform: 5.026001 linux
...

Any ideas what’s going on here?

What version of MiaB are you running? Are system packages up to date?

Latest version: v55. Yes, system packages are up to date.

Have you installed anything besides MiaB or modified anything?

The VM is dedicated to MiaB, no additional software is installed, nothing modified in the config.
Also, only 30% of disk space is used, so there is no reason, why an upfront download should have failed.
The file claimed to be missing is not there, indeed. The directory belongs to debian-spamd.

I don’t have that file and I’ve never received that email, so I’m not sure what the file is fore, but I’m also not sure how those updates are applied.

Hi
I had the same message.
System is as installed by Alento back in June, on a dedicated server

Stef

See my earlier discussion at: SpamAssassin Daily Updates Script Failure Reports. Reinstalling the spamassassin and python3 packages seemed to fix the SpamAssassin update problems that mysteriously developed on our MiaB server.