Jump to content

vadim

Members
  • Posts

    31
  • Joined

  • Last visited

Posts posted by vadim

  1. As of now, this is not possible as there is integrated validation for e-mail address format in both Endpoint 6 & ERA 6 policy editor. Statement that it was working in Endpoint 5 is correct, but was never officially supported. We will however track the improvement, and would work on changing the behavior of e-mail notifications for ESET Endpoint Antivirus 6 in the future releases.

     

    Ok, thanks for the info.

  2. I have two email addresses separated by semicolon here:

    policy "ESET Security Product for Windows" --> Tools --> Email notifications --> Recipient address --> "mail1@contoso.com;mail2@contoso.com"

    This policy was created in previous version of ERA.

    After updating to 6.3 I want to edit another element (e.g. "Minimum verbosity") of the policy and cannot save because there is an error "Invalid value" at "Recipient address" field. Single email is ok, no error.

    How can I use more than one email for notifications?

     

    post-6794-0-97758800-1455091433_thumb.png

  3. For those with this problem, could you please add innodb_lock_wait_timeout=600 to your MySQL configuration (/etc/my.cnf) into [mysqld] section and restart database server?

     

    We think it is caused by database cleanups that are executed at midnight of local time and also just after startup in case SERVER was not running during midnight. Could you all confirm this?

    This midnight passed without errors. Increasing lock wait timeout helps. Thanks a lot.

  4.  

    MartinK,

    It turns out my problem is not fixed too :(

    Last status update is "Jan 26 20:59:51" (UTC) and I have the same MySQL error:

    2016-01-26 21:00:59 Error: CDataMinersModule [Thread 7f7b7d1f4700]: CClientsDataMiner2: Failed with: [MySQL][ODBC 5.3(w) Driver][mysqld-5.6.28]Lock wait timeout exceeded; try restarting transaction (1205)

     

    Today I have the same error in the same time:

    2016-01-27 21:01:04 Error: CDataMinersModule [Thread 7f4a427e3700]: CClientsDataMiner2: Failed with: [MySQL][ODBC 5.3(w) Driver][mysqld-5.6.28]Lock wait timeout exceeded; try restarting transaction (1205)

    ERA logs time in UTC(+0) and my local time is UTC+3, so maybe the error occurs every local midnight.

  5. Please attach content of /etc/odbcinst.ini to be sure it is correctly configured.

    [PostgreSQL]
    Description        = ODBC for PostgreSQL
    Driver        = /usr/lib/psqlodbc.so
    Setup        = /usr/lib/libodbcpsqlS.so
    Driver64        = /usr/lib64/psqlodbc.so
    Setup64        = /usr/lib64/libodbcpsqlS.so
    FileUsage        = 1
    UsageCount        = 2
    
    [MySQL ODBC 5.3 Unicode Driver]
    Driver        = /usr/lib64/libmyodbc5w.so
    UsageCount        = 2
    Threading        = 0
    
    [MySQL ODBC 5.3 ANSI Driver]
    Driver        = /usr/lib64/libmyodbc5a.so
    UsageCount        = 2
    Threading        = 0
    
    
  6. There is no 'Threading' parameter (see below). I'll try to add and update.

    [PostgreSQL]
    Description        = ODBC for PostgreSQL
    Driver        = /usr/lib/psqlodbc.so
    Setup        = /usr/lib/libodbcpsqlS.so
    Driver64        = /usr/lib64/psqlodbc.so
    Setup64        = /usr/lib64/libodbcpsqlS.so
    FileUsage        = 1
    
    [MySQL ODBC 5.3 Unicode Driver]
    Driver        = /usr/lib64/libmyodbc5w.so
    UsageCount        = 1
    
    [MySQL ODBC 5.3 ANSI Driver]
    Driver        = /usr/lib64/libmyodbc5a.so
    UsageCount        = 1
    

    We are using MySQL (supplied with virtual appliance).

  7. My "last connected" statuses are not updating too. After restarting ERA server they are updating some time, but then stop updating again.

    And at about the same time server trace log (/var/log/eset/RemoteAdministrator/Server/trace.log) states:

    2016-01-26 10:40:06 Error: CDataMinersModule [Thread 7fec577eb700]: CClientsDataMiner2: Failed with: [MySQL][ODBC 5.3(w) Driver][mysqld-5.6.28]Lock wait timeout exceeded; try restarting transaction (1205)

    It seems to be a database issue.

  8. Ok, one more try.

    Another strange issue with 'administrator privileges'.

    I'm installing / upgrading Eset Endpoint Security from ERA Server (client task). Some executions ends successfully, but another ones ends with error. From 'software-install.log':

    Error 1921. Service 'ESET Service' (ekrn) could not be stopped. Verify that you have sufficient privileges to stop system services.

    Why some agents can stop service and another agents can not?

  9. Hello,

    First I would check what the log says - does the Agent run with admin rights?

    Also, are there any errors or warnings in C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html ?

    Is the issue present on all Agents, or just on some of them? What OS do they run on?

     

    OS: Win7 SP1

    status.html states that everything is "OK".

    The issue is present on every agent I have checked. I have not checked all of them )

    Agent's service runs under 'Local system' account by default. No manual settings was made, just installed agent automatically. How can I check its admin rights?

  10. ERA 6 agents have the following in their logs:

    2015-10-14 09:30:57 Error: CEssConnectorModule [Thread cf0]: Set policy failed: CNodcommChannel: Send request failed with 14, Command failed - Make sure that Agent runs with Administrator privileges.

    What is it?

     

    ESET Remote Administrator Server 6.2.200.0
    ESET Endpoint Security 6.2.2021.2
    ESET Remote Administrator Agent 6.2.190.0
     

×
×
  • Create New...