Closed dhimmel closed 6 years ago
Here are the 30 day graphs for our Digital Ocean droplet usage:
You can see the crash was preceded by heavy disk IO but not a huge amount of CPU usage.
I rebooted the Droplet, and the docker restarted, so https://neo4j.het.io is now working. I could consider upgrading our instance to 3.2.12 (Dockerfile
). See the 3.2 changelog here.
Update: Neo4j 3.2.12 has a permissions issue when mapping the logs volume. see https://github.com/neo4j/docker-neo4j/issues/131#issuecomment-398097390.
I'm closing this issue, since the instance is now up. Hopefully it doesn't come back... maybe the upgrade to 3.2.8 in https://github.com/dhimmel/hetionet/commit/9f214ab7cb6b59fde5fd9530e379d2d71cee4f43 will fix it.
I noticed https://neo4j.het.io/browser/ is currently not working with
ERR_CONNECTION_REFUSED
. I randocker logs hetionet-container
to see what happened. Below is the tail of the docker logs:So it looks like Neo4j ran out of memory. We've had similar issues in the past with Neo4j 3.1: see https://github.com/neo4j/neo4j/issues/9209. We have also had an issue where Neo4j runs out of memory but does not die as a process: see https://github.com/dhimmel/hetionet/issues/5. Currently neo4j.het.io is running Neo4j 3.2.3:
https://github.com/dhimmel/hetionet/blob/6d26d15e9055b33b4fd97a180fa288e4f2060b96/hetnet/neo4j/docker/Dockerfile#L1
So the two main questions for me are: