[esets_daemon freeze]

Hello dmenl,

Thank you for your information.

In case of our customer, too, this issue has not occurred since restarting all esets services yet.

 

@Peter

After updating to DB module 1095, is the restarting all esets services necessary to fix this bug?

 

Best regards,

Satoshi

[esets_daemon freeze]

Hello Peter,

thank you for your reply.
We understood that this problem has not occurred elsewhere.

My colleague reported this case as TICKET 207524.
Unfortunately, the customer did not know the way to generate core files of esets processes from the frozen state at that time.
Therefore, we have asked the customer to generate core files when freeze happened next.

Thank you.

Best regards,
Satoshi

[esets_daemon freeze]

Hello,

Our customer called us that the freeze happened after updating to Database module 1095 again. 
The following error was written in maillog of postfix.

Dec 13 13:38:20 XXXXXX postfix/smtp[11483]: XXXXXXXX: to=<XXXX@XXXXXXXX.XX>, relay=127.0.0.1[127.0.0.1]:2526, delay=300, delays=0.05/0/300/0, dsn=4.4.2, status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while receiving the initial server greeting)

And, we confirmed in data.txt of customer that the EMSL was updated to DB module 1095 as below.
--------------------------------------------
modules:
em000_32.dat:14:version: 1069 (20161122)
em000_32.dat:15:build: 1112
em000_32.dat:17:type: loader module
em001_32.dat:5:version: 1533.2 (20171205)
em001_32.dat:6:build: 1927
em001_32.dat:8:type: perseus module
em002_32.dat:5:version: 16563 (20171212)
em002_32.dat:6:build: 35712
em002_32.dat:8:type: engine module
em003_32.dat:5:version: 1270 (20171113)
em003_32.dat:6:build: 1332
em003_32.dat:8:type: archives module
em004_32.dat:5:version: 1184 (20171110)
em004_32.dat:6:build: 1156
em004_32.dat:8:type: heuristic module
em005_32.dat:5:version: 1152 (20171127)
em005_32.dat:6:build: 1207
em005_32.dat:8:type: cleaner module
em006_32.dat:5:version: 1118 (20171108)
em006_32.dat:6:build: 1169
em006_32.dat:8:type: antistealth module
em013_32.dat:5:version: 1018 (20100812)
em013_32.dat:8:type: self-defense module
em021_32.dat:5:version: 6585 (20171212)
em021_32.dat:6:build: 12801
em021_32.dat:8:type: horus module
em022_32.dat:5:version: 1095 (20171206)
em022_32.dat:6:build: 1100
em022_32.dat:8:type: DB module
em023_32.dat:5:version: 11276 (20171212)
em023_32.dat:6:build: 11427
em023_32.dat:8:type: pegasus module
em034_32.dat:5:version: 1019 (20170825)
em034_32.dat:6:build: 1023
em034_32.dat:8:type: antistealth helper module
--------------------------------------------

We reported this case to GPC already.

Are there any other cases where this problem occurred after updating to DB module 1095?

Best regards,
Satoshi