Logstash error "Errno::EACCES: Permission denied - NUL" when installing plugin input-syslog

Elastic Stack Logstash
1

Hi,
I haven't been able to install logstash-input-syslog

I thought this could be solved by following this but it did not solve it

I am trying this in a Windows 11 Enterprise Evaluation VM (WINDEV2204EVAL)
Attaching the jvm.options file, I added the -Djdk.io.File.enableADS=true at the end.

## JVM configuration

# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space

-Xms1g
-Xmx1g

################################################################
## Expert settings
################################################################
##
## All settings below this section are considered
## expert settings. Don't tamper with them unless
## you understand what you are doing
##
################################################################

## GC configuration
11-13:-XX:+UseConcMarkSweepGC
11-13:-XX:CMSInitiatingOccupancyFraction=75
11-13:-XX:+UseCMSInitiatingOccupancyOnly

## Locale
# Set the locale language
#-Duser.language=en

# Set the locale country
#-Duser.country=US

# Set the locale variant, if any
#-Duser.variant=

## basic

# set the I/O temp directory
#-Djava.io.tmpdir=$HOME

# set to headless, just in case
-Djava.awt.headless=true

# ensure UTF-8 encoding by default (e.g. filenames)
-Dfile.encoding=UTF-8

# use our provided JNA always versus the system one
#-Djna.nosys=true

# Turn on JRuby invokedynamic
-Djruby.compile.invokedynamic=true
# Force Compilation
-Djruby.jit.threshold=0

## heap dumps

# generate a heap dump when an allocation from the Java heap fails
# heap dumps are created in the working directory of the JVM
-XX:+HeapDumpOnOutOfMemoryError

# specify an alternative path for heap dumps
# ensure the directory exists and has sufficient space
#-XX:HeapDumpPath=${LOGSTASH_HOME}/heapdump.hprof

## GC logging
#-Xlog:gc*,gc+age=trace,safepoint:file=@loggc@:utctime,pid,tags:filecount=32,filesize=64m

# log GC status to a file with time stamps
# ensure the directory exists
#-Xloggc:${LS_GC_LOG_FILE}

# Entropy source for randomness
-Djava.security.egd=file:/dev/urandom

# Copy the logging context from parent threads to children
-Dlog4j2.isThreadContextMapInheritable=true

-Djdk.io.File.enableADS=true

I am attaching here the steps I am following and the error display:

PS C:\logstash-8.3.0-windows-x86_64\logstash-8.3.0\bin> .\logstash-plugin install logstash-input-syslog
"Using bundled JDK: C:\logstash-8.3.0-windows-x86_64\logstash-8.3.0\jdk\bin\java.exe"
Validating logstash-input-syslog
Resolving mixin dependencies
Errno::EACCES: Permission denied - NUL
                             sysopen at org/jruby/RubyIO.java:1237
                          initialize at org/jruby/RubyFile.java:365
                                open at org/jruby/RubyIO.java:1156
                          initialize at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/jruby/lib/ruby/stdlib/rubygems/user_interaction.rb:645
                          initialize at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/ui/rg_proxy.rb:11
                                 ui= at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler.rb:91
                                  ui at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler.rb:87
                            validate at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/rubygems_integration.rb:68
                       validate_spec at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/source/path.rb:168
                     load_spec_files at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/source/path.rb:182
                                each at org/jruby/RubyArray.java:1821
                     load_spec_files at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/source/path.rb:176
                         local_specs at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/source/path.rb:107
                               specs at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/source/path.rb:115
           specs_for_source_changed? at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/definition.rb:562
                      specs_changed? at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/definition.rb:547
                      converge_paths at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/definition.rb:591
                                any? at org/jruby/RubyArray.java:4553
                      converge_paths at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/definition.rb:590
                          initialize at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/definition.rb:134
                       to_definition at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/dsl.rb:219
                            evaluate at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/dsl.rb:13
                               build at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler/definition.rb:38
                          definition at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/bundler-2.3.16/lib/bundler.rb:208
  expand_logstash_mixin_dependencies at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/lib/bootstrap/bundler.rb:218
  update_logstash_mixin_dependencies at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/lib/pluginmanager/install.rb:190
                             execute at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/lib/pluginmanager/install.rb:78
                                 run at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:68
                             execute at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/subcommand/execution.rb:11
                                 run at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:68
                                 run at C:/logstash-8.3.0-windows-x86_64/logstash-8.3.0/vendor/bundle/jruby/2.5.0/gems/clamp-1.0.1/lib/clamp/command.rb:133
                              <main> at C:\logstash-8.3.0-windows-x86_64\logstash-8.3.0\lib\pluginmanager\main.rb:64
PS C:\logstash-8.3.0-windows-x86_64\logstash-8.3.0\bin>

Please, let me know what I am missing
Thanks in advance

2

I'm seeing exactly the same issue when trying to install Logstash 8.3.0 on Windows 10 (as part of an upgrade from Logstash 8.1.2).

All I've done is unpack the Logstash 8.3.0 zip file into a suitable folder and then run the logstash-plugin.bat file to list the installed plugins. This results in the same failure as Carlos has reported:

image
image1180×598 21.5 KB

I still see the error even after following the instructions to add the following line to the logstash config jvm.options file:
-Djdk.io.File.enableADS=true

Thanks,
Steve

3

Just tried the latest LS version (8.3.1) released a few days ago but that shows the same issue.

Steve

4

To provide an update here, I am not sure if it is necessary to install the plugins since these are loaded depending on the ones stated in the .conf file.

PS C:\logstash-8.3.2> .\bin\logstash.bat -f .\config\<logstash>.conf
5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.