Hello everyone,
all of a sudden ESET NOD32 stopped working on my system.
In the syslog i'll see output like this:
Nov 19 18:41:20 hostname systemd[1]: Starting ESET NOD32 Antivirus...
Nov 19 18:41:20 hostname systemd-coredump[23185]: Process 23166 (esets_daemon) of user 0 dumped core.#012#012Stack trace of thread 23166:#012#0 0x00000000f7fd74ba n/a (ld-linux.so.2)#012#1 0x00000000f7fd802b n/a (ld-linux.so.2)#012#2 0x00000000f7da850c n/a (libc.so.6)#012#3
0x00000000f7e50de1 n/a (libdl.so.2)#012#4 0x00000000f7da8b70 _dl_catch_exception (libc.so.6)#012#5 0x00000000f7da8c20 _dl_catch_error (libc.so.6)#012#6 0x00000000f7e513e1 n/a (libdl.so.2)#012#7 0x00000000f7e50e63 dlsym (libdl.so.2)#012#8 0x00000000f7ebf732 _Z9nod_dlsymP11_nod_
dll_t_PKc (libesets.so.4)#012#9 0x00000000f7ee091e n/a (libesets.so.4)#012#10 0x00000000f7eacf1c n/a (libesets.so.4)#012#11 0x00000000f7a2a95d n/a (n/a)#012#12 0x00000000f78bbf42 n/a (n/a)#012#13 0x00000000eea547e6 n/a (n/a)#012#14 0x00000000eebf06fa n/a (n/a)
Nov 19 18:41:22 hostname systemd[1]: Started Process Core Dump (PID 23217/UID 0).
Nov 19 18:41:22 hostname systemd[1]: esets.service: Control process exited, code=dumped status=11
Nov 19 18:41:22 hostname systemd[1]: esets.service: Failed with result 'core-dump'.
Nov 19 18:41:22 hostname systemd[1]: Failed to start ESET NOD32 Antivirus.
Nov 19 18:41:22 hostname systemd[1]: esets.service: Service hold-off time over, scheduling restart.
Nov 19 18:41:22 hostname systemd[1]: esets.service: Scheduled restart job, restart counter is at 94.
Nov 19 18:41:22 hostname systemd[1]: Stopped ESET NOD32 Antivirus.
i've reinstalled/repaired the installed version, updated to the latest available version without success.
Does anyone else have this issue too or an idea what it might be?
Kind regards
Frank