Applicable to:
- Plesk Onyx for Linux
Symptoms
- The following notification is received every hour:
CONFIG_TEXT: Message:
/etc/cron.hourly/asl:
Error: ASL has not been configured
run-parts: /etc/cron.hourly/asl exited with return code 1
EMAIL ERROR - 2 - Manual execution if the task results in the same outcome:
# run-parts /etc/cron.hourly/
/etc/cron.hourly/asl:
Error: ASL has not been configured
Cause
Aum was updated, but was not configured properly.
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.
In case below workaround was applied remove /usr/bin/aum -c > /dev/null 2>&1 from /etc/cron.hourly/asl file.
- Log into the server via SSH.
- Configure ASL manually by executing the following command:
# aum -c
- Verify that the issue is gone by executing the task manually:
# run-parts /etc/cron.hourly/
Note: this command might be hung in case there was another
/etc/cron.hourly/plesk-php-cleanupertask running at the same time. In case it does not finish in 10-15 minutes, just interrupt the process, nothing bad will come from it. - As the
/etc/asl/configfile might be overwritten by Plesk/ASL daily tasks, place the same command at the top of/etc/cron.hourly/aslfile right after#!/bin/bashline, the result should look like follows:CONFIG_TEXT: #!/bin/bash
/usr/bin/aum -c > /dev/null 2>&1
...
... - Perform the same procedure as in the step 4 for
/etc/cron.daily/asltask too.
Note: Please subscribe to this article in order to be notified regarding the better workaround and also to be updated with the further news regarding the issue.
Comments
7 comments
After the command "run-parts /etc/cron.hourly/" nothing happens, it seems stuck.
Hi @info!
It might be possible in case there were an interference with another task that was running from /etc/cron.hourly/. In general, in case there were no errors right after the start of run-parts, just interrupt the process.
That worked. After waiting about 10-15 minutes step 3 finished, and I could proceed to step 4. Thanks!
It worked! :)
I don't understand this page : it says the issue has been resolved on atomic side, if so why os it still hapening? (last alert 2 min ago)
Hi, @Arnaud!
Based on our information, fix should he delivered in scope of the rule set updates, in case the issue is still actual, force the Atomic Basic ModSecurity rule set update by switching it on and off via Tools & Settings > Web Application Firewall.
aum -c gives -bash: aum: command not found
yum remove aum
downloaded aum-4.0.18-36.el7.art.x86_64.rpm package
yum install aum-4.0.18-36.el7.art.x86_64.rpm
run-parts /etc/cron.hourly/
now gives me new error
This Helped
https://support.plesk.com/hc/en-us/articles/115000143534-ModSecurity-failed-to-update-rule-set-modsecurity-ctl-failed-HTTP-Error-403-Forbidden
Please sign in to leave a comment.