elastic/logstash

Logstash error "Microsystems was unexpected at this time."

Open

Aperta il 30 mar 2020

Vedi su GitHub
 (2 commenti) (0 reazioni) (0 assegnatari)Ruby (14.197 star) (3496 fork)batch import
good first issuewindows

Descrizione

  • Version: 7.6.1
  • Operating System: Windows 10, ver 1709
  • Config File (if you have sensitive info, please remove it):
  • Sample Data:
  • Steps to Reproduce:
  1. Install java.
> java -version
Picked up JAVA_TOOL_OPTIONS: -Djava.vendor="Sun Microsystems Inc."
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)
  1. Extract the logstash zip.
  2. Open a command line window.
  3. Move to bin folder and run logstash.
  4. Error shown: Microsystems was unexpected at this time.

This issue is similar to 26261.

Workaround as of now to make it logstash start: Comment out the block in setup.bat in bin folder.

rem do not let JAVA_TOOL_OPTIONS slip in (as the JVM does by default)
if not "%JAVA_TOOL_OPTIONS%" == "" (
  echo "warning: ignoring JAVA_TOOL_OPTIONS=$JAVA_TOOL_OPTIONS"
  set JAVA_TOOL_OPTIONS=
)

and add just set the env variable to empty. As below.

rem do not let JAVA_TOOL_OPTIONS slip in (as the JVM does by default)
rem if not "%JAVA_TOOL_OPTIONS%" == "" (
rem   echo "warning: ignoring JAVA_TOOL_OPTIONS=$JAVA_TOOL_OPTIONS"
rem   set JAVA_TOOL_OPTIONS=
rem )
set JAVA_TOOL_OPTIONS=

Guida contributor

Tech stack
shell
Dominio
backend
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
under 1 hour
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Windows batch scripting
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
80
Direzione di ricerca
The issue is in bin/setup.bat. The problem occurs because the batch script incorrectly parses the JAVA TOOL OPTIONS variable when it contains parentheses. The workaround involves setting the variable to empty after checking. To fix, update the batch script to properly handle the variable, similar to the referenced Elasticsearch issue #26261. The file is located at bin/setup.bat in the Logstash repository.