• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved run-parts: /etc/cron.daily/60sa-update exited with return code 4

floh

Basic Pleskian
Server operating system version
Debian GNU/Linux 10 \n \l
Plesk version and microupdate number
Obsidian 18.0.54
Hi, I got that error message by email. How can I fix it and what is the cause of that?

I believe it's related to that:
Code:
Jul 23 06:36:08.506 [1636103] dbg: dns: query failed: 2.4.3.updates.spamassassin.org => REFUSED
Jul 23 06:36:08.506 [1636103] dbg: dns: query failed: mirrors.updates.spamassassin.org => REFUSED
channel: no 'mirrors.updates.spamassassin.org' record found, channel failed
Jul 23 06:36:08.506 [1636103] dbg: diag: updates complete, exiting with code 4

If this is the reason, then how can I check if and why it's refused?

Best regards
Floh
 
Fixed it with following commands:
Bash:
wget http://spamassassin.apache.org/updates/GPG.KEY
sa-update --import GPG.KEY
But do you know why this happened? And why doesn't plesk-update script check if the key is still valid and try to repair itself by updating the gpg key?

Best regards
Floh
 
Back
Top