Error upgrading from ESMC 7.0 to 7.2 (latest)

[autobanned 0]

Hello all,

I would like to ask something about the latest ESMC.

 

I have an ESMC on Ubuntu 16.04 hosts running ESMC 7.0 and i want to upgrade it to the latest version. 

I started the upgrade procedure from the ESMC WebConsole and running the ESMC Component Upgrade task, but it took me over 3 days and the task is still running and without any error message on the log.

So i just stopped the upgrade procedure and run the upgrade proccess manually.

I backed up the database dan stop the eraserver services. Then executed the esmc installer script to install the new version of ESMC.

The script executed successfully without any error, and the ESMC is already installed without error. But i cannot start the eraserver service, and the  systemd services status only give me hint that eraserver PID not found, and then i go over to the /var/log/eset/RemoteAdministrator/Server/trace.log to check the log, and i got this error of 

(mysqld-5.7.27) Unknown table 'era_db.fact_fe_threat_event'

I did performed the upgrade procedure a few more time, but still got the same results and I cannot start the eraserver services.

 

Thx in advice for any help guys, and

Pardon me for my bad english...

 

 

[Marcos 5,074]

Would it be possible to revert to the previous version? How much RAM is installed on the machine? How many clients connect to the ESMC server?

[MartinK 378]

Also would it be possible to attach trace.log that covers first startup of service after upgrade? Previously attached screenshot/log shows startup that fails to properly recover from previous failures, so problem probably happened during previous startup.

Also note that crucial part of upgrade actually happens during first startup after installer execution: this process might take more resources than normally required (depending on amount of data present in database prior to upgrade) and unexpected interruption might result in unexpected state, probably as is the one from this case.

[autobanned 0]

On 10/14/2020 at 10:49 PM, Marcos said:

Would it be possible to revert to the previous version? How much RAM is installed on the machine? How many clients connect to the ESMC server?

it think it not possible to revert to previous state,  since we don't any backup or snapshot taken before running the upgrade proccess.

and for the RAM AFAIK the machine have sufficient enough RAM installed (8GB), but tbh i don't have direct access to machine before the accident happened, so i don't really know the system load while upgrade proccess is running.

[autobanned 0]

On 10/15/2020 at 2:30 AM, MartinK said:

Also would it be possible to attach trace.log that covers first startup of service after upgrade? Previously attached screenshot/log shows startup that fails to properly recover from previous failures, so problem probably happened during previous startup.

Also note that crucial part of upgrade actually happens during first startup after installer execution: this process might take more resources than normally required (depending on amount of data present in database prior to upgrade) and unexpected interruption might result in unexpected state, probably as is the one from this case.

Hi mates, this is the log of my era server, i replace the compression with to .zip cause tgz upload is not supported.

 

customer_info.zip