• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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