Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
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
Hey PLESK team, will you please fix this? It's getting very annoying.
BTW, when I delete all existing Backups and start over it works - until one full cycle has been reached (i.e. weekly full + incremental = full cycle after 7 days).
On Plesk Onyx Version 17.0.17 Update #12 this happens (again). I have applied the manual pmm-ras fix as it helped in the past and will report back.
This thread should NOT be tagged as "resolved".
I copied the pmm-ras file over manually, that did the trick for a few days. Suddenly the errors are back and I realized: My copy was overwritten. I repeated the manual fix. Let's see how that works...
I removed the config, removed aum, reinstalled it, copied the config file from /var/asl/rbc/etc/asl/config , now the crons are not generating error reports with
REPUTATION_REPORT="no"
APACHE_RESTART_COMMAND="/etc/init.d/apache2 restart"
on Debian.
Nope. Did no such thing.
Using the content of the config(backup?) that was located at /var/asl/rbc/etc/asl/config with APACHE_RESTART_COMMAND and REPUTATION_REPORT adjusted to apache2 Debian / "no".
The KB (which now just says update aum) doesn't fix the cron error message
run-parts: /etc/cron.hourly/asl exited with return code 126
with aum 4.0.19-40 on Debian.
@KristianM , your fix did help indeed. FInal or not, it'sa working workaround, better than disabling the hourly job.
To wrap the fixes / workarounds up:
1. Missing config
/ ASL has not been configured
2. Hourly cron exit code 127