kreeks 0 Posted February 23, 2016 Share Posted February 23, 2016 Hi there We were experiencing the same issue, where the last connected was stopping for all agents. Made the change as mentioned above " add innodb_lock_wait_timeout=600 to your MySQL configuration (/etc/my.cnf) into [mysqld] section" This seemed to have fixed the issue, but now it seems to have only extended the time before the agents again fail to show the updated connection time Anything else we can try? Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 24, 2016 ESET Staff Share Posted February 24, 2016 Hi there We were experiencing the same issue, where the last connected was stopping for all agents. Made the change as mentioned above " add innodb_lock_wait_timeout=600 to your MySQL configuration (/etc/my.cnf) into [mysqld] section" This seemed to have fixed the issue, but now it seems to have only extended the time before the agents again fail to show the updated connection time Anything else we can try? Proper value depends on number of clients you are managing, amount of collected data and overall performance of MySQL database. In case value 600 is not enough, you may increase it (maybe to 3600). Also have you checked whether multi-threading is enabled for your MySQL driver (/etc/odbcinst.ini)? Link to comment Share on other sites More sharing options...
kreeks 0 Posted February 28, 2016 Share Posted February 28, 2016 (edited) thanks for the reply have upped the timeout to 3600, so will keep an eye on it this link (hxxp://help.eset.com/era_install/63/en-US/index.html?odbc_configuration.htm) says my version on MySQL (5.3) supports multithreading but do I need to add this line aswell? Threading = 0 as per above link fyi, we are only dealing with <100 clients Edited February 28, 2016 by kreeks Link to comment Share on other sites More sharing options...
kreeks 0 Posted February 28, 2016 Share Posted February 28, 2016 (edited) but have found this in the trace.log Warning: CDatabaseModule [Thread 7f89e899e700]: Dependability checks of underlaying layer failed with:The underlying unixodbc implementation has not support for multithreading. also contents of odbcinst.ini [PostgreSQL]Description = ODBC for PostgreSQLDriver = /usr/lib/psqlodbc.soSetup = /usr/lib/libodbcpsqlS.soDriver64 = /usr/lib64/psqlodbc.soSetup64 = /usr/lib64/libodbcpsqlS.soFileUsage = 1 [MySQL ODBC 5.3 Unicode Driver]Driver = /usr/lib64/libmyodbc5w.soUsageCount = 1 [MySQL ODBC 5.3 ANSI Driver]Driver = /usr/lib64/libmyodbc5a.soUsageCount = 1 Edited February 28, 2016 by kreeks Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted February 29, 2016 ESET Staff Share Posted February 29, 2016 thanks for the reply have upped the timeout to 3600, so will keep an eye on it this link (hxxp://help.eset.com/era_install/63/en-US/index.html?odbc_configuration.htm) says my version on MySQL (5.3) supports multithreading but do I need to add this line aswell? Threading = 0 as per above link fyi, we are only dealing with <100 clients Yes, you should enable multi-threading. It is not only due to performance, but also for certain functionality that requires it - for example canceling SQL queries that are no longer required. Link to comment Share on other sites More sharing options...
Recommended Posts