When logstash has eventlog inputs configured on systems that have a high volume of eventlog traffic it crashes after a relatively short period of time with the following dump:
Peak volume appears to be about 150 eventlog entries per second.
C:\logstash\bin>logstash agent -f logstash.conf
io/console not supported; tty will not be manipulated
Default settings used: Filter workers: 1
Logstash startup completed
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fef3501aa4, pid=4616, t
id=2656
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b15) (build 1.8.0_45-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode windows-amd64
compressed oops)
# Problematic frame:
# C [racob-x64.dll+0x1aa4]
#
# Core dump written. Default location: C:\logstash\bin\hs_err_pid4616.mdmp
#
# An error report file with more information is saved as:
# C:\logstash\bin\hs_err_pid4616.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
I had this issue in 1.5 as well, and honestly I'm a little surprised that it still exists.. it seems to be a pretty well reported issue?
Here's what Visual Studio has to say about the dump, unfortunately the full text is too long for a post here, so I've truncated the loaded modules:
Dump Summary
------------
Dump File: hs_err_pid4616.mdmp : C:\Users\username\Desktop\hs_err_pid4616.mdmp
Last Write Time: 11/19/2015 10:41:18 AM
Process Name: java.exe : C:\Program Files\Java\jre1.8.0_45\bin\java.exe
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Present
System Information
------------------
OS Version: 6.1.7601
CLR Version(s):
SET GEM_HOME=C:\logstash\vendor\bundle\jruby\1.9
C:\logstash\vendor\jruby\bin>gem install win32-eventlog
io/console not supported; tty will not be manipulated
Fetching: ffi-1.9.10-java.gem
(100%)
Successfully installed
ffi-1.9.10-java
Successfully installed
win32-eventlog-0.6.5
2 gems installed
Updated eventlog.rb with the contents of the file here:
Still crashes...
C:\logstash\bin>logstash agent -f logstash.conf
io/console not supported; tty will not be manipulated
Default settings used: Filter workers: 1
Logstash startup completed
java.lang.OutOfMemoryError: Java heap space
Dumping heap to java_pid904.hprof ...
Heap dump file created [1086460308 bytes in 2.960 secs]
Error: Your application used more memory than the safety cap of 1G.
Specify -J-Xmx####m to increase it (#### = cap size in MB).
Specify -w for full OutOfMemoryError stack trace
playing with memory settings now
UPDATE: Giving it 2 gigs seems to have done the trick.. stable now.. fingers crossed!
I dunno.. I don't think it's a memory issue. I would have expected an out of memory error before the update and test I ran. Not to mention the other people having the same problem...
Also worth mentioning that when Java runs out of memory it writes a different type of dump.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.