jordigg
-
Posts
7 -
Joined
-
Last visited
Posts posted by jordigg
-
-
Will give it a try Martin, thanks so much for the tip!
-
Hi there,
We have seen that when ESET real-time protection is used on our workstations, it blocks our build process when this one runs on more than one core.
Our build fails when we run it like:
cmake --build . --target WhatEver -- -j 4
In order to overcome this issue we have two options:
1- Run cmake only on 1 core (using the -j cmake flag)
2- Remove/comment libesets_pac.so from /etc/ld.so.preload
Anyone have encounter it before? What happens when we remove that line from the preload file? Is that disabling the real-time feature?
Cheers,
Jordi
-
Our machines have dualboot, Windows and Linux. We install ESET on both, is there any way to licence only the machine and not each OS? Maybe licence the user that is logged in instead?
-
Is there any way to specify an SSL connection to the database used on the Remote Administrator? We want to allow only SSL connection to our MySQL instance hosted on Google Cloud (GCE) but I can't find the way to specify the certificates to be used on the connection.
MySQL connection with SSL certs uses the following command:
mysql --ssl-ca=server-ca.pem --ssl-cert=client-cert.pem --ssl-key=client-key.pem \
--host=[INSTANCE_IP] --user=root --passwordAny help is appreciated!
-
Fixed by downgrading to Mysql 5.5. GCE forces that flag to be on on latest 5.6 version they run. Not sure if it will become an standard in the future but would be nice to have a workaround.
-
Hi there,
I'm running ESET Remote Administrator on a Gcloud instance and the database uses GCloud SQL. Everything worked for a few weeks but without any kind of changes on our side the remote administrator fails now to show an kind of data.
I can login but I can view any data related to reports, machines, configurations...
Looking at the errors I get:
- Error while generating report on each graph of the dashboard
- CCleanupModule: Failed to process cleanup task request with: [MySQL][ODBC 5.3(w) Driver][mysqld-5.6.29-google-log]When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.
- CCleanupModule: [MySQL][ODBC 5.3(w) Driver][mysqld-5.6.29-google-log]When @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1, the statements CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can be executed in a non-transactional context only, and require that AUTOCOMMIT = 1. These statements are also not allowed in a function or trigger because functions and triggers are also considered to be multi-statement transactions.
On every page load. By default GCloud SQL uses ENFORCE_GTID_CONSISTENCY for replication which prevents the use of, for example, temp tables.
Is there any workaround? I don't think I can disable that "feature" without downgrading to another version of MySQL. I'm sharing that database with another tool and that's why I was trying to don't downgrade. I would prefer to always use the latest stable versions.
Cheers
Error while generating report - MySQL Running on GCE SQL Cloud instance
in ESET PROTECT On-prem (Remote Management)
Posted
Will try to raise a ticket with Google as well to check whether is possible to run v5.6 with ENFORCE_GTID_CONSISTENCY disabled. Thanks for checking by again!