As the question title suggests, our OrientDB database crashed today. We got notified by our monitoring server that our sites aren't accepting any requests anymore, which was quickly traced to OrientDB being unavailable, i.e., not running anymore.
However, when checking the logs (orientdb.err/orientdb.log), there was no indication at all of any crash. What can I do to investigate this issue, and, even better, prevent OrientDB from crashing again? This isn't the first time OrientDB crashes, but usually it's with an OutOfMemory exception, which we fixed(?) by giving it more memory. Currently, the DB hardly does anything (1 request per 10 seconds?), and we're a bit worried that once we do get some requests, that OrientDB might crash more often.
Our current settings to run OrientDB look like this:
JAVA_OPTS_SCRIPT="-Djna.nosys=true -XX:+HeapDumpOnOutOfMemoryError -Djava.awt.headless=true -Dfile.encoding=UTF8 -Drhino.opt.level=9"
# ORIENTDB MAXIMUM HEAP. USE SYNTAX -Xmx<memory>, WHERE <memory> HAS THE TOTAL MEMORY AND SIZE UNIT. EXAMPLE: -Xmx512m
# ORIENTDB MAXIMUM DISKCACHE IN MB, EXAMPLE, ENTER -Dstorage.diskCache.bufferSize=8192 FOR 8GB
If we need to provide some more information, please let me know.