Jump to content


  • Posts

  • Joined

  • Last visited

About M3741

  • Rank

Profile Information

  • Location
  1. Whenever I update my system a new snapshot of my system files (/ FS) is created (so I can rollback if something goes bad [hurray for zypper snapper and BTRFS!]). The problem is, whenever a snapshot is found, EAV 4 Linux starts to scan it fully, which brings my machine to an IO starvation situation. I mean, I understand this is how EAV 4 Linux is meant to work, it sees 'new' files being written so it automatically scans them to make sure they are not infected. However these are not really new files, they are snapshots of files I already had and were already scanned by previous system scans. I have tried adding /.snapshots/* path to EAV 4 Linux's exclusion list, but it doesn't seem to work. Browsing the forums I've seen @Marcos post about EAV 4 Linux not being developed anymore and that it'll be replaced by something based on Endpoint 7 next year. Is there a solution to this issue? Will the next product address this issue? Thanks
  2. I tried the "Windows Admin Approach" of uninstalling, downloading the latest installer and reinstalling the product and it seems to have worked. What was the underlying issue I have no idea. T430:/ # LANG=C systemctl status esets ● esets.service - LSB: ESET NOD32 Antivirus Loaded: loaded (/etc/init.d/esets; generated) Active: active (running) since Thu 2020-11-19 13:21:12 -03; 5min ago Docs: man:systemd-sysv-generator(8) Process: 1377 ExecStart=/etc/init.d/esets start (code=exited, status=0/SUCCESS) Tasks: 11 (limit: 4915) CGroup: /system.slice/esets.service ├─1484 /opt/eset/esets/sbin/esets_daemon ├─1485 /opt/eset/esets/sbin/esets_daemon └─1486 /opt/eset/esets/lib/esets_mac Nov 19 13:21:08 T430 systemd[1]: Starting LSB: ESET NOD32 Antivirus... Nov 19 13:21:12 T430 esets[1377]: Starting ESET NOD32 Antivirus..done Nov 19 13:21:12 T430 systemd[1]: Started LSB: ESET NOD32 Antivirus. /me tips hat towards win admins out there.
  3. Can confirm. I'm having the exact same issue as of today. T430:/ # /opt/eset/esets/sbin/esets_daemon --version /opt/eset/esets/sbin/esets_daemon (esets) 4.0.93 T430:/ # T430:/ # ls -l /tmp/bt.esets_daemon.* | wc -l 143 T430:/ # cat /tmp/bt.esets_daemon.zQcNEM /lib/ld-linux.so.2(+0xac36)[0xf7f38c36] /lib/ld-linux.so.2(+0xac36)[0xf7f38c36] /lib/ld-linux.so.2(+0xb735)[0xf7f39735] /lib/libc.so.6(+0x14750b)[0xf7d2f50b] /lib/libdl.so.2(+0x1441)[0xf7ddd441] /lib/libc.so.6(_dl_catch_exception+0xa3)[0xf7d2fc53] /lib/libc.so.6(_dl_catch_error+0x30)[0xf7d2fd30] /lib/libdl.so.2(+0x1b11)[0xf7dddb11] /lib/libdl.so.2(dlsym+0x71)[0xf7ddd4c1] /opt/eset/esets/lib32/libesets.so.4(_Z9nod_dlsymP11_nod_dll_t_PKc+0x4b)[0xf7e4c732] /opt/eset/esets/lib32/libesets.so.4(+0x4a91e)[0xf7e6d91e] /opt/eset/esets/lib32/libesets.so.4(+0x16f1c)[0xf7e39f1c] [0xeda6d95d] [0xeb093f42] [0xe23637e6] [0xe24ff6fa] [0xe24ff63a] signal = 11 bad addr = 0xd4 T430:/ #
  • Create New...