Symptoms
If a ClamAV scan gets stuck or when executing the start_scan API for a user it returns the following:
# uapi --user=bobby ClamScanner start_scan scan_type='mail';
apiversion: 3
func: start_scan
module: ClamScanner
result:
data: ~
errors:
- ClamAV® is disabled for this account.
messages: ~
metadata: {}
status: 0
warnings: ~
Description
This is caused because the cPanel account has either not been configured or configured to have all the scan disabled.
Examples:
The user bigdog has not been configured:
bigdog's user Settings:
Workaround
You can add the user in question to the Configured Users list by selecting the user in the User List and pressing the "add" button. This will apply the default values you have configured to the user:
An alternative solution is to configure the user individually by searching for the user in the text field under the ClamAV Scanner User Configuration section:
Comments
0 comments
Article is closed for comments.