• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Cron ASL errors started today

@Pascal_Netenvie make sure that you have default content of /etc/cron.daily/50plesk-daily:

# cat /etc/cron.daily/50plesk-daily
#!/bin/sh
### Copyright 1999-2017. Plesk International GmbH. All rights reserved.

# install_statistics
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1

# install_mysqldump
/usr/local/psa/bin/mysqldump.sh >/dev/null 2>&1
 
@Pascal_Netenvie make sure that you have default content of /etc/cron.daily/50plesk-daily:

# cat /etc/cron.daily/50plesk-daily
#!/bin/sh
### Copyright 1999-2017. Plesk International GmbH. All rights reserved.

# install_statistics
/usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/plib/DailyMaintainance/script.php >/dev/null 2>&1

# install_mysqldump
/usr/local/psa/bin/mysqldump.sh >/dev/null 2>&1

Sure, thanks.
Done.
 
But I'm asking how can happen again if:

"Resolution

The issue has been fixed on Atomic ModSecurity side. Fix should be delivered in scope of rule set update, so in order to force it, enable and disable Atomic Basic ModSecurity via Tools & Settings > Web Application Firewall."
 
I also have this problems on my servers from around 03:20 CEST today. I am running the Advanced Atomicorp Ruleset (subscription). Turning off and turning on ModSecurity did not help, I'm still getting the same emails with Cron errors every hour saying "Error: ASL has not been configured". Any other clues about a solution?
 
I also have this problems on my servers from around 03:20 CEST today. I am running the Advanced Atomicorp Ruleset (subscription). Turning off and turning on ModSecurity did not help, I'm still getting the same emails with Cron errors every hour saying "Error: ASL has not been configured". Any other clues about a solution?

There seems to be something on Atomic's side again that needs to be fixed by them. Only this solution can help temporarily:

Notification in Plesk: Error: ASL has not been configured run-parts: /etc/cron.hourly/asl exited with return code 1
 
Switching to OWASP and then back to Atomic Advanced ModSecurity Rules also solved the problem for me, now everything is working as it should, thanks!
 
Back
Top