Logstash file input plug - exception argument error

Hi All

Getting a weird error when trying to use the file input plugin.

Some information on my environment

java --version
openjdk 11.0.3 2019-04-16
OpenJDK Runtime Environment (build 11.0.3+7-Ubuntu-1ubuntu218.04.1)
OpenJDK 64-Bit Server VM (build 11.0.3+7-Ubuntu-1ubuntu218.04.1, mixed mode, sharing)

logstash-input-file (4.1.10)

bin/logstash --version
logstash 7.2.0

Logstash input config -

input {
file {
path => "/data/my-logs/*"
mode => "read"
file_completed_action => "log"
sincedb_path => "/data/logstash-db/20_sincedb"
file_completed_log_path => "/data/logstash-db/20_file_completed_log"
}
}

The files are all .gz files.

The error -

Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: Plugin: <LogStash::Inputs::File mode=>"read", path=>["/data/my-logs-logs/*"], id=>"46723655fc001488cf5ff6d5dc3bc4a6b319d2b1f226e73155eac6b447c1a9b1", file_completed_action=>"log", sincedb_path=>"/data/logstash-db/20_sincedb", file_completed_log_path=>"/data/logstash-db/20_file_completed_log", enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_868e1ea4-3fcc-457b-af16-40dc95679d0d", enable_metric=>true, charset=>"UTF-8">, stat_interval=>1.0, discover_interval=>15, sincedb_write_interval=>15.0, start_position=>"end", delimiter=>"\n", close_older=>3600.0, sincedb_clean_after=>1209600.0, file_chunk_size=>32768, file_chunk_count=>140737488355327, file_sort_by=>"last_modified", file_sort_direction=>"asc">
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: Error: wrong number of arguments (given 1, expected 0)
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: Exception: ArgumentError
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: Stack: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/read_mode/handlers/read_zip_file.rb:26:in handle_specifically' Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/read_mode/handlers/base.rb:26:inhandle'
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/read_mode/processor.rb:39:in read_zip_file' Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/read_mode/processor.rb:102:inblock in process_active'
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: org/jruby/RubyArray.java:1792:in each' Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/read_mode/processor.rb:88:inprocess_active'
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/read_mode/processor.rb:45:in process_all_states' Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/watch.rb:67:initerate_on_state'
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/watch.rb:45:in subscribe' Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/filewatch/observing_read.rb:12:insubscribe'
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.1.10/lib/logstash/inputs/file.rb:339:in run' Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:309:ininputworker'
Jul 3 11:53:50 sys-logstash-my-logs logstash[10366]: /usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:302:in `block in start_input'

fixed -

Just so everyone knows/if anyone finds this on google in the future.

the plugin doesnt work with Java 11, you need to install java 8, and everything is fine.

Yeah, this has been seen before with Java 12, which is not supported, although 11 is.

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