Jump to content

Fedon Kadifeli

  • Posts

  • Joined

  • Last visited

About Fedon Kadifeli

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I installed ESET NOD32 to a Windows 10 VirtualBox 6.0.6 guest machine. The update is complete and its latest version ( is running. I am able to manually scan the local Windows drive (C :) without any problems. But, I cannot scan a drive, say H:, that is mapped to my host's (Ubuntu 19.04) home folder (/home/my_user) which is defined as a "shared folder" in VirtualBox: The scan completes immediately with 0 scanned objects. Here is the scan log: Log Scan Log Version of detection engine: 19645 (20190707) Date: 07/07/2019 Time: 1:42:37 PM Scanned disks, folders and files: H:\ Number of scanned objects: 0 Number of detections: 0 Time of completion: 1:42:37 PM Total scanning time: 0 sec (00:00:00) I have tried other shared folders (smaller and larger) with read-only permissions or full permissions. I even tried to scan directly a sub-folder of a mapped shared folder (like: H:\Documents) and I got the same result: Log Scan Log Version of detection engine: 19673 (20190712) Date: 12/07/2019 Time: 11:00:41 AM Scanned disks, folders and files: H:\Documents Number of scanned objects: 0 Number of detections: 0 Time of completion: 11:00:41 AM Total scanning time: 0 sec (00:00:00) The scan always completes with zero scanned objects, even though there are plenty of ordinary files in the shared folder. I assume that these drives should be treated as Network drives by NOD32, which is an enabled option in NOD32 Setup. Please note that, other applications in the guest (Windows 10) machine can access the files and sub-folders on the drive(s) mapped to the shared folder(s) and this is not a permission problem. Please also note that, when I select Custom Scan and then go to one of the shared folder's drive, select some files from a (sub)folder, then NOD32 can scan those specific files. The problem is that NOD32 cannot "find" files in selected folders. In other words, NOD32 seems not be able to get the list of files in such "network" drives.
  2. Yes. The problem is with the update. There is no log about the update process. The GUI quickly changes; so, I am not able to see what wrong happens. But, it seems that it tries to download 3 files after the update.ver file and it fails after the first one. I cleared the Update Cache from Setup and retried; but no improvement. I selected enable pre-release updates from Setup; it tried to download a 92 MB worth of data files having names em0??_32_l?.nup. However, it got stuck several times at ~80%. Finally after several retries it was able to update to 19117P (20190331). I deselected enable pre-release updates, cleared the Update Cache from Setup and retried again several times. It tries to update normally, but again it stops and displays the wrong message: Virus signature database has been updated successfully. The virus database does not change: still the Pre-Release database version is displayed. I think there is some problem with the download servers of ESET. I am sure that the problem is not related to my Internet connection (~32mbps download speed), because I do not have any similar problem with my Windows installation.
  3. The modification on the file /etc/apparmor.d/abstractions/base did not work for me. There is a syntax error on the line starting with unix.
  4. What is the recommended solution for AppArmor? BTW, the esets.service is running OK: ● esets.service - ESET NOD32 Antivirus Loaded: loaded (/lib/systemd/system/esets.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-03-31 15:14:21 +03; 4min 3s ago Process: 1260 ExecStart=/opt/eset/esets/sbin/esets_daemon (code=exited, status=0/SUCCESS) Main PID: 2055 (esets_daemon) Tasks: 11 (limit: 4915) Memory: 489.2M CGroup: /system.slice/esets.service ├─2055 /opt/eset/esets/sbin/esets_daemon ├─2056 /opt/eset/esets/sbin/esets_daemon └─2057 /opt/eset/esets/lib/esets_mac Mar 31 15:14:18 xxxx systemd[1]: Starting ESET NOD32 Antivirus... Mar 31 15:14:21 xxxx systemd[1]: Started ESET NOD32 Antivirus. Mar 31 15:14:21 xxxx esets_mac[2057]: error[08090000]: Cannot unblock removable media (org.freedesktop.udisks2.filesystem-mount)
  5. I am in a process of moving from Windows (7) to Linux (Ubuntu 18.10). I have a license for NOD32 Antivirus. Yesterday I installed the ESET NOD32 Antivirus software that I downloaded for ESET web site: eset_nod32av_64bit_en.linux Everything went smoothly and I entered my licenced Username and Password to the new NOD32 installation. However, I noticed that the virus database is out-of-date. Manual or automatic update did not manage to bring the database to the current state. When I try to manually update the virus database, NOD32 first downloads the update.ver file (8KB) and then tries to download the database files (~77MB). However, after ~3-5% of the download process, NOD32 stops and displays the message: Virus signature database has been updated successfully. On the same window I see that the Last successful update is the current time; however, the Version of virus signature database is 13825 (20160719). I have not seen anything important in /var/log/esets directory. Events log contains these: Note that 10:35 is the system's boot time. My /tmp folder's permissions are the normal ones (drwxrwxrwt) and there is no file named esets.sock under /tmp. Product version is More info is attached.
  • Create New...