file security error "Modules mapping directory not found" on SLES-12.4

[Axel.HARTH 2]

Hi,

 

I get the error "Cannot initialize scanner : Modules mapping directory not found " when I start the ESET file security.

I have a Linux server with the OS SLES-12.4 installed on it.

 

From a freshly installed Linux, I just install the glibc-locale-32bit and then I install the esets.x86_64.rpm.bin (version 4.5.11).

I have imported my license file and then I start eset with the command

$ systemctl start esets

 

And I get the error "Cannot initialize scanner : Modules mapping directory not found ".

 

Do you know what sould I do to fix this bug?

[J.J. 26]

24 minutes ago, Axel.HARTH said:

Hi,

 

I get the error "Cannot initialize scanner : Modules mapping directory not found " when I start the ESET file security.

I have a Linux server with the OS SLES-12.4 installed on it.

 

From a freshly installed Linux, I just install the glibc-locale-32bit and then I install the esets.x86_64.rpm.bin (version 4.5.11).

I have imported my license file and then I start eset with the command

$ systemctl start esets

 

And I get the error "Cannot initialize scanner : Modules mapping directory not found ".

 

Do you know what sould I do to fix this bug?

May I ask why are you installing 4.5.11 when 4.5.13 is available?

https://www.eset.com/int/business/file-security-linux/download/

- I would suggest to uninstall previous version and make clean install of version 4.5.13 and check if issue persist.

reboot system after uninstallation

[Axel.HARTH 2]

Thanks for your reply.

 

Due to a project constraint, I have to use the 4.5.11.

Before, we were installation this version of ESET on SLES 12.3 and it was working well.

We have recently moved to SLES 12.4 and we now get this error when starting the esets service.

 

For information, esets.service exit with status=69

 

[J.J. 26]

51 minutes ago, Axel.HARTH said:

Thanks for your reply.

 

Due to a project constraint, I have to use the 4.5.11.

Before, we were installation this version of ESET on SLES 12.3 and it was working well.

We have recently moved to SLES 12.4 and we now get this error when starting the esets service.

 

For information, esets.service exit with status=69

 

Just for testing purposes can you check if it is working with newest version? It could be interesting to know, if issue is present too with new version. There can be some changes in SLES 12.4

[J.J. 26]

I checked it at my SLES 12.4 and ESET File Security works for me. I find the cause of the issue. It is that Apparmor is enabled by default at SLES 12.4. It is needed to disable Apparmor completely and reboot the system and than install ESET File Security and it works as expected.

[Axel.HARTH 2]

HI,

 

Thanks for the reply.

If I understand well, ESET and apparmor cannot be run together?

[J.J. 26]

On 4/18/2019 at 4:27 PM, Axel.HARTH said:

HI,

 

Thanks for the reply.

If I understand well, ESET and apparmor cannot be run together?

Yes, you understand it correctly.   

[Axel.HARTH 2]

Hi J.J,

 

I try your configuration and it is working well.

Thanks for your help.

 

Axel