I've been running "Eset 32 4 Linux" happily for the past few months with no issues. Suddenly today I started having problems with the daemon. On boot up my computer started running extremely slow and froze for about five minutes. Looking at the logs I noticed there were a long stream of problems related to the ESET demon.
The logs are attached below in full but what was basically repeated was:
Cannot send message "Cannot scan: Daemon closed connection": Resource temporarily unavailable
Cannot read from socket: Resource temporarily unavailable
Cannot send message "Cannot read from socket: Resource temporarily unavailable": Resource temporarily unavailable
Cannot scan: Daemon closed connection
Cannot connect to /tmp/esets.sock: Resource temporarily unavailable
Cannot send message "Cannot connect to /tmp/esets.sock: Resource temporarily unavailable": Resource temporarily unavailable
and a core dump:
Process 657 (esets_daemon) of user 0 dumped core.
Stack trace of thread 660:
#0 0x00000000f7580069 inet_pton (libc.so.6)
#1 0x00000000f0b02f0b n/a (libnss_files.so.2)
#2 0x00000000f0b03360 _nss_files_gethostbyname3_r (libnss_files.so.2)
#3 0x00000000f0b03944 _nss_files_gethostbyname2_r (libnss_files.so.2)
#4 0x00000000f75751ce gethostbyname2_r@@GLIBC_2.1.2 (libc.so.6)
#5 0x00000000f754ac4a gaih_inet (libc.so.6)
#6 0x00000000f754c19f getaddrinfo (libc.so.6)
#7 0x00000000f769fe21 n/a (libesets.so.4)
#8 0x00000000f769ff27 _Z24nod_sockaddr_create_inetPKci (libesets.so.4)
#9 0x00000000f76cb5f2 n/a (libesets.so.4)
#10 0x00000000f76cc2e0 n/a (libesets.so.4)
#11 0x00000000f768673f n/a (libesets.so.4)
#12 0x00000000f768f3d9 n/a (libesets.so.4)
#13 0x00000000f775335a n/a (n/a)
I attempted to uninstall and reinstall with a fresh up-to-date install; however, the new fresh install won't even run.
Here are the resulting logs after attempting to run on a fresh install.:
Starting ESET Scanner Daemon...
Cannot initialize scanner: Module init
Control process exited, code=exited status=69
Failed to start ESET Scanner Daemon.
Unit entered failed state.
Failed with result 'exit-code'.
Service hold-off time over, scheduling restart.
Stopped ESET Scanner Daemon.
Start request repeated too quickly.
Failed to start ESET Scanner Daemon.
Has something recently been changed and can anything be made of these logs?
I attached the logs I found relevant.
eset.log
