Clamav-daemon and mariadb Services Not Starting Automatically After HestiaCP v1.9.1 Update

Hi everyone,

I recently updated my Hestia Control Panel to version 1.9.1, and I’ve noticed that after a system reboot, some services like clamav-daemon and mariadb do not start automatically. However, when I start them manually using systemctl start clamav-daemon mariadb, they run without any issues.

Has anyone else faced a similar issue after updating HestiaCP? Are there any configuration changes or additional steps needed to ensure these services start automatically on boot?