On-demand scan on Linux doesn't respect the scheduled time when the machine resumes from sleep
Hello! In short, my problem is the following: On the Linux machines where BEST is installed, we configured the on-demand scan to run from Monday to Friday at 3:00 AM and NOT to try to run again if the execution time has been missed.
It turns out that, on the machines that users suspended overnight, the scan happens in the morning exactly when the machine wakes up from the suspend state. Since the scan consumes a lot of disk and CPU resources, users notice a significant impact on the performance of their activities at the beginning of their workday.
We collected some journalctl logs from two of these machines and identified the following pattern:
Machine A:Apr 30 07:41:40 MACHINE-A systemd-sleep[109147]: System returned from sleep operation 'suspend'.2025-04-30T07:41:41.750-03:00 MACHINE-A bdsecd[2093][2351]: info: UPDATE: Received UpdateStarted for product started by scheduled
Scan Log created at 30 April 2025, 7:41:47
Machine B:Apr 30 09:18:24 MACHINE-B systemd-sleep[244776]: System returned from sleep operation 'suspend'.2025-04-30T09:18:23.903-03:00 MACHINE-B bdsecd[2474][2853]: info: UPDATE: Received UpdateStarted for product started by scheduled
Scan Log created at 30 April 2025, 09:18:43
We have tried every possible configuration in GravityZone and still cannot stop the full scan from happening as soon as these users return to work. Is this a bug in BitDefender? In Linux itself? This has been impacting our team a lot.
Answers
-
Hello @saulo.guilhermino ,
As far as I know there is no configuration that would led to this scenario. Please open a case to be investigated with support so we can determine the root cause.
Attach all the logs collected so we can review them as well.
Thank you,
Andrei
0
