Why have the ESET and Kaspersky scan engines failed to initialize on the hardened Linux OS?
This article applies to all MetaDefender Core V5 and V4 releases deployed on hardened Linux systems.
For customers using a hardened Linux OS, such as Hardened Amazon Linux 2, the ESET and Kaspersky engines will fail to initialize unless certain changes are made.
The ESET and Kaspersky scan engines require execution permission on a temp folder. However, while on the hardened system, such permissions are restricted on: /var/tmp, resulting in the engines’ failure to initialize.
Browse MetaDefender Configuration for instructions on how to change the default temp folder (tempdirectory) to a folder that has execution permission.
If you have followed all of the steps above but your ESET and Kaspersky engines are still failing to initialize, please follow these instructions on auto$, before creating a support case or chatting with our support engineer.