Login error after upgrade VA EP from 9.0 to 10.0

[question-guy 1]

Hello,

Yesterday I have update an Eset Protect environment based on Virtual Appliance from the Web Console setting. I have put task for update from EP 9.0 to 10.0. Today I cannot login to the Web Console. I have an error code ""loginConnectionStateNotConnected"

I try out a one of the ESET KB's instruction, exactly a KB6760 and instruction finded on this forum: 

 but clearly without an effect. For surprise I have today a call from on of the Customer whos have this same case and also have a server on Virtual Appliance and have done upgrade from version 9.0 to 10.0

I find information about ODBC drivers and downgrade it from version 8.X to version 5.3 and change on NANO entries. Also I try out this solution:

 

/etc/odbcinst.ini

[MySQL ODBC 5.3 Unicode Driver]
Driver=/usr/lib64/libmyodbc8a.so
UsageCount=1

Still I cannot login into the Web Console. I try restart server few times and nothing changes. Once I try connect to web console during the restart procedure i have a LOG from web console windows:

 

*version : 9.0.138.0*
*locale : pl_PL*
*user.agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36 (safari)*
*document : https://192.168.1.93/era/webconsole/9F18AC3AC14CB94F0FE83102182EC234.cache.html*
*url: https://192.168.1.93/era/webconsole/*
        
*error: *
An uncaught exception has occurred! (" "Error: Network error: Failed to fetch ")
@     at new t (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:49567) @
@     at Object.error (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:200:449483) @
@     at v (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:527608) @
@     at C (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528065) @
@     at e.value (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528682) @
@     at https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:200:466477 @
@     at Set.forEach (<anonymous>) @
@     at Object.error (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:200:466438) @
@     at v (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:527608) @
@     at C (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528065) @
@     at e.value (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528682) @
@     at v (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:527608) @
@     at C (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528065) @
@     at e.value (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528682) @
@     at https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:200:482823 @
@     at Array.forEach (<anonymous>) @
@     at https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:200:482795 @
@     at Array.forEach (<anonymous>) @
@     at Object.d [as error] (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:200:482769) @
@     at v (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:527608) @
@     at C (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528065) @
@     at e.value (https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:168:528682) @
@     at https://192.168.1.93/era/webconsole/static/js/main.285fa9a8.cache.js:200:478950" @ 

But as I reading it - it could be related to startup procedure.

Have anyone have any tips for what to check or what to done to resolve this problem in my console and Customer console ? Right now I try to update a ODBC drivers to newest version and try to change names from 5.3 to 8.X again and hope that could do anything...

On the Customer console also there is a problem with MySQL DB:

 

> InnoDB: The error means the system cannot find the path specified.

> InnoDB: If you are installing InnoDB, remember that you must create

> InnoDB: directories yourself, InnoDB does not create them.

> InnoDB: Error: could not open single-table tablespace file

> ./era_db/tbl_access_tokens_register.ibd

> InnoDB: We do not continue the crash recovery, because the table may

> become

> InnoDB: corrupt if we cannot apply the log records in the InnoDB log

> to it

 

Please let me know if you have any ideas for this case