windows-installers
windows-installers copied to clipboard
elastic
Error while upgrading 7.9.0 to 7.10.0
Environment
Windows 2016
Expected Behaviour
Upgrade process fails.
Actual Behaviour
Successful upgrade.
Steps to reproduce the behaviour
@GrzegorzLyp I had some trouble too. In my case it was going from 7.4.0 to 7.10.0. My issue was updates to the jvm.options. In the Application log I found there was some invalid entries for the latest version of the JDK. I was able to get my nodes upgraded by changing jvm.options before the install as described at https://discuss.elastic.co/t/elasticsearch-wont-start-after-7-9-1-to-7-9-2-upgrade/249878
Does this help you out? If so, hopefully the MSI installer is updated to automatically make these changes during upgrade.
I believe I have the same issue when trying to upgrade from 7.6.2 to 7.10.0. Installation log file is attached. install_log.txt
Environment
Windows 2016
Expected Behaviour
Upgrade process fails.
Actual Behaviour
Successful upgrade.
Steps to reproduce the behaviour
MSI (s) (A4:4C) [01:08:52:252]: Product: Elasticsearch 7.10.0 -- Error 1920. Service 'Elasticsearch' (Elasticsearch) failed to start. Verify that you have sufficient privileges to start system services.
I believe I have the same issue when trying to upgrade from 7.6.2 to 7.10.0. Installation log file is attached. install_log.txt
MSI (s) (B0:54) [16:42:00:854]: Product: Elasticsearch 7.10.0 -- Error 1920. Service 'Elasticsearch' (Elasticsearch) failed to start. Verify that you have sufficient privileges to start system services.
Is this issue being looked at? I've tried the latest version of the setup, 7.10.2 and it's failing in the same way. I've tried to uncheck the "start service after installation" and the setup completes successfully, but then the service cannot be started (starts then stops) and no errors are present in the logs. I've uninstalled Elasticsearch while keeping the data and config folders and a new installation also fails.
Also regarding the reply above mine, I don't think it's a question of permissions, I am running as Administrator and have run the installation with both the Local System and Network Service options. Both fail, and checking the account permissions, I am certain at least the latter is explicitly configured.
Below is the installation log for the Network Service attempt. install.LOG
Edit: after deleting both the config and data folders to simulate a clean/fresh installation, I think I understand why it fails. The jvm.options file in the latest version is different from the previous one and the setup fails to account for this.
The significant portion is this:
Is this issue being looked at? I've tried the latest version of the setup, 7.10.2 and it's failing in the same way. I've tried to uncheck the "start service after installation" and the setup completes successfully, but then the service cannot be started (starts then stops) and no errors are present in the logs. I've uninstalled Elasticsearch while keeping the data and config folders and a new installation also fails.
Also regarding the reply above mine, I don't think it's a question of permissions, I am running as Administrator and have run the installation with both the Local System and Network Service options. Both fail, and checking the account permissions, I am certain at least the latter is explicitly configured.
Below is the installation log for the Network Service attempt. install.LOG
Edit: after deleting both the config and data folders to simulate a clean/fresh installation, I think I understand why it fails. The jvm.options file in the latest version is different from the previous one and the setup fails to account for this.
The significant portion is this:
According to your log: Verify that you have sufficient privileges to start system services
Hello all,
On Windows we run Elasticsearch using a wrapper service process. This process reports its errors to Windows Event Log as shown in sample screenshot below. Please take a look and let us know, thanks!
HINT: wrapper process accepts --debug-env command line argument which might help in troubleshooting as well:
It is possible that certain manual changes to jvm.options file might cause the MSI to panic. I would suggest temporarily replacing your current file with one from, say, a .zip distribution, and then performing the upgrade. Replace the temporary options file with your original one.
If options file turns out to be the culprit, please let us know by attaching the offending file to an issue. This would help us immensely!
We also have a fix for a blocker in the 7.11 (#402).
@ygel In my case, already confirmed the jvm.options was the culprit. Either deleting it or replacing it with a newer version fixed the issue. There were no manual changes to the file, only by the installer. Check my original post to see the diff that I believe was changed starting with 7.7.0.
Behaviour-wise, the installer didn't properly update those options on upgrade (which is the actual bug imo), which made the service unable to start, which failed the setup process.