Error: File name too long - ReadEventLog

[laoshancun]

logstash version

D:\logstash-2.3.4\bin>java -version java version "1.8.0_66" Java(TM) SE Runtime Environment (build 1.8.0_66-b18) Java HotSpot(TM) 64-Bit Server VM (build 25.66-b18, mixed mode)

error info:

Error: File name too long - ReadEventLog {:level=>:error}[0m#[31mA plugin had an unrecoverable error. Will restart this plugin. Plugin: <LogStash::Inputs::EventLog type=>"Win32-EventLog", codec=><LogStash::#Codecs::Plain charset=>"UTF-8">, logfile=>"Application", interval=>1000>

here is my config file:

# For detail structure of this file
# Set: https://www.elastic.co/guide/en/logstash/current/configuration-file-structure.html
input {
    eventlog {
        type => "Win32-EventLog"
        #logfile => ["Application", "System", "Security"]
        codec => plain{
            charset => 'UTF-8'
        }
    }
}
filter {

}
output {
  # For detail config for elasticsearch as output,
  # See: https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html
    stdout { codec => rubydebug }
 #file {
 #  path => "d:/test.txt"
 #}
}

[jordansissel]

This second error message seems different than your first. Can you file a separate issue about the 2nd error message?

On Saturday, August 27, 2016, Laoshancun notifications@github.com wrote:

there is another error

[31mA plugin had an unrecoverable error. Will restart this plugin. Plugin: <LogStash::Inputs::EventLog type=>"Win32-EventLog", codec=><LogStash::Codecs::Plain charset=>"UTF-8">, logfile =>"Application", interval=>1000> Error: Unknown error 1503 - ReadEventLog {:level=>:error}[0m

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/logstash-plugins/logstash-input-eventlog/issues/35#issuecomment-242902089, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIC6s4Tt6IZLrgjMIfTffw9sFTiUhb5ks5qj-eOgaJpZM4Jt8hV .

[laoshancun]

@jordansissel ok https://github.com/logstash-plugins/logstash-input-eventlog/issues/36

[sametserpil]

@jordansissel @laoshancun Getting same error. Is there any update regarding to this?