``` root@921206babbc9:/# /var/lib/neo4j/bin/neo4j console
Starting Neo4j Server console-mode... Using additional JVM arguments: -server -XX:+DisableExplicitGC -Dorg.neo4j.server.properties=conf/neo4j-server.properties -Djava.util.logging.config.file=conf/logging.properties -Dlog4j.configuration=file:conf/log4j.properties -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:-OmitStackTraceInFastThrow -XX:hashCode=5 -Dneo4j.ext.udc.source=debian 2015-06-01 16:39:34.082+0000 INFO [API] Setting startup timeout to: 120000ms based on 120000 2015-06-01 16:39:35.100+0000 INFO [API] Successfully shutdown Neo4j Server. ``` Running neo4j v2.2.2 in a Docker container. On one environment, the thing starts up just fine, but on another, with more data, it does this start then stop trick. Note that neither environment has much data at all. Barely double digits number of nodes. The databases were upgraded from an older version of neo4j recently. Anyway, with that log output I'm not really sure where to go with this. Does anyone have a clue as to what might cause it to launch and just shutdown on its own? (Notice that the time delta between the last two entries in that log is just a second or so.) -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
