Jump to content

Marcos

Administrators
  • Posts

    36,451
  • Joined

  • Last visited

  • Days Won

    1,449

Posts posted by Marcos

  1. Since this is an English forum, we kindly ask you to post in English.

    Please carry on as follows to resolve the issue:

    1. stop the PROTECT Server service

    systemctl stop eraserver
    
    • check if the service has been stopped
    systemctl status eraserver
    

    2. install the MariaDB ODBC driver

    yum install mariadb-connector-odbc
    
    • check if the driver has been correctly installed
      yum list installed | grep mariadb
      mariadb-connector-c.x86_64                3.2.6-1.el9_0                       @appstream
      mariadb-connector-odbc.x86_64             3.1.12-3.el9                        @appstream
      

    3. check the alias of the ODBC driver and search for the following section:

    less /etc/odbcinst.ini
    
    [MariaDB]
    Description=ODBC for MariaDB
    Driver=/usr/lib/libmaodbc.so
    Driver64=/usr/lib64/libmaodbc.so
    FileUsage=1
    
    • verify if such file is present
    ls -la /usr/lib64 | grep -I libmaod*
    
    -rwxr-xr-x.  1 root root    326688 May 25  2022 libmaodbc.so
    

    4. modify the "StartupConfiguration.ini" - replace the "MySQL ODBC 8.3 Unicode Driver" with "MariaDB" so the final configuration file will look like follows:

    vi /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini
    
    DatabaseType=MySqlOdbc
     DatabaseConnectionString=Driver=MariaDB;Server=127.0.0.1;Port=****;User=***;Password={****};CharSet=utf8;NO_LOCALE=1;NO_SSPS=1;Database=era_db;
    

    5. start the PROTECT server service

    systemctl start eraserver
    
  2. 4 minutes ago, AlSky said:

    Why in the result of smart scan do the files hiberfil.sys, pagefile.sys and swapfile.sys continue to be showed at the end, but in the result of deep scan are shown in the middle of it?

    Hard to say, probably smart optimization, the number of CPU cores and the type of scanned files has an effect on that.

    5 minutes ago, AlSky said:

    Why do ESET spend almost three more hours scanning files even if it does not show an increase in the number of scanned files? As you can see in screenshots 5 and 6. 40 minutes and the number of files scanned was the same. So three hours like that, apparently analyzing something without showing an increase in the number of files analyzed. It's never happened to me before something like this. It could stop a few minutes (three, four minutes), but never three hours in which it apparently is scanning something but shows no increase in scanned files.

    Does it happen if you disable also archives and SFX archives?

  3. 1, Regarding scanning of the files in the root of the C drive while scanning the c:\users folder, I assume this is due to multi-thread scanning introduced in v17.1.

    2, As an administrator, many more objects are scanned compared to a scan under a normal user.

    3, "when the number of files it says are scanned just stops, although you can see that it is still scanning files. "
    This is a normal behavior when scanning objects like the registry, WMI or larger archives.

  4. It is only the firewall or network protection that could be involved in network issues from the technical point of view or the network traffic scanner when it comes to http(s), pop3(s) or imap(s). If disabling any of them didn't make any difference and uninstalling ESET did, it could be that simply installation of the WFP driver could interfere with another application's WFP driver or cause some unknown bug in MS WFP to manifest. Please provide logs collected with ESET Log Collector and also raise a support ticket for further investigation.

  5. We are in the process of preparing a KB with instructions how to address login issues caused by PROTECT server restarts under heavy server load:

    1. stop the PROTECT Server service

    systemctl stop eraserver
    
    • check if the service has been stopped
    systemctl status eraserver
    

    2. install the MariaDB ODBC driver

    yum install mariadb-connector-odbc
    
    • check if the driver has been correctly installed
      yum list installed | grep mariadb
      mariadb-connector-c.x86_64                3.2.6-1.el9_0                       @appstream
      mariadb-connector-odbc.x86_64             3.1.12-3.el9                        @appstream
      

    3. check the alias of the ODBC driver and search for the following section:

    less /etc/odbcinst.ini
    
    [MariaDB]
    Description=ODBC for MariaDB
    Driver=/usr/lib/libmaodbc.so
    Driver64=/usr/lib64/libmaodbc.so
    FileUsage=1
    
    • verify if such file is present
    ls -la /usr/lib64 | grep -I libmaod*
    
    -rwxr-xr-x.  1 root root    326688 May 25  2022 libmaodbc.so
    

    4. modify the "StartupConfiguration.ini" - replace the "MySQL ODBC 8.3 Unicode Driver" with "MariaDB" so the final configuration file will look like follows:

    vi /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini
    
    DatabaseType=MySqlOdbc
     DatabaseConnectionString=Driver=MariaDB;Server=127.0.0.1;Port=****;User=***;Password={****};CharSet=utf8;NO_LOCALE=1;NO_SSPS=1;Database=era_db;
    

    5. start the PROTECT server service

    systemctl start eraserver
    
  6. 14 hours ago, lukem said:

    I've enabled informational notifications as the 'file submitted' notification from liveguard is informational and without it and with pre-emptive protection enabled staff don't receive any notification to indicate why they may not be able to execute a file that has been sent to liveguard. I see this 'file submitted' notification as a requirement to run liveguard on any of my client endpoints which means I now have informational notifications enabled but now find I can't disable the scan complete notification, please add the ability to disable the scan complete notification and/or change the notification type of the liveguard 'file submitted' notification.

    Would disabling these desktop notifications accomplish what you are after?

    image.png

×
×
  • Create New...