Jump to content

MartinK

ESET Staff
  • Content Count

    1,522
  • Joined

  • Last visited

  • Days Won

    48

Kudos

  1. Upvote
    MartinK received kudos from Peter Randziak in ESMC 7 Bad file descriptor   
    This is most probably caused by limits set in your Linux system. Please verify limit for open files in your system, or limits for services in case systemd is used.
    In case you are using ESMC Appliance, please check following forum topic:
     
  2. Upvote
    MartinK received kudos from Peter Randziak in ERA 6.5 Server MySQL issue - Windows Server 2016   
    Just to be sure, there are two other settings of MySQL server that has to be changed:
    innodb_log_file_size=100M innodb_log_files_in_group=2 Could you verify those too? They can have different values but there are minimal requirements that are larged than default (documentation).
  3. Upvote
    MartinK received kudos from Peter Randziak in ERA 6.5 Server MySQL issue - Windows Server 2016   
    Just to be sure, there are two other settings of MySQL server that has to be changed:
    innodb_log_file_size=100M innodb_log_files_in_group=2 Could you verify those too? They can have different values but there are minimal requirements that are larged than default (documentation).
  4. Upvote
    MartinK received kudos from MichalJ in two licenses issue   
    I would try to create new report with following data set configuration:

    which should provide you list of devices with public ID of used licenses. It is possible multiple entries per device will be reported in case multiple activated products or multiple licenses are used.
  5. Upvote
    MartinK received kudos from Peter Randziak in ESET SMC Appliance disc full with proxy cache files   
    Indeed it seems that Apache HTTP proxy has taken all of the free space. When configuring appliance and proxy is enabled, service used to cleanup cache regularly should be enabled. It uses htcacheclean utility to clean cache directory. From my point of view it seems this service is not working or your proxy is heavily used and all those ~40GB of cached files were downloaded recently.
    I would recommend to check status of mentioned service:
    service htcacheclean status  
    Any chance you enabled apache HTTP later, i.e. not during initial appliance configuration? It would explain why cleanups are not enabled.
    In order to resolve this issue, easiest would be to clean proxy cache directory. In case it won't help, we will need some trace logs from ESMC services, so that we can check reason why services are not running. It is possible that actually database (MySQL) has to be restarted as it might also stopped working due to insufficient disk space.
  6. Upvote
    MartinK received kudos from bbahes in SMC7: The maximum number of open file descriptors is reached, Agent v7 can't access ESMC   
    Thanks, that means your appliance (VHD) comes from release 7.0.66.0, not latest 7.0.72.0 where we targeted this issue.
    We have decided to resolve this issue by changing default limits for all systemd services, it can be done by commands:
    sed -i "s/.*DefaultLimitNOFILE=.*/DefaultLimitNOFILE=65535 /" /etc/systemd/system.conf sed -i "s/.*DefaultLimitNOFILE=.*/DefaultLimitNOFILE=65535 /" /etc/systemd/user.conf Modification of service file (eraserver.conf) won't "survive" ESMC upgrade and file will be replaced with version bundled in installer.    
  7. Upvote
    MartinK received kudos from bbahes in SMC7: The maximum number of open file descriptors is reached, Agent v7 can't access ESMC   
    Thanks, that means your appliance (VHD) comes from release 7.0.66.0, not latest 7.0.72.0 where we targeted this issue.
    We have decided to resolve this issue by changing default limits for all systemd services, it can be done by commands:
    sed -i "s/.*DefaultLimitNOFILE=.*/DefaultLimitNOFILE=65535 /" /etc/systemd/system.conf sed -i "s/.*DefaultLimitNOFILE=.*/DefaultLimitNOFILE=65535 /" /etc/systemd/user.conf Modification of service file (eraserver.conf) won't "survive" ESMC upgrade and file will be replaced with version bundled in installer.    
  8. Upvote
    MartinK received kudos from Peter Randziak in 7.0.577.0 Agent Upgrade Fails On Hyper-V Guests   
    There should be full-verbosity MSIEXEC installation log with name ra-upgrade-infrastructure.log either in AGENT's Logs directory, or in system temporary directory. It should help us to identify cause of failure of last upgrade attempt.
    From symptoms you describe it is possible that AGENT's service cannot stop and thus upgrade fails - in such case, could you provide us version/type of ESET security product you are using on those clients?
  9. Upvote
    MartinK received kudos from Peter Randziak in ESMC 7 ERA Web Console - How to import 3rd party SSL certificate   
    In appliance, ESMC console is hosted in Apache Tomcat (official CentOS7 package), so you have to modify it's configuration. Configuration file should be located in /etc/tomcat/server.xml. Only known complication is that Apache Tomcat has some special requirements for naming certificate, especially when java keystore file is used.
  10. Upvote
    MartinK received kudos from Peter Randziak in Can't use AD integration   
    Could you please check SERVER's trace.log for "Error:" entries from time that login does not works? When did this started to happen? Are you using "\" delimiter when specifying domain name in login screen or some alternative?
  11. Upvote
    MartinK received kudos from j-gray in All clients are members of all dynamic groups?   
    Unfortunately you are right. Issue has been discovered during ESMC "Early Access" but was not resolved yet. As you noted, it does not respect hierarchy of groups, only results of matching dynamic group templates.
  12. Upvote
    MartinK received kudos from DaveBOpt in ESMC - Agent Outdated   
    It is a client task "Security Management Center Components Upgrade" (see documentation).
  13. Upvote
    MartinK gave kudos to MichalJ in ERA 6.5 to ESMC Components Upgarde Issue   
    ESET Security Management Components Upgrade task is only intended to upgrade agents & other ESMC components. If you want to install a newer version of the endpoint, you need to do it via "software install task". The simplest way, if you already have ESMC V7 would be to navigate to the main dashboard, tab "ESET Applications", locate the table "outdated applications" and click on the individual entries you want to update. You can then click "update installed eset products", and that would automatically create corresponding installation tasks.
  14. Upvote
    MartinK received kudos from 1 079 379 164 in ESMC components upgrade task failed   
    According to provided logs, ESMC server has problem to establish connection to most of ESET services. It is not able to connect to ESET repository, update server, license servers .. could you verify it is properly configured? Maybe there is problem with firewall or proxy configuration?
    Also I would recommend to check AGENT's trace.log -> upgrade of infrastructure is executed by AGENT, so there should be visible also upgrade errors, but my best guess is that AGENT installed on the same machine as ESMC has the same network-related problems.
  15. Upvote
    MartinK received kudos from greyjoy99 in Issues with ERA migration from one server to another   
    I would recommend to follow documentation and troubleshoot AGENT's connectivity. In case policy is correctly applied (this can be verified remotely), it is possible that connection to new server is not possible, and thus AGENT is using previous. This is "fallback" scenario so that you do not loose manageability of AGENT after wrong configuration.
    Without more details it is just guessing, but most probably there will be problems with certificates, where either AGENT rejects certificate of new SERVER, or vice versa.
  16. Upvote
    MartinK received kudos from Timreck in Setting of Proxy Server - which setting has what result   
    Just to clarify, but configuration of AGENT (in ESET Management Agent policy) and configuration of HTTP proxy in policy for security product (i.e. ESET Endpoint Security for Windows) are completely unrelated, and each of them configure only specific product it is targeting.
    Regarding settings, both of policies (Agent vs. other products) are using the same principle: there is possibility to configure one HTTP proxy for all communication (this one is mostly called global), and there is possibility to override this setting for specific services or communication types. In case of ESET Management Agent, you can use different configuration for communication with ESET infrastructure, through internet, and different HTTP proxy (or not at all) for communication between Agent and ERA/ESMC Server.
    This is hard to answer, but it definitely depends on infrastructure. For example there are customers, that has very weak connection between AGENT and ESMC Server (i.e. some kind of VPN between company branches) and installation or download through this link would be killing internal network - also it would mean that ESMC has to be transformed into high-grade HTTP server. There is also alternative to use one HTTP proxy hosted side-by-side ESMC Server which should partially resolve this issue, but it is not enforced.
  17. Upvote
    MartinK gave kudos to TomasP in ERA VA - Missing ODBC driver   
    Hello,
    We have recently learned of an issue that may affect your ERA Appliances. It is caused by an updated MySQL ODBC driver (Linux ODBC Connector package) and will manifest upon ERA service restart.
    You can identify this issue by the "Error loading data" message shown in the console, or by trace.log entries mentioning missing ODBC driver.
    More details, as well as the steps necessary to fix this issue (or prevent it, if you are not affected yet), can be found at https://support.eset.com/kb6760/
    Regards,
    Tomas
×