Issues
- Crash after standby with evenlog input on WindowsLOGSTASH-2095Logstash Developers
- missing jruby-win32ole gem in logstash 1.4.0rc1LOGSTASH-2004Resolved issue: LOGSTASH-2004Logstash Developers
- input: eventlog: redundant field: typeLOGSTASH-1903Philippe Weber
- input: eventlog: redundant field: hostLOGSTASH-1902Philippe Weber
- input: eventlog: redundant field: pathLOGSTASH-1901Philippe Weber
- Eventlog Input Error - Invalid format: "2014-01-22T19:26:07+00:00" is malformed at "+00:00"LOGSTASH-1821Resolved issue: LOGSTASH-1821Philippe Weber
- Existing events not being importedLOGSTASH-1636Resolved issue: LOGSTASH-1636Logstash Developers
- Change eventlog logfile default value to everythingLOGSTASH-1517Resolved issue: LOGSTASH-1517Logstash Developers
- Duplicate message field in json from windows eventlogLOGSTASH-1510Logstash Developers
- Read old Windows eventlog logsLOGSTASH-1506Logstash Developers
- Multiline filter with Windows Event LogLOGSTASH-1431Logstash Developers
- Wrong Encoding ASCII-8BIT to UTF-8 for input eventlog for German UmlautsLOGSTASH-1390Logstash Developers
12 of 12
Crash after standby with evenlog input on Windows
Description
Gliffy Diagrams
Details
Details
Assignee
Logstash Developers
Logstash DevelopersReporter
Aron Curzon
Aron CurzonCreated April 6, 2014 at 8:06 AM
Updated February 14, 2015 at 6:53 AM
Activity
Show:
Kurt Hurtado
updated the LabelsFebruary 14, 2015 at 6:53 AMeventlog input/eventlog udp windows
eventlog input/eventlog output/udp udp windows
Kurt Hurtado
updated the LabelsFebruary 14, 2015 at 6:52 AMeventlog udp windows
eventlog input/eventlog udp windows
Aron Curzon
updated the DescriptionApril 6, 2014 at 8:08 AMWith evenlog input AND udp output, logstash crashes after resume from standby(S3)
With only eventlog input OR udp output logstash does not crash after resume from standby(S3)
stacktrace, configuration, system info - https://gist.github.com/curzona/10002556
{{Exception in thread "LogStash::Runner" org.jruby.exceptions.RaiseException: (Soc
ketError) send: name or service not known
at org.jruby.ext.socket.RubyUDPSocket.send(org/jruby/ext/socket/RubyUDPS
ocket.java:318)
at RUBY.register(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logsta
sh-1.3.3-flatjar.jar!/logstash/outputs/udp.rb:25)
at org.jruby.RubyProc.call(org/jruby/RubyProc.java:271)
at RUBY.encode(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstash
-1.3.3-flatjar.jar!/logstash/codecs/json.rb:45)
at RUBY.receive(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstas
h-1.3.3-flatjar.jar!/logstash/outputs/udp.rb:35)
at RUBY.handle(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstash
-1.3.3-flatjar.jar!/logstash/outputs/base.rb:86)
at RUBY.initialize((eval):24)
at org.jruby.RubyProc.call(org/jruby/RubyProc.java:271)
at RUBY.output(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstash
-1.3.3-flatjar.jar!/logstash/pipeline.rb:259)
at RUBY.outputworker(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/lo
gstash-1.3.3-flatjar.jar!/logstash/pipeline.rb:218)
at RUBY.start_outputs(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/l
ogstash-1.3.3-flatjar.jar!/logstash/pipeline.rb:145)}}
With evenlog input AND udp output, logstash crashes after resume from standby(S3)
With only eventlog input OR udp output logstash does not crash after resume from standby(S3)
stacktrace, configuration, system info - https://gist.github.com/curzona/10002556
{quote}
Exception in thread "LogStash::Runner" org.jruby.exceptions.RaiseException: (Soc
ketError) send: name or service not known
at org.jruby.ext.socket.RubyUDPSocket.send(org/jruby/ext/socket/RubyUDPS
ocket.java:318)
at RUBY.register(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logsta
sh-1.3.3-flatjar.jar!/logstash/outputs/udp.rb:25)
at org.jruby.RubyProc.call(org/jruby/RubyProc.java:271)
at RUBY.encode(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstash
-1.3.3-flatjar.jar!/logstash/codecs/json.rb:45)
at RUBY.receive(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstas
h-1.3.3-flatjar.jar!/logstash/outputs/udp.rb:35)
at RUBY.handle(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstash
-1.3.3-flatjar.jar!/logstash/outputs/base.rb:86)
at RUBY.initialize((eval):24)
at org.jruby.RubyProc.call(org/jruby/RubyProc.java:271)
at RUBY.output(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/logstash
-1.3.3-flatjar.jar!/logstash/pipeline.rb:259)
at RUBY.outputworker(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/lo
gstash-1.3.3-flatjar.jar!/logstash/pipeline.rb:218)
at RUBY.start_outputs(file:/C:/Users/adcurzon/Downloads/logstash-1.3.3/l
ogstash-1.3.3-flatjar.jar!/logstash/pipeline.rb:145)
{quote}
Aron Curzon
created the IssueApril 6, 2014 at 8:06 AM
With evenlog input AND udp output, logstash crashes after resume from standby(S3)
With only eventlog input OR udp output logstash does not crash after resume from standby(S3)
stacktrace, configuration, system info - https://gist.github.com/curzona/10002556