kurco

Hi kees, this is result of one package that is supporting ubuntu 18/20/22 and therefore headers also for older versions are installed. Kernel modules compilation uses only headers for currently running kernel, if they are not present, compilation fails otherwise modules are build and loaded. Regards, Kurco

Yes, this link leads to correct package, but after installation there should be running efs service, not esets.

esets.service belongs to File Security v4.5, which is already end-of-life. Do you really want to install this version?

logs collector from Endpoint sudo /opt/eset/eea/sbin/collect_logs.sh

Hi, I have once again checked provided logs, but I can't see there anything about File Security installation. Without proper logs I'm not able to identify issues you are encountering. Please try to run installation of File Security on affected machine and after that collect system logs. Thanks, Kurco

Hi TecX, you don't need to enroll MOK every time, if you backup generated keys, you can always use the same ones to sign new kernel. sudo /opt/eset/eea/lib/install_scripts/sign_modules.sh -p /tmp/mok.priv -d /tmp/mok.der -a Regards, Kurco

I see, would it be possible to share system logs? without them I'm not able to give any suggestions what could be wrong.

econnd is responsible only for communication with other eset agents. What kind of desktop environment are you using?

Hi, kernel 5.15 is not affected, because it's compiled with default version of ubuntu gcc. But 6.5 is compiled with gcc version, which is not by default present and therefore it needs to be installed, because it is dependency for kernel modules compilation. Kurco.

Hi, it looks like you are encountering following issue: https://support.eset.com/en/kb8571-eset-service-fails-to-start-when-installing-eset-server-security-or-eset-endpoint-antivirus-for-linux-on-ubuntu-2204-or-mint-21 Regards, Kurco

Interesting, most probably it was really some misinterpretation of console, that nod32 appeared there. But back to the initial question, File Security uninstall is proceeded by system package manager, who is responsible for cleanup and removal. He can decide to left back some directories/files, but there is always some reason for it (e.g. some unknown file unrelated to package is present). Regards, Kurco

Hi, I have checked provided logs, but there is no info in management agent logs about detection of Nod32. If it is still possible, could you check if following folders /opt/esets/, /etc/opt/esets are existing on affected machine? Thanks.

Hi eornate, it look like enhanced security is enabled and package manager is unable to check GPG keys. Our package isn't signed and therefore installation is failing. You should be able to install efs manually, but you need to skip gpg check. sudo dnf install --nogpgcheck ./efs-10.2.41.0.x86_64.rpm Regards, Kurco

You are using version which is already in limited support and it's not working with latest kernel on Ubuntu 22.04. To resolve this issue, you need to upgrade to 10.1 or 10.2 (this is the best option, because 10.1 is also in limited support). Versions support could be checked here: Is my ESET product supported? | ESET End of Life | ESET End of Life

You can get version from installed packages list. dpkg --list | grep eea

Hi d4rk463, what version of Endpoint are you using? Regards, Kurco

Hi Mauricio, is it possible to share with us system logs? It is weird behavior, because uninstall is managed by system package manager (in your case dnf). Regards, Kurco

Hi wisnu, PopOs 22.04 isn't officially supported, but this post could help you to get it working (focus on step 5) Regards, Kurco

yes, please try it. Most probably it will have problems to collect everything (because of confd issue), but for now, it should be enough.

Hi BlueBear, Confd is part of Endpoint Antivirus, if you are getting this error, there is something wrong with your installation. Could you please share logs? without them it's really hard to tell what is wrong. Regards Kurco

Hi, from provided logs, I can see that you have enabled secure boot, therefore you need to sign kernel modules, before they can be loaded into system. (Secure boot | ESET Endpoint Antivirus for Linux | ESET Online Help)

Without any system/product logs, it is really hard to identify what is going on. Is it possible to share at least product event log (sudo /opt/eset/eea/sbin/lslog -ec)?

Hi Andres96, check this post: ESET not starting on Ubuntu 22.04 - ESET Endpoint Products for Linux - ESET Security Forum. Most probably you are experiencing same issue. Regards, Kurco

There was no need to remove (during remove products are always deactivated) and install eea again. After installation of gcc-12, it is enough to try again starting our service sudo systemctl start eea.

Hi, most probably you are experiencing issue with missing compiler. Ubuntu latest released kernel was compiled with gcc-12, but this version isn't by default installed there and it results into issue during our kernel modules compilation. Please try to install gcc-12 package (sudo apt install gcc-12) and start again our service. Regards, Kurco