Malzahn

Uninstall and reinstall worked for me, too. While working, this is not a satisfactory solution since I had to redo all the configuration. And as Cybertooth pointed out - let's see how long it lasts.

Concretely I've done the following: sudo systemctl stop esets sudo rm /var/opt/eset/esets/lib/* sudo rm -r /var/opt/eset/esets/lib/data/updfiles/* sudo systemctl start esets Result in a a few minutes of downloading data (network load) etc with no terminal output followed by: Job for esets.service failed because a timeout was exceeded. See "systemctl status esets.service" and "journalctl -xe" for details. sudo systemctl status esets Results in the following terminal output: ● esets.service - ESET NOD32 Antivirus Loaded: loaded (/lib/systemd/system/esets.service; enabled; vendor preset: enabled) Active: failed (Result: timeout) since Mon 2020-11-23 10:50:16 CET; 1min 20s ago Process: 5292 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=killed, signal=TERM) Nov 23 10:48:45 mertins007 systemd[1]: Starting ESET NOD32 Antivirus... Nov 23 10:50:16 mertins007 systemd[1]: esets.service: Start operation timed out. Terminating. Nov 23 10:50:16 mertins007 systemd[1]: esets.service: Failed with result 'timeout'. Nov 23 10:50:16 mertins007 systemd[1]: Failed to start ESET NOD32 Antivirus. Trying sudo systemctl start esets fails with the same message as above, but sudo systemctl status esets results in: ● esets.service - ESET NOD32 Antivirus Loaded: loaded (/lib/systemd/system/esets.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2020-11-23 10:53:48 CET; 31s ago Process: 5582 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=69) Nov 23 10:53:44 mertins007 systemd[1]: Starting ESET NOD32 Antivirus... Nov 23 10:53:48 mertins007 esets_daemon[5582]: error[15ce0000]: Cannot initialize scanner: Module init Nov 23 10:53:48 mertins007 esets_daemon[5582]: error[15ce0000]: Cannot initialize scanner: Module init Nov 23 10:53:48 mertins007 systemd[1]: esets.service: Control process exited, code=exited status=69 Nov 23 10:53:48 mertins007 systemd[1]: esets.service: Failed with result 'exit-code'. Nov 23 10:53:48 mertins007 systemd[1]: Failed to start ESET NOD32 Antivirus. So for me unfortunately no success for me. Please let me know if I interpreted your instructions wrong and or how to proceed.

Hi @Marcos, Your previous suggestions didn't work for me or @Cybertooth as posted by both of us on Friday. We also could not completely execute them, since we don't have an esets_update program. Maybe these instructions are for a different linux software version (e.g. the buisiness version)? We also provided additional information on Friday in case they might be useful. Please advice how to proceed.

I could not see a "modules" directory in /var/opt/eset/esets/lib/ . The only directory is data Neither removing only the *.dat and files in /var/opt/eset/esets/lib/data/updfiles/ (one machine) nor removing everything in lib (other machine) resulted in success. I do not have a /opt/eset/esets/sbin/esets_update file the only files in sbin are esets_daemon esets_scan esets_set Restarting with sudo systemctl start esets resulted in: Job for esets.service failed because the control process exited with error code. See "systemctl status esets.service" and "journalctl -xe" for details. systemctl status esets.service resulted in: ● esets.service - ESET NOD32 Antivirus Loaded: loaded (/lib/systemd/system/esets.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-11-20 09:35:54 CET; 4min 41s ago Process: 4587 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=69) Nov 20 09:35:50 mertins007 systemd[1]: Starting ESET NOD32 Antivirus... Nov 20 09:35:54 mertins007 esets_daemon[4587]: error[11eb0000]: Cannot initialize scanner: Module init Nov 20 09:35:54 mertins007 esets_daemon[4587]: error[11eb0000]: Cannot initialize scanner: Module init Nov 20 09:35:54 mertins007 systemd[1]: esets.service: Control process exited, code=exited status=69 Nov 20 09:35:54 mertins007 systemd[1]: esets.service: Failed with result 'exit-code'. Nov 20 09:35:54 mertins007 systemd[1]: Failed to start ESET NOD32 Antivirus.

For clarification this was the status before trying marcos steps.

For further info: /opt/eset/esets/sbin/esets_daemon --version returns 4.0.95 And insepcting/var/log/syslog shows many messages like the following: Nov 20 08:37:29 mertins007 systemd[1]: Failed to start ESET NOD32 Antivirus. Nov 20 08:37:30 mertins007 systemd[1]: esets.service: Service hold-off time over, scheduling restart. Nov 20 08:37:30 mertins007 systemd[1]: esets.service: Scheduled restart job, restart counter is at 2943. Nov 20 08:37:30 mertins007 systemd[1]: Stopped ESET NOD32 Antivirus. in between these there is this message: Nov 20 08:32:04 mertins007 kernel: [52700.292288] audit: type=1400 audit(1605857524.775:463): apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" name="/opt/eset/esets/lib/libesets_pac.so" pid=31210 comm="krb5_child" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Nov 20 08:32:04 mertins007 kernel: [52700.292290] audit: type=1400 audit(1605857524.775:464): apparmor="ALLOWED" operation="file_mmap" profile="/usr/sbin/sssd" name="/opt/eset/esets/lib/libesets_pac.so" pid=31210 comm="krb5_child" requested_mask="rm" denied_mask="rm" fsuid=0 ouid=0 Nov 20 08:32:04 mertins007 kernel: [52700.293724] audit: type=1400 audit(1605857524.775:465): apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" name="/etc/opt/eset/esets/info/pkgid" pid=31210 comm="krb5_child" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Maybe these infos help figuring out the problem.

I had the excact same problem yesterday on two kubuntu 18.04 machines, also Plasma 5.12.9. Absolutely blocked system (only occasionally reaction slightly) with red ESET notifcation icon. Hard reboot, followed by normally working system but not ESET gui icon. /opt/eset/esets/bin/esets_gui --version returns 4.0.95 for me. libappindicator1 was already installed package version 12.10.1+18.04.20180322.1-0ubuntu1 The indicator and gui was also working till yesterday earlier.