Jump to content

Krzysztof L.

  • Content Count

  • Joined

  • Last visited

Everything posted by Krzysztof L.

  1. Hi, I also have this problem, it has occurred since 22/01/2021. Eset mail security crashes once a day (more or less every 24h). Nothing in logs... also no bt.esets_daemon.* files in /tmp/ directory. Centos 7 3.10.0-1160.11.1.el7.x86_64 # /opt/eset/esets/sbin/esets_update --version /opt/eset/esets/sbin/esets_update (esets) 4.5.15 # esets_update --verbose Update is not necessary - the installed virus signature database is current. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module | Available version
  2. I also confirm that solution from you all is working. Thank you all. (Burk code) cd /var/opt/eset/esets/lib ls -la mv em002_32.dat em002_32.dat.o cd /opt/eset/esets/sbin/ ./esets_update --verbose systemctl start esets systemctl status esets Povas i agree, we need to wait for next update.
  3. It looks like the problem is back again. I think Is is happen after todays update at 2PM. /opt/eset/esets/sbin/esets_daemon --version /opt/eset/esets/sbin/esets_daemon (esets) 4.5.15 There is a lot of /tmp/bt.esets_daemon.* files cat bt.esets_daemon.EkR1IE signal = 11 bad addr = 0xcfc00004 /opt/eset/esets/sbin/esets_update --verbose Naruszenie ochrony pamięci (translate: Memory protection violation) Esets hung in starting loop systemctl start esets.service Job for esets.service failed because a fatal signal was delivered to the control process. See "s
  4. I also confirm this problem. I have now changed the file name em001_32.dat and make update. Now we will wait and watch. # /opt/eset/esets/sbin/esets_update --verbose Virus signature database has been updated successfully. ESETS Update utility +-+--------------------+------------------------+------------------------+ | | Module | Available version | Installed version | +-+--------------------+------------------------+------------------------+ |*| loader | 1074.1 (20190925) | | |*| perseus | 1555 (201909
  5. It is now 24 hours of stable working , few days more and we will be full stable. Thank you.
  6. Hi Dingolino, You are not alone with this problem, this is fresh bug, go here -->
  7. Yes i confirm this bug. My system is: CentOS Linux release 7.5.1804 (Core) (esets) 4.5.11 But is also happen on esets 4.5.9 (i just updated it to 4.5.11). First occurred of this bug is 25/10/2018 at 4pm. Now its happen about one/two times a day. To Eset support team - Please check what are you changed in last week. In my recognition only engine module was changed in this day. While esets daemon is freezed then i UNABLE to restart it by command: # systemctl restart esets.service i need to: # /usr/bin/killall -u esets -9 and then start eset again. Some ot
  8. Michal, my mails are scanned only 8 hours a day, then I disable the postfix-eset connection and go home. By these 8 hours a day works well (last 2 days). I think this is a topic for support, but this forum is more for ordinary users and not for real support. I think we need to contact eset support directly. Michal please write more about your configuration. Perhaps it will be helpful to someone. Our postfix is on another machine than eset mail security. Both machines are virtual (vsphere 6.5). Postfix communicates with eset through the 'content filter' configuration: main.cf content_fi
  9. We have the same problem as Michal wrote. Yesterday, esets_deamon (Eset mail security for linux) entered a strange state. Telnet to eset smtp module works good but all messages goes back to postfix with status: "delivery temporarily suspended: conversation with xxx[yyy] timed out while receiving the initial server greeting". There is nothing interesting in eset logs. As an workaround we also need to restart whole virtual machine (Linux Centos 7.4). update 11:00 2017-10-04 its happened again, 3 hours after the reboot. Maybe the reason is any of newests up
  • Create New...