Jump to content

Flyer

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Posts posted by Flyer

    Error - Login failed: Connection has failed with state 'Not connected'

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by Flyer

    Hi Martink,

    I think I've solved!  :D

     

    1: shutdown container, edit config file and add this, just because if you run lxc on a systemd it won't auto set systemd for guests (argh!!)

    lxc.autodev = 1
lxc.kmsg = 0

    Reference: Debian Jessie and lxc containers (https://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#issues-lxc-jessie-host)

     

    2: wget serverinstall from eset and run it as root (it shows a initcl error, but systemd starts)

    3: reboot lxc just for check and eraserver service is running.

    4: deploy agent from webconsole (liveinstaller).

    5: run agent installer from CLI - root rights obviously.

    6: reboot and check services: both eraserver and eraagent loaded on boot and it's all fine  :)

     

    Other useful info for people running from containers (i moved to gpo to solve, and got the solution with all agents already installed xD) : by default CIFS mounts are disabled (that in proxmox, but i think in dockers too), so you won't be able to mount admin shares on win clients and deploy agent via era server (/etc/apparmor.d/lxc/ edit apparmor lxc rules and add mount fstype=cifs , reload apparmor)

     

     

     

    I think it should be useful to add it in a KB for everyone running era and webconsole on docker/proxmox/containers: if you get a systemd host that doesn't mean you'll get a systemd guest by default

    Error - Login failed: Connection has failed with state 'Not connected'

    in ESET PROTECT On-prem (Remote Management)

    Posted

     

    Component upgrade from Webconsole failed (check in trace.log of agent)

    2016-02-02 19:28:59 Error: CSystemConnectorModule [Thread 7fcd40ca6700]: ReadUpgradeStatus: Upgrade infrastructure task failed: Error upgrading with installer '/tmp/6ef7-2323-55c2-747a/Server-Linux-x86_64.sh': Command failed (exit code: 1)
2016-02-02 19:40:36 Error: CSystemConnectorModule [Thread 7fccab7fe700]: UpgradeInfrastructure: Error upgrading with installer '/tmp/1b23-2b21-d641-8d84/Server-Linux-x86_64.sh': Command failed (exit code: 1)

    Please note timing, it was 20.40 when i launched the task (i think it's just utc time)

     

    I'll try by CLI and let you know

     

    ERA + webconsole is running on lxc container over proxmox, but it was all working till yesterday

     

    Now I am almost sure it is problem with upstart which was introduced in 6.3. There containers (lxc, docker) are not able to handle upstart or systemd services properly, they are either completely mocked or requires advanced configuration to work properly.

     

    ERA installers are detecting upstart by searching for command "initctl" -> once found, fully operational upstart is expected. In case you will be able to confirm that it is problem with upstart service initialization, only solution we were able to come with is to fool upstart detection by temporarily renaming/removing initctl command => in case it is not found during installation, fallback SysV-init scripts for daemon startup will be used.

    Btw. ERA AGENT installed in this container should be having exactly the same problems ... is it upgraded to 6.3? Is it actually running/connecting to SERVER?

     

     

    Got it, you're right :

    ESET Remote Administrator Server Installer (version: 6.3.148.0), Copyright © 1992-2016 ESET, spol. s r.o. - All rights reserved.

Cleaning database scripts from path: /opt/eset/RemoteAdministrator/Server/setup/Database
Extracting archive, please wait...
Archive extracted to /tmp/tmp.ffOT92m0Tc.
Checking OpenSSL ... done [OpenSSL 1.0.1k 8 Jan 2015]
Reading previous installation settings ... done
Checking installed version... done
Status of current installation is: REPAIR
Checking database connection ... done
Loading GUID ... done [GUID = 5920bbb2-4c07-4251-b2f7-42621b1b0b1e]
Moving ESET Modules from '/tmp/tmp.ffOT92m0Tc/setup/Modules' to /var/opt/eset/RemoteAdministrator/Server/Modules/... done
Moving scripts from '/tmp/tmp.ffOT92m0Tc/setup/Scripts' to /var/opt/eset/RemoteAdministrator/Server/Scripts/... done
Skipping certificates generation.
Skipping static groups synchronization scheduling.
Stopping service... ./Server-Linux-x86_64.sh: 1512: ./Server-Linux-x86_64.sh: initctl: not found
Preparing database upgrade ... done
Upgrading database ... done
Storing ports into configuration ... done
Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/Server
Creating 'libs' directory path: /opt/eset/RemoteAdministrator/Server
Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/Server
Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/Server
Moving LangData.dat to /var/opt/eset/RemoteAdministrator/Server/Localization/LangData.dat... done
Extracting ReportPrinter files... done
Creating startup configuration file /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini ... done
Creating config file /etc/opt/eset/RemoteAdministrator/Server/config.cfg ... done
Backing up contents of /opt/eset/RemoteAdministrator/Server
Copying files to target destination: /opt/eset/RemoteAdministrator/Server
File ownership set to: root:root
Setting auto-start service...
Failed to get D-Bus connection: Unknown error -1

    It's all about initctl & systemd (although systemd is installed with all its packages), so I have a "perfect" running era server + era agent but without service on boot

     

    So how to do? (worst solution: destroy lxc container & mv to old style VM, but i'll have to migrate prefs, certificates just to avoid redeploy of agents, configuretion, etc)

    Error - Login failed: Connection has failed with state 'Not connected'

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Component upgrade from Webconsole failed (check in trace.log of agent)

    2016-02-02 19:28:59 Error: CSystemConnectorModule [Thread 7fcd40ca6700]: ReadUpgradeStatus: Upgrade infrastructure task failed: Error upgrading with installer '/tmp/6ef7-2323-55c2-747a/Server-Linux-x86_64.sh': Command failed (exit code: 1)
2016-02-02 19:40:36 Error: CSystemConnectorModule [Thread 7fccab7fe700]: UpgradeInfrastructure: Error upgrading with installer '/tmp/1b23-2b21-d641-8d84/Server-Linux-x86_64.sh': Command failed (exit code: 1)

    Please note timing, it was 20.40 when i launched the task (i think it's just utc time)

     

    I'll try by CLI and let you know

     

    ERA + webconsole is running on lxc container over proxmox, but it was all working till yesterday

    Error - Login failed: Connection has failed with state 'Not connected'

    in ESET PROTECT On-prem (Remote Management)

    Posted

    From EraServerInstaller.log - It seems ok, but no server service from 2016-02-01 13.07 - I've just done a reboot and still get "Login failed not connected"

     

    I can just manually start Era server from /opt/eset/RemoteAdministrator/Server/setup/eraserver start/restart and so i can log into webconsole

    The same was for the agent, so i manually started from /opt/eset/RemoteAdministrator/Agent/setup/eraagent start/restart

    Now I'll try a Remote Administrator Components Upgrade - hope it'll fix all services on boot problems

     

    Other suggestions?

     

     

     

    EraServerInstaller.log

    2016-02-01 13:16:49 Information: Installer: Installed version loaded from config-file is: 6.3.148.0
2016-02-01 13:16:49 Information: Installer: Installed locale loaded from config-file is: en_US
2016-02-01 13:16:49 Information: Installer: Checking installed version...
2016-02-01 13:16:49 Information: CheckVersion: Action invoked with:  --current-version 6.3.148.0 --installed-version 6.3.148.0
2016-02-01 13:16:49 Information: CheckVersion: Set output property: P_VERSION_STATUS = REPAIR
2016-02-01 13:16:49 Information: CheckVersion: Return code: 0
2016-02-01 13:16:49 Information: Installer: Checking of installed version was successful
2016-02-01 13:16:49 Information: Installer: Status of current installation is: REPAIR
2016-02-01 13:16:49 Information: Installer: Checking database connection ...
2016-02-01 13:16:49 Information: DbCheckConnection: Action invoked with:  --db-admin-password ********** --db-admin-username ********** --db-connectors-dir /tmp/tmp.TCSC3kzAwl/setup --db-driver MySQL --db-hostname 127.0.0.1 --db-name era_db --db-port 3306 --db-scripts-dir /tmp/tmp.TCSC3kzAwl/setup/Database --db-type MySQL Server --db-user-password ********** --db-user-username ********** --installed REPAIR --modules-dir /var/opt/eset/RemoteAdministrator/Server/Modules/ --product-name Server --silent-reinstall 1 --upgrade ""
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_CONNECTION_STATUS =
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_STATUS =
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_UPGRADE =
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_USE_FIRST_USER =
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_PORT = 3306
2016-02-01 13:16:49 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;'
.........
.........
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_STATUS = DB_UPGRADEABLE
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_UPGRADE = 1
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_USE_FIRST_USER = 1
2016-02-01 13:16:49 Information: DatabaseReader: Recycling current DB connection.
2016-02-01 13:16:49 Information: DbCheckConnection: Set output property: P_DB_CONNECTION_STATUS = OK
2016-02-01 13:16:49 Information: DbCheckConnection: Return code: 0
2016-02-01 13:16:49 Information: Installer: Connections working.
2016-02-01 13:16:50 Information: Installer: Loading GUID ...
2016-02-01 13:16:50 Information: LoadCorrectProductGuid: Action invoked with:  --db-admin-password ********** --db-admin-username ********** --db-connectors-dir /tmp/tmp.TCSC3kzAwl/setup --db-driver MySQL --db-hostname 127.0.0.1 --db-name era_db --db-port 3306 --db-type MySQL Server --db-user-password ********** --db-user-username ********** --product-guid 5920bbb2-4c07-4251-b2f7-42621b1b0b1e --product-name Server
2016-02-01 13:16:50 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;'
2016-02-01 13:16:50 Information: GetProductGuid: Loading GUID from the database...
2016-02-01 13:16:50 Information: GetProductGuid: Final choice of GUID is: 5920bbb2-4c07-4251-b2f7-42621b1b0b1e
2016-02-01 13:16:50 Information: LoadCorrectProductGuid: Set output property: P_PRODUCT_GUID = 5920bbb2-4c07-4251-b2f7-42621b1b0b1e
2016-02-01 13:16:50 Information: LoadCorrectProductGuid: Return code: 0
2016-02-01 13:16:50 Information: Installer: GUID loaded.
2016-02-01 13:16:50 Information: Installer: Creating 'modules' directory path: /var/opt/eset/RemoteAdministrator/Server/Modules/
2016-02-01 13:16:50 Information: Installer: Moving ESET Modules from '/tmp/tmp.TCSC3kzAwl/setup/Modules' to /var/opt/eset/RemoteAdministrator/Server/Modules/...
2016-02-01 13:16:50 Information: Installer: Modules directory moved succesfully
2016-02-01 13:16:50 Information: Installer: Moving scripts from '/tmp/tmp.TCSC3kzAwl/setup/Scripts' to /var/opt/eset/RemoteAdministrator/Server/Scripts/...
2016-02-01 13:16:50 Information: Installer: Scripts directory moved succesfully
2016-02-01 13:16:50 Information: Installer: Skipping certificates generation.
2016-02-01 13:16:50 Information: Installer: Skipping static groups synchronization scheduling.
2016-02-01 13:16:50 Information: Installer: Stopping service
2016-02-01 13:16:50 Information: Installer: Stopping running instance of /etc/init.d/eraserver
2016-02-01 13:16:59 Information: Installer: Preparing database upgrade.
2016-02-01 13:16:59 Information: DbPrepareUpgrade: Action invoked with:  --db-admin-password ********** --db-admin-username ********** --db-connectors-dir /tmp/tmp.TCSC3kzAwl/setup --db-driver MySQL --db-hostname 127.0.0.1 --db-name era_db --db-port 3306 --db-scripts-dir /tmp/tmp.TCSC3kzAwl/setup/Database --db-type MySQL Server --db-user-password ********** --db-user-username **********
2016-02-01 13:16:59 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;'
2016-02-01 13:16:59 Information: Entering function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ExecuteScriptsInDirectory(const string&, const string&)
2016-02-01 13:16:59 Information: ExecuteScriptsInDirectory: Processing file /tmp/tmp.TCSC3kzAwl/setup/Database/MySQL/SetupScripts/1_prepare_setup.sql
2016-02-01 13:16:59 Information: Leaving function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ExecuteScriptsInDirectory(const string&, const string&)
2016-02-01 13:16:59 Information: DbPrepareUpgrade: Return code: 0
2016-02-01 13:16:59 Information: Installer: Database upgrade prepared.
2016-02-01 13:16:59 Information: Installer: Upgrading database.
2016-02-01 13:16:59 Information: DbUpgrade: Action invoked with:  --db-connectors-dir /tmp/tmp.TCSC3kzAwl/setup --db-driver MySQL --db-hostname 127.0.0.1 --db-name era_db --db-port 3306 --db-scripts-dir /tmp/tmp.TCSC3kzAwl/setup/Database --db-type MySQL Server --db-user-password ********** --db-user-username ********** --locale en_US --product-guid 5920bbb2-4c07-4251-b2f7-42621b1b0b1e --product-name Server --silent-reinstall 1
2016-02-01 13:16:59 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;'
2016-02-01 13:16:59 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;'
2016-02-01 13:16:59 Information: GetProductGuid: Loading GUID from the database...
2016-02-01 13:16:59 Information: GetProductGuid: Final choice of GUID is: 5920bbb2-4c07-4251-b2f7-42621b1b0b1e
2016-02-01 13:16:59 Information: Entering function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::UpgradeDatabase(const string&, const string&, const string&, const string&)
2016-02-01 13:16:59 Information: Leaving function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::UpgradeDatabase(const string&, const string&, const string&, const string&)
2016-02-01 13:16:59 Information: Entering function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ImportProductIdentityForDBServer(const string&, const string&, const string&, uint64_t)
2016-02-01 13:16:59 Information: Leaving function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ImportProductIdentityForDBServer(const string&, const string&, const string&, uint64_t)
2016-02-01 13:16:59 Information: Entering function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::StoreStaticObjectPresets(const string&, const string&, bool)
2016-02-01 13:16:59 Information: Leaving function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::StoreStaticObjectPresets(const string&, const string&, bool)
2016-02-01 13:16:59 Information: Entering function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ExecuteScriptsInDirectory(const string&, const string&)
2016-02-01 13:16:59 Information: ExecuteScriptsInDirectory: Processing file /tmp/tmp.TCSC3kzAwl/setup/Database/MySQL/SetupScripts/1_prepare_setup.sql
2016-02-01 13:16:59 Information: Leaving function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ExecuteScriptsInDirectory(const string&, const string&)
2016-02-01 13:16:59 Information: Entering function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ExecuteScriptsInDirectory(const string&, const string&)
2016-02-01 13:16:59 Information: ExecuteScriptsInDirectory: Processing file /tmp/tmp.TCSC3kzAwl/setup/Database/MySQL/SetupScripts/Upgrade/2_do_upgrade.sql
2016-02-01 13:16:59 Information: StoreStaticObjectPresets: Initializing with locale 'en_US'
..........
..........

2016-02-01 13:17:03 Information: ExecuteScriptsInDirectory: Processing file /tmp/tmp.TCSC3kzAwl/setup/Database/MySQL/SetupScripts/Upgrade/3_clean_upgrade.sql
2016-02-01 13:17:03 Information: Leaving function: void Era::Setup::Common::CustomActions::CDatabaseWrapper::ExecuteScriptsInDirectory(const string&, const string&)
2016-02-01 13:17:03 Information: DbUpgrade: Return code: 0
2016-02-01 13:17:03 Information: Installer: Database upgraded.
2016-02-01 13:17:03 Information: Installer: Storing ports into configuration.
2016-02-01 13:17:03 Information: ConfigInsertPorts: Action invoked with:  --console-port 2223 --db-connectors-dir /tmp/tmp.TCSC3kzAwl/setup --db-driver MySQL --db-hostname 127.0.0.1 --db-name era_db --db-port 3306 --db-type MySQL Server --db-user-password ********** --db-user-username ********** --modules-dir /var/opt/eset/RemoteAdministrator/Server/Modules/ --product-name Server --server-port 2222
2016-02-01 13:17:03 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;'
2016-02-01 13:17:03 Information: Entering function: std::string Era::Setup::Common::CustomActions::CDatabaseReader::GetConfigEngineData(const string&)
2016-02-01 13:17:03 Information: Leaving function: std::string Era::Setup::Common::CustomActions::CDatabaseReader::GetConfigEngineData(const string&)
2016-02-01 13:17:03 Information: ConfigInsertPorts: Return code: 0
2016-02-01 13:17:03 Information: Installer: Ports stored.
2016-02-01 13:17:03 Information: Installer: Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/Server
2016-02-01 13:17:03 Information: Installer: Creating 'libs' directory path: /opt/eset/RemoteAdministrator/Server
2016-02-01 13:17:03 Information: Installer: Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/Server
2016-02-01 13:17:03 Information: Installer: Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/Server
2016-02-01 13:17:03 Information: Installer: Moving LangData.dat to /var/opt/eset/RemoteAdministrator/Server/Localization/LangData.dat...
2016-02-01 13:17:03 Information: Installer: Extracted reportprinter.tar.gz to /var/opt/eset/RemoteAdministrator/Server
2016-02-01 13:17:03 Information: Installer: Creating startup configuration file /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini ...
2016-02-01 13:17:03 Information: CreateStartupConfig: Action invoked with:  --db-driver MySQL --db-hostname 127.0.0.1 --db-name era_db --db-port 3306 --db-type MySQL Server --db-user-password ********** --db-user-username ********** --startup-config-path /etc/opt/eset/RemoteAdministrator/Server/StartupConfiguration.ini
2016-02-01 13:17:03 Information: GetDatabaseServerConnectionStringWithoutEscape: Created connection string: 'Driver=MySQL;Server=127.0.0.1;Port=3306;User=******;Password={******};CharSet=utf8;'
2016-02-01 13:17:03 Information: CreateStartupConfig: Return code: 0
2016-02-01 13:17:03 Information: Installer: Created startup configuration.
2016-02-01 13:17:03 Information: Installer: Created config file /etc/opt/eset/RemoteAdministrator/Server/config.cfg
2016-02-01 13:17:03 Information: Installer: Backing up contents of /opt/eset/RemoteAdministrator/Server
2016-02-01 13:17:03 Information: Installer: Copying files to target destination: /opt/eset/RemoteAdministrator/Server
2016-02-01 13:17:03 Information: Installer: File ownership set to: root:root
2016-02-01 13:17:03 Information: Installer: Setting auto-start service.

    Error - Login failed: Connection has failed with state 'Not connected'

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hello,

     

    about unexpected upgrade, we are definitely not doing it automatically, so there must be somewhere "Remote Administrator components upgrade" task created (or maybe removed in the meantime). Please search Reports->Audit log for creating of this task type. There is also chance it was actually not upgrade, but only "repair". Once you run this task on AGENT that is managing SERVER (=installed on the same system), it will automatically upgrade/repair also SERVER and other ERA components is available.

     

    About second problem with muting: please got to about page in Webconsole and check versions of SERVER and Webconsole = they must be from the same release (i.e. both starting 6.3.), this may be reason for this issue.

     

    Muting: ERA and webconsole are all 6.3.x (managed upgrade from 6.2.x via webconsole components upgrade asa eset released new versions, it was all fine without using CLI)

     

    The only strange data in audit log is about UPDATE MODULES

     

    It seems a task performed by system (system user - system - native user yes) and get always failed!!

    Error - Login failed: Connection has failed with state 'Not connected'

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by Flyer 

    
2016-02-01 13:17:04 Error: CSystemConnectorModule [Thread 7f99edffb700]: UpgradeInfrastructure: Error upgrading with installer '/tmp/6ef7-2323-55c2-747a/Server-Linux$

    <--- ?!?!? Never asked for server upgrade ?!?!?

    2016-02-01 13:18:02 Error: CReplicationModule [Thread 7f99ef7fe700]: CReplicationManager: Replication (network) connection to 'host: "192.168.11.6" port: 2222' faile$

    Probably solved or at least got services running:

    after that upgrade (but i never asked for server upgrades!!!) all services went down, messing up mysql too.

    Just forced eset service manually (/opt/eset/RemoteAdministrator/Server/setup/eraserver) and i can log to webconsole

     

    I've not tryed to reboot yet

     

     

    Please note this, although i don't know if it matter with the server "auto upgrade and next crash":  i was trying to mark as resolved some quarantine and got "Failed to (un)mute some threats" from webconsole and this fro era server trace.log

    2016-02-01 11:32:30 Error: CDataMinersModule [Thread 7f3425fdb700]: Unknown product for mute
2016-02-01 11:32:30 Error: ConsoleApiModule [Thread 7f34297e2700]: 15758 Error while muting threat log: Unknown product for mute
2016-02-01 11:32:30 Error: ConsoleApiModule [Thread 7f34297e2700]: Untranslatable CInterModuleException: Unknown product for mute
2016-02-01 11:32:35 Error: CDataMinersModule [Thread 7f3425fdb700]: Unknown product for mute
2016-02-01 11:32:35 Error: ConsoleApiModule [Thread 7f34297e2700]: 15758 Error while muting threat log: Unknown product for mute
2016-02-01 11:32:35 Error: ConsoleApiModule [Thread 7f34297e2700]: Untranslatable CInterModuleException: Unknown product for mute
2016-02-01 12:32:33 Warning: NetworkModule [Thread 7f34f67fc700]: The connection will be closed due to timeout. SessionId:17845 Ip address: 192.16$
2016-02-01 13:14:16 Error: CDataMinersModule [Thread 7f3425fdb700]: Unknown product for mute
2016-02-01 13:14:16 Error: ConsoleApiModule [Thread 7f3426fdd700]: 18749 Error while muting threat log: Unknown product for mute
2016-02-01 13:14:16 Error: ConsoleApiModule [Thread 7f3426fdd700]: Untranslatable CInterModuleException: Unknown product for mute
2016-02-01 13:14:19 Error: CDataMinersModule [Thread 7f3425fdb700]: Unknown product for mute
2016-02-01 13:14:19 Error: ConsoleApiModule [Thread 7f3426fdd700]: 18749 Error while muting threat log: Unknown product for mute
2016-02-01 13:14:19 Error: ConsoleApiModule [Thread 7f3426fdd700]: Untranslatable CInterModuleException: Unknown product for mute
2016-02-01 13:14:23 Error: CDataMinersModule [Thread 7f3425fdb700]: Unknown product for mute
2016-02-01 13:14:23 Error: ConsoleApiModule [Thread 7f3426fdd700]: 18749 Error while muting threat log: Unknown product for mute
2016-02-01 13:14:23 Error: ConsoleApiModule [Thread 7f3426fdd700]: Untranslatable CInterModuleException: Unknown product for mute

    Mirko

    Error - Login failed: Connection has failed with state 'Not connected'

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by Flyer

    Hi all,

    I've already read about problems with mysql db, etc, etc. but i don't find a way to solve.

    It was all good today, but something got wrong after a scan task on 27 clients.

     

    ODBC should be ok ( hxxp://help.eset.com/era_install/63/en-US/index.html?odbc_configuration.htm- done it and got "odbcinst: Driver installed. Usage count increased to 2" ), nothing has been changed, except for mysql update on debian (done just 1 hour ago)

     

     

    latest server trace.log:

    2016-02-01 13:16:57 Information: AutomationModule [Thread 7f3520282740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-$
2016-02-01 13:16:57 Information: AutomationModule [Thread 7f3520282740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-$
2016-02-01 13:16:57 Information: AutomationModule [Thread 7f3520282740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-$
2016-02-01 13:16:57 Information: AutomationModule [Thread 7f3520282740]: Facade: All triggers have been unloaded.
2016-02-01 13:16:57 Error: Service [Thread 7f3520282740]: Kernel shut down forcefully

    latest agent on server log:

    2016-01-29 20:10:02 Error: CReplicationModule [Thread 7f99ef7fe700]: CReplicationManager: Failed to start replication, replication link '00000000-0000-0000-7007-0000$
2016-02-01 13:00:13 Warning: CSystemConnectorModule [Thread 7f9a167fc700]: CUnixRestartAgentTask: Execution postponed
2016-02-01 13:15:37 Warning: CSystemConnectorModule [Thread 7f9a167fc700]: CUnixRestartAgentTask: Execution postponed
2016-02-01 13:17:02 Error: CReplicationModule [Thread 7f99ef7fe700]: CReplicationManager: Replication (network) connection to 'host: "192.168.11.6" port: 2222' faile$
2016-02-01 13:17:04 Error: CSystemConnectorModule [Thread 7f99edffb700]: UpgradeInfrastructure: Error upgrading with installer '/tmp/6ef7-2323-55c2-747a/Server-Linux$

    <--- ?!?!? Never asked for server upgrade ?!?!?

    2016-02-01 13:18:02 Error: CReplicationModule [Thread 7f99ef7fe700]: CReplicationManager: Replication (network) connection to 'host: "192.168.11.6" port: 2222' faile$

    - this evening -

    2016-02-01 23:22:21 Information: Kernel [Thread 7f9a71c0b740]: Unloading module: CSymbolsModule
2016-02-01 23:22:21 Information: Kernel [Thread 7f9a71c0b740]: Unloading module: CUpdatesModule
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-7006-000000000001, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-7006-000000000002, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-7006-000000000005, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-7006-00000000000a, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-7006-00000000000b, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-7006-00000000000c, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=00000000-0000-0000-7006-00000000000e, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=20f8f346-2f82-4dc9-886a-424ada3a8cba, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: Trigger has been unloaded [SHUTDOWN=1, UUID=277ca5b3-c5e4-42d0-8960-8b4c15ad6d46, TY$
2016-02-01 23:22:21 Information: AutomationModule [Thread 7f9a71c0b740]: Facade: All triggers have been unloaded.
2016-02-01 23:22:21 Information: Service [Thread 7f9a71c0b740]: Kernel shut down nicely

    Info : server time this evening was wrong (1 hour less), but it was right this morning.

     

    M.

    ERA Agent installation

    in ESET PROTECT On-prem (Remote Management)

    Posted

     

     

    Hi, 

     

    I'm using ESET Virtual Appliance 6.3 and I've successfully configured it.

     

    Now I have to install Agent in Linux system using Live installer.

     

    I have shared a folder on windows system which contains Agent installation file (Windows file path: \\servername\eset\Agent-Linux-x86_64.sh), but I am unable to understand what would be the link to be entered in installer file (EraAgentInstaller.sh) to get & install the Agent installer file over the LAN.

     

    For Windows agent installer I have edited path from ESET repository to file://\\servername\eset\agent_x64.msi and it works fine.

     

    So kindly suggest how to install Agent in Linux using Agent live installer.

     

    Simply download .sh to you machine, login and run it from shell

     

    Mirko

     

    Thanks for you reply...

     

    If I do as you said then the agent file will be downloaded from the ESET repository and it will consume internet bandwidth to install in each and every client workstation which I don't want.

     

    As I said earlier that I have shared Agent installer file in my network on windows PC and I want to replace the path from repository.eset.com to my shared network path in EraAgentInstaller.sh file.

     

     

    Ok, sorry for that, looking to EraAgentInstaller.sh it uses WGET to download from repository, so you have to deploy it over http.

    You should download agent from eset and copy to tomcat ERA webconsole dir - under debian is /var/lib/tomcatX/webapps/era, so doing you'll have to change from hxxp://repository.eset.com/blablablato hxxp://IP_OR_HOSTNAME_OF_YOUR_ERASERVER_WEBCONSOLE/agentscript

     

     

    Mirko

    ERA Agent installation

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hi, 

     

    I'm using ESET Virtual Appliance 6.3 and I've successfully configured it.

     

    Now I have to install Agent in Linux system using Live installer.

     

    I have shared a folder on windows system which contains Agent installation file (Windows file path: \\servername\eset\Agent-Linux-x86_64.sh), but I am unable to understand what would be the link to be entered in installer file (EraAgentInstaller.sh) to get & install the Agent installer file over the LAN.

     

    For Windows agent installer I have edited path from ESET repository to file://\\servername\eset\agent_x64.msi and it works fine.

     

    So kindly suggest how to install Agent in Linux using Agent live installer.

     

    Simply download .sh to you machine, login and run it from shell

     

    Mirko

    Dynamic group for Eset EndPoint outdated products

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by Flyer

    So no answer?!?  :blink:

     

    Ok, i've manually done it (take a look to the images - computers and dynamic groups template), but it'd be useful to get software version not equal to "latest" than changing it for every new ESET new version release.

     

    With Era Web Console you've already got this info (look at the dashboard for eset products), so it should be simple to implement.

     

    Don't you agree??  :)

     

    Mirko

    post-10610-0-99094200-1453810638_thumb.jpg

    post-10610-0-83840200-1453810639_thumb.jpg

    Dynamic group for Eset EndPoint outdated products

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hi all,

    I've just managed to upgrade ERA Server and agent on linux server to the latest 6.x version by a client task (Debian server has got his agent, so i could update all via web console), but i'm not able to manage lan clients outdated products.

     

    I'd like to create a dynamic group like that one from the dashboard (Eset applications - Outdated products) and attach it a trigger (something link "when you get computer with product outdated install new version of eset agent and eset enpoint antivirus), but if i check for dynamic groups I can only create a trigger looking for a specific version: this mean that every time Eset release a new version of endpoint products I'd have to manually change version if statment.

     

    Any suggestion or proposal for ERA dynamic group to behave link dashboard outdated products report?? (go and check online for the latest available version, if greater that one installed, do updates)

     

    Attached to this:

    dashboard screenshot showing outdated products

    dynamic groups screenshot, not showing outdated products in "problematic computers"

     

     

    BR

    Mirko

     

    post-10610-0-69914900-1453551811_thumb.jpg

    post-10610-0-62160400-1453551895_thumb.jpg

×
×
  • Create New...