• 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.

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

Dirk

Dirk

Basic Pleskian
I am receiving an Email every morning at about 4 from cron:

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

The subject states:
Cron <root@liesenfeld> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

When I run from shell:
/etc/cron.daily/60sa-update
there is no error.

Any ideas guys...?
 
Dirk said:
Ah, so it will be fixed in the next update?
Click to expand...
We're running Ubuntu as well, we still get the error and we can also run it from shell with no errors etc. @Dirk

Just confirming which? @IgorG An OS update for us exclusive of Plesk... or, an OS update, with which, Plesk will then subsequently release an Obsidian Update?

Assuming that it's the second type of fix (most likley), the last Obsidian update was 18.0.28 #3 on the 20/7/2020 just a few days after the last posts on this thread. In which case, we're guessing the Spam Assasin fix arrived after 18.0.28 #3 had alrerady been prepared & signed off? Therefore, assuming the normal Plesk release schedule still applies, it should actually be fixed in the Obsidian 18.0.29 release, which is due very soon?
 
The exact same problem returned a couple of days ago. What is the reason for this and how can I fix it?
 
You must log in or register to reply here.

Similar threads

T
Issue ERROR: Dr.Web Updater: failed to download files ! return code 105
Replies
3
Views
1K
Kaspar@Plesk
Kaspar@Plesk
M
Issue Dr.Web Updater: failed to download files (return code 103)
Replies
1
Views
864
Kaspar
K
W
Issue Debian 11 run-parts: /etc/cron.hourly/01-awp_hourly exited with return code 127
Replies
2
Views
561
websb
W
M
Issue run-parts: /etc/cron.daily/pleskupdate exited with return code 1
2
Replies
21
Views
5K
Kloptor
K
Liwindo
run-parts: /etc/cron.daily/pleskupdate exited with return code 1
Replies
9
Views
16K
Peter Debik
P
Back
Top