mhorbul 0 Posted November 7, 2019 Share Posted November 7, 2019 I have created a "Remote Components Upgrade" task as described here The agent on the target host gets updated, but the server upgrade has failed. I have found the following error in the /var/log/eset/RemoteAdministrator/EraServerInstaller.log 2019-11-07 21:54:21 Error: It is not possible to deploy the database, status of the database is: DB_INVALID 2019-11-07 21:54:21 Information: DbCheckConnection: Set output property: P_DB_CONNECTION_STATUS = 77701 2019-11-07 21:54:21 Information: DbCheckConnection: Return code: 0 2019-11-07 21:54:21 Information: Installer: The specified database was not used for this purpose before or it is corrupted. 2019-11-07 21:54:21 Information: Installer: Error: The specified database was not used for this purpose before or it is corrupted. I have tried to remove database (backed it up previously), then upgrade process creates the empty database but also fails with another message Error: Cannot upgrade, database 'era_db' is missing Any idea how to fix this problem? Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted November 11, 2019 ESET Staff Share Posted November 11, 2019 Hello @mhorbul What was the DB in use before the upgrade? It might be related to the usage of MariaDB, or other unsupported DB type. Only MySQL DB is supported on Linux. Link to comment Share on other sites More sharing options...
mhorbul 0 Posted November 11, 2019 Author Share Posted November 11, 2019 We are using Percona MySQL Server. I have upgraded it by tracing down each error manually and applying necessary .sql files. I upgrade so far ESET to 7.x and it works fine. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted November 12, 2019 ESET Staff Share Posted November 12, 2019 Unfortunately provided log is probably not from first failed attempt -> in indicates database was in "corrupted" state before upgrade attempt started. My best guess is that initial upgrade attempt failed and left database in such state. This is probable especially in case older ERA version (possibly 6.4 or older) was upgrade as there were issue with DB corruption in case upgrade process was interrupted. We have seen that upgrade might take minutes (hours in extreme cases) and administrator were often interrupting this process which resulted in inconsistent state. Link to comment Share on other sites More sharing options...
Recommended Posts