Jump to content

Upgrade ESMC 7.1 to latest version failed

Recommended Posts

Hello forum,

we try to update the ESMC 7.1 Module to the latest version. Its installed as virtuell ERA-Appliance. If we try to update over the management website we get an unkown error (found in audit log)Undocumented serious error.

If we try it with the console we get the following error:
2020-09-17 11:30:30 Information: Installer: Extracting archive to /tmp/tmp.NdjArT0xeu
2020-09-17 11:30:32 Information: Installer: Archive extracted to /tmp/tmp.NdjArT0xeu.
2020-09-17 11:30:32 Information: Installer: Checking OpenSSL ...
./server-linux-x86_64.sh: Zeile 1823: /tmp/tmp.NdjArT0xeu/setup/CustomActions: Keine Berechtigung
2020-09-17 11:30:32 Information: Installer: Failed dependency check for OpenSSL.
2020-09-17 11:30:32 Information: Installer: Error: 1836: Error occurred while checking OpenSSL

current version:

ESET Security Management Center (Server), Version 7.1 (7.1.503.0)
ESET Security Management Center (Web Console), Version 7.1 (7.1.393.0)
CentOS (64-bit), Version 7.8.2003

current openssl version:

OpenSSL 1.0.2k-fips  26 Jan 2017

Normally we do it in this way: https://help.eset.com/esmc_admin/72/en-US/client_tasks_upgrade_components.html

Any ideas?




Link to comment
Share on other sites

  • ESET Staff

Could you please attach log file:


It contains more detailed information - might helps with Analysis. From provided output it indeed seems that OpenSSL verification fails, but OpenSSL version seems to be correct. Any chance multiple versions are installed? Or were there made any changes in appliance itself? Asking as I am surprised by "german" error in output of logs, which is suspicious as we are not localizing such messages - maybe locale of system was changed from default en_US?

Also there is an alternate method for upgrade, using migration to completely new appliance: https://help.eset.com/esmc_deploy_va/72/en-US/?va_upgrade_migrate.html which would probably helps, but it might consequences in case some custom modifications of system or administrative operations were made (i.e. manual joining into domain, etc.).

Link to comment
Share on other sites

Dear Martin,
thank you for your feedback.
We took another look at the "EraServerInstaller.log" and read over the line "./server-linux-x86_64.sh: Line 1823: /tmp/tmp.NdjArT0xeu/setup/CustomActions: No permission" all the time.
This was because /tmp was mounted with "noexec".
Thanks for your help!
Many greetings

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...