eraserver not start

[gochoa 0]

Hi

After click upgrade on contextual menu, eraserver service not start.

trace.log

2021-03-04 02:12:27 Information: Kernel [Thread 7f5ab2792740]: Unloading module: CUpdatesModule
2021-03-04 02:12:27 Information: Kernel [Thread 7f5ab2792740]: Unloading module: CTranslatorModule
2021-03-04 02:12:27 Error: Service [Thread 7f5ab2792740]: [MySQL][ODBC 8.0(w) Driver][mysqld-5.6.40]PROCEDURE era_db.usp_static_object_ids_get does not exist (1305)

ra-upgrade-infraestructure.log
 

Initialized log file: /var/log/eset/RemoteAdministrator/EraAgentInstaller.log

ESET Management Agent Installer (version: 8.0.2216.0), Copyright © 1992-2020 ESET, spol. s r.o. - All rights reserved.

Creating directories...
Creating 'install' directory path: /opt/eset/RemoteAdministrator/Agent
Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/Agent
Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/Agent
Creating 'Pki Cache' directory path: /var/opt/eset/RemoteAdministrator/Agent/pki.eset.com/
Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/Agent
Creating 'libs' directory path: /opt/eset/RemoteAdministrator/Agent
Directories created
Cleaning database scripts from path: /opt/eset/RemoteAdministrator/Agent/setup/Database
The archive will be extracted to: /opt/eset/RemoteAdministrator/Agent
Extracting, please wait...
Checking OpenSSL ... done [OpenSSL 1.0.2k-fips 26 Jan 2017]
GUID loaded from config-file with value: 07b42969-fbd9-4de9-8a70-55fa45e3761b
Installed version loaded from config-file is: 7.0.471.0
Checking installed version ...
Status of current installation is: UPGRADE
Reading previous configuration settings
Previous configuration read ('hostname': '127.0.0.1', 'port': 2222)
Using previous connection settings 'hostname': '127.0.0.1', 'port': 2222
Loading correct GUID...
Loading of GUID was successful (new GUID = 07b42969-fbd9-4de9-8a70-55fa45e3761b)
Creating config file: /etc/opt/eset/RemoteAdministrator/Agent/config.cfg ...
Creating 'modules' directory path: /var/opt/eset/RemoteAdministrator/Agent/Modules/
Moving ESET Modules from '/opt/eset/RemoteAdministrator/Agent/setup/Modules' to /var/opt/eset/RemoteAdministrator/Agent/Modules/...
Reading database status...
Database read successfully.
Database status is 'DB_UPGRADEABLE'
Database status is 'DB_UPGRADEABLE'. Database exists and will be upgraded
Upgrading database.
Database upgraded.
Resetting configuration...
Resetting configuration was successful.
Setting connection into config...
Connection set successfully.
Resetting replication interval...
Replication interval reset was successful.
Reset of log filter...
Reset of log filter was successful.
Copying installer to target destination: /opt/eset/RemoteAdministrator/Agent/setup/installer_backup.sh
File ownership set to: root:root
Setting auto-start service...
Installing SELinux policy... done

 

Any idea to fix the problem

[MartinK 378]

From provided logs it is not possible to find out what went wrong, but it seems that upgrade might have been interrupted and thus database schema is currently incomplete.
I would recommend to perform EP server repair using installer, that can be found here:

/opt/eset/RemoteAdministrator/Agent/setup/installer_backup.sh

which might help to restore database, but be aware that after that, another attempt to upgrade will be performed during next service startup, where it might take some time (depending on DB size) and during this time, console won't be accessible.

Also note, that possible upgrade problem might be described in more detail in standard EP trace.log - as you are using MySQL, there were few reports of ailed upgrades with this database type in case there was not enough memory, but it is hard to confirm this -> I would recommend to monitor resources.

[gochoa 0]

Hi MartinK thanks for you reply,

When I was run the script, this is the output

Creating 'install' directory path: /opt/eset/RemoteAdministrator/Agent
Creating 'config' directory path: /etc/opt/eset/RemoteAdministrator/Agent
Creating 'data' directory path: /var/opt/eset/RemoteAdministrator/Agent
Creating 'Pki Cache' directory path: /var/opt/eset/RemoteAdministrator/Agent/pki.eset.com/
Creating 'logs' directory path: /var/log/eset/RemoteAdministrator/Agent
Creating 'libs' directory path: /opt/eset/RemoteAdministrator/Agent
Directories created
Cleaning database scripts from path: /opt/eset/RemoteAdministrator/Agent/setup/Database
The archive will be extracted to: /opt/eset/RemoteAdministrator/Agent
Extracting, please wait...
Checking OpenSSL ... done [OpenSSL 1.0.2k-fips 26 Jan 2017]
GUID loaded from config-file with value: 07b42969-fbd9-4de9-8a70-55fa45e3761b
Installed version loaded from config-file is: 8.0.2216.0
Checking installed version ...
Status of current installation is: REPAIR
Reading previous configuration settings
Previous configuration read ('hostname': '127.0.0.1', 'port': 2222)
Using previous connection settings 'hostname': '127.0.0.1', 'port': 2222
Loading correct GUID...
Loading of GUID was successful (new GUID = 07b42969-fbd9-4de9-8a70-55fa45e3761b)
Creating config file: /etc/opt/eset/RemoteAdministrator/Agent/config.cfg ...
Creating 'modules' directory path: /var/opt/eset/RemoteAdministrator/Agent/Modules/
Moving ESET Modules from '/opt/eset/RemoteAdministrator/Agent/setup/Modules' to /var/opt/eset/RemoteAdministrator/Agent/Modules/...
Reading database status...
Failed reading database.
1203: Error '2' occurred while reading database: Current locale settings are invalid
Cleaning up setup directories

 

Edited March 16, 2021 by gochoa
Code section

[gochoa 0]

Both server and agent trace.log is attached

Server_trace.log Agent_trace.log