Sudden Errors and Daemon Crashing

[Bubba 0]

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

[kooalaa 0]

Hi there, 

 

same symptoms and messages here.

[trayntab 0]

same problem here

need help!

Xubuntu 16.04.1 and 16.10 (new System)

[trayntab 0]

hi,

i found a way to install eset without any problems!!!!

https://ubuntu-mate.community/t/how-to-run-eset-nod32-for-linux-in-ubuntu-mate-16-04-or-16-10/9733/13

Quote

So here is a step by step instruction how I got it to work on any machine I have tried.

1. Download from ESET
2. Mark it as "Executable"
3. Install the library libc6 32bit, with sudo apt install libc6:i386
   It is critical to use it like this with : , not like described here hxxp://support.eset.com/kb5827/2 with - between libc6 and i386. Installing it with - causes the system to freeze.
4. Double click the downloaded file and install it. Restart and activate.
5. To start it from the Systray-Icon, just click on the icon. To start it from the menu, change the Exec line in /usr/share/applications/eset-esets_gui.desktop to Exec=/opt/eset/esets/lib/esets_clean.sh

 

now it's working normaly without errors and freezes!

 

Best regards

trayntab

[Defalt Hackinson 0]

On 31/12/2016 at 10:30 AM, trayntab said:

hi,

i found a way to install eset without any problems!!!!

https://ubuntu-mate.community/t/how-to-run-eset-nod32-for-linux-in-ubuntu-mate-16-04-or-16-10/9733/13

now it's working normaly without errors and freezes!

 

Best regards

trayntab

I have a trouble here... Debian complains about not finding the library with the colon. What should I install in this case?

defalt@x54hr:~$ sudo apt install libc6:i386
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias       
Leyendo la información de estado... Hecho
Package libc6:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libc6:i386' has no installation candidate

 

[trayntab 0]

i have no debian vm here

hxxp://stackoverflow.com/questions/37313639/whats-the-difference-between-libc6i386-and-libc6-i386

Edited January 24, 2017 by trayntab

[trayntab 0]

dpkg --add-architecture i386
apt-get update

and then install the right package ? maybe?

Edited January 24, 2017 by trayntab

[helpneeded 0]

Hi,

I encountered the following errors since 3 December 2017 with ESET Nod32 (version 4.0.85) on Ubuntu 16.04.3 LTS (4.10.0-40-generic #44~16.04.1-Ubuntu SMP). Laptop model HP Pavilion 14-bf057tx

 

1. ESET Daemon Cannot initialize scanner: Module init (Note: NESET Daemon will not load after reboot and I need to reinstall NOD32)
2. ESET Daemon Error updating Antivirus modules: File corrupted.
3. ESET Daemon Error updating Antivirus modules: Unidentified server response.    
4. ESET Daemon Cannot read from socket: Connection reset by peer.
5. ESET Daemon Error updating Antivirus modules: File not found on server.    
6. After repeated reinstallation attempts, NOD32 is still showing incorrect database version (see attached screenshot).
7. I noticed that NOD32 is trying to download a large file (31 – 80 MB) during each update attempt. I last successfully updated NOD32 on 29 November 2017.
8. After 2 successful update attempts on 5 December 2017, I suddenly encountered the “ESET Daemon Cannot initialize scanner: Module init” error. After rebooting, ESET Daemon was unable to startup. Subsequently, I was unable to update the database despite multiple reinstallation attempts.

I tried the following:

1. Installed libc:i386 and uninstalled libc-i386
2. Uninstalled NOD32 using the default uninstaller (esets_gil)
3. Reinstalled NOD32 using the installer downloaded from ESET website (eset_nod32av_64bit_en.linux)
4. Manually removed the em*.dat files from /var/opt/eset/esets/lib before updating the database.
5. Manually moved the em*.dat files from /var/opt/eset/esets/lib to another folder before updating the database.
6. Previously, I encountered read-only file system error with /var/opt/eset/esets/lib. I used a Live USB to boot the system, unlocked and mounted the encrypted volume, switch to chroot and remove the em*.dat files from /var/opt/eset/esets/lib and restart.

Appreciate your advice. Thanks.

Edited December 5, 2017 by helpneeded
Provide additional details.

[helpneeded 0]

Hi,

1. I encountered the same error (ESET Daemon Cannot initialize scanner: Module init) again tonight (22 Dec 17). My last successful update was on 17 Dec 17 (Sunday).

2. I had to uninstall and reinstall the software several times.

3. After repeated update attempts (both manual and scheduled automatic), my ESET virus database is still stuck at 13825 (20160719) which is even older than the default baseline that comes with version 4.0.85 (15366 (20170505)).  Please refer to original screenshot.

Appreciate your advice. Thanks.