[esets_daemon freeze - 2020 version]

solution (just tested with one of our systems) for our site:
 

[root@vm /]# cd /var/opt/eset/esets/lib
[root@vm lib]# mv em002_32.dat em002_32.dat.o

[root@vm lib]# cd /opt/eset/esets/sbin/
[root@vm sbin]# ./esets_update --verbose
Virus signature database has been updated successfully.                        
ESETS Update utility
+-+--------------------+------------------------+------------------------+
| | Module             | Available version      | Installed version      |
+-+--------------------+------------------------+------------------------+
|*| loader             |        1076 (20200313) |                        |
|*| perseus            |      1566.4 (20201006) |                        |
|*| engine             |       22334 (20201117) |                        |
|*| archiver           |        1310 (20201029) |                        |
|*| heuristic          |        1203 (20201015) |                        |
|*| cleaner            |        1214 (20200921) |                        |
| |                    |                        | �o}��Ue��o}��<{��0|�p6{�0�[�� |
| |                    |                        |                        |
| |                    |                        |                      
                                                                        |
+-+--------------------+------------------------+------------------------+
[root@vm sbin]# ./esets_update --verbose
Update is not necessary - the installed virus signature database is current.   
ESETS Update utility
+-+--------------------+------------------------+------------------------+
| | Module             | Available version      | Installed version      |
+-+--------------------+------------------------+------------------------+
| | loader             |        1076 (20200313) |        1076 (20200313) |
| | perseus            |      1566.4 (20201006) |      1566.4 (20201006) |
| | engine             |       22334 (20201117) |       22334 (20201117) |
| | archiver           |        1310 (20201029) |        1310 (20201029) |
| | heuristic          |        1203 (20201015) |        1203 (20201015) |
| | cleaner            |        1214 (20200921) |        1214 (20200921) |
+-+--------------------+------------------------+------------------------+
[root@vm sbin]# systemctl start esets
[root@vm sbin]# systemctl status esets
● esets.service - ESET Scanner Daemon
   Loaded: loaded (/usr/lib/systemd/system/esets.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2020-11-19 16:59:09 CET; 4s ago
  Process: 94942 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=0/SUCCESS)
 Main PID: 94943 (esets_daemon)
   CGroup: /system.slice/esets.service
           ├─94943 /opt/eset/esets/sbin/esets_daemon
           ├─94944 /opt/eset/esets/sbin/esets_daemon
           └─94945 /opt/eset/esets/lib/esets_wwwi

 

 

[esets_daemon freeze - 2020 version]

Quote

same problem started the same time. Possible corruption of new patterns?

same problem using RHEL 6 and also on CentOS7

daemon and eset_update throwing secmentation fault. Update logfile and systemctl status:
 

[root@server eset]# cat /tmp/bt.esets_update.yBOi3p
/lib/ld-linux.so.2(+0x9ab6)[0xf779bab6]
/lib/ld-linux.so.2(+0x9ab6)[0xf779bab6]
/lib/ld-linux.so.2(+0xa356)[0xf779c356]
/lib/libc.so.6(+0x134aec)[0xf76d0aec]
/lib/libc.so.6(_dl_sym+0x1a)[0xf76d0f8a]
/lib/libdl.so.2(+0xdf1)[0xf775cdf1]
/lib/ld-linux.so.2(+0xf9ba)[0xf77a19ba]
/lib/libdl.so.2(+0x138c)[0xf775d38c]
/lib/libdl.so.2(dlsym+0x58)[0xf775ce58]
./esets_update(_Z9nod_dlsymP11_nod_dll_t_PKc+0x3f)[0x809fccf]
./esets_update(_Z31AppGetProcAddressImplementationPvPKcPS_+0x25)[0x808bf34]
./esets_update(_Z12api_callbackjz+0x14fa)[0x8072d72]
[0xf723295d]
[0xf70c3f42]
[0xee25c7e6]
[0xee3f86fa]
[0xee3f863a]
signal = 11
bad addr = 0xcfc00004

[root@vm esets]# systemctl status esets
● esets.service - ESET Scanner Daemon
   Loaded: loaded (/usr/lib/systemd/system/esets.service; enabled; vendor preset: disabled)
   Active: inactive (dead) since Thu 2020-11-19 15:05:32 CET; 1h 36min ago
 Main PID: 35664 (code=exited, status=0/SUCCESS)

Nov 19 15:05:05 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[92027] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:08 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57176] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:10 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57270] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:13 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57280] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:16 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57290] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:18 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57300] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:21 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57310] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:23 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57320] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:27 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57330] did not handle signal 11, restart in 0 seconds
Nov 19 15:05:29 vm esets_daemon[35664]: error[8b500000]: Child process esets_daemon[57342] did not handle signal 11, restart in 0 seconds