systemd[1]: eea.service: Failed with result 'timeout'.

[abyss02 0]

Hi all,

as ESET NO32 for Linux Desktop has been announced to be discontinued in 2022, i decided to migrate to ESET Endpoint Antivirus. I deployed an Eset Mgmt Appliance and installed the Eset Client to 2 Linux Server (Ubuntu 20.04) and one Fedora 34 Laptop. I actived all of them and registered them via agent installation.

So far so good, but.

If i restart the eea service on the fedora laptop, i randomply get a system load up to 9 (!) and i see this here after the load is back to <1:

 

systemctl status eea
● eea.service - ESET Endpoint Antivirus
     Loaded: loaded (/usr/lib/systemd/system/eea.service; enabled; vendor preset: disabled)
     Active: active (running) since Wed 2021-08-25 16:18:53 CEST; 1min 14s ago
    Process: 6473 ExecStartPre=/opt/eset/eea/lib/install_scripts/check_start.sh (code=exited, status=0/SUCCESS)
    Process: 6555 ExecStartPost=/bin/sleep 2 (code=exited, status=0/SUCCESS)
    Process: 6619 ExecStartPost=/opt/eset/eea/lib/install_scripts/launch_gui_all_users.sh (code=exited, status=0/SUCCESS)
   Main PID: 6554 (startd)
      Tasks: 34 (limit: 18807)
     Memory: 1.2G
        CPU: 7.669s
     CGroup: /system.slice/eea.service
             ├─6554 /opt/eset/eea/sbin/startd
             ├─6580 /opt/eset/eea/lib/logd
             ├─6588 /opt/eset/eea/lib/scand
             ├─6589 /opt/eset/eea/lib/sysinfod
             ├─6590 /opt/eset/eea/lib/updated
             ├─6591 /opt/eset/eea/lib/licensed
             ├─6593 /opt/eset/eea/lib/utild
             ├─6594 /opt/eset/eea/lib/confd
             └─6602 /opt/eset/eea/lib/oaeventd

Aug 25 16:17:48 t14 systemd[1]: eea.service: Failed with result 'timeout'.
Aug 25 16:17:48 t14 systemd[1]: eea.service: Unit process 3391 (oaeventd) remains running after unit stopped.
Aug 25 16:17:48 t14 systemd[1]: Stopped ESET Endpoint Antivirus.
Aug 25 16:17:48 t14 systemd[1]: eea.service: Consumed 42.029s CPU time.
Aug 25 16:17:48 t14 systemd[1]: eea.service: Found left-over process 3391 (oaeventd) in control group while starting unit. Ignoring.
Aug 25 16:17:48 t14 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Aug 25 16:17:48 t14 systemd[1]: Starting ESET Endpoint Antivirus...
Aug 25 16:18:53 t14 runuser[6648]: pam_unix(runuser:session): session opened for user andreas(uid=1000) by (uid=0)
Aug 25 16:18:53 t14 runuser[6648]: pam_unix(runuser:session): session closed for user andreas
Aug 25 16:18:53 t14 systemd[1]: Started ESET Endpoint Antivirus

 

What does this mean, is that a bug? Does anyone else experince this?

Regards,

Andreas

 

[J.J. 24]

Hello

Fedora distribution is not supported by ESET Endpoint Antivirus for Linux Desktop

https://help.eset.com/eeau/8/en-US/?system_requirements.html

The following operating systems of 64-bit architecture are officially supported and tested:

•Ubuntu Desktop 18.04 LTS 64-bit

•Ubuntu Desktop 20.04 LTS

•Red Hat Enterprise Linux 7, 8 with supported desktop environment installed.

•SUSE Linux Enterprise Desktop 15