• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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