IM Scanner running 10 hours+

[alik.ross]

IM scanner has been running on vhosts/* for 10 hours now and still going. This seems rather long.

Is this normal? Any insight appreciated.

Running Centos 7 on Plesk 17.x with Meltdown updates applied.

thx
G

[oshchukin]

Hi Glenn,

Malware scan can be time consuming process not only due to vhosts/* size, but also because of IM malware scan is run with the lowest cpu nice priority=19 and low ionice priority (ionice class best-effort, ionice priority=6). For sure that can the reason for IM malware scan to slow down, if your server is under load, and that is only because your server primary mission services (httpd, mysqld) are given higher priority.

Feel free to readjust cpu nice or ionice priority for IM malware scan process by using `renice`, `ionice` tools respectively in a case you want to get IM malware scan process results earlier.

If you think IM scan is stuck (you can check that with `strace -p`), please open zendesk ticket and provide us with server access so we can find the reason and fix it.

Kind regards,
Oleksiy Shchkin
Imunify360 developer