-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
neo4j.het.io down as of 2018-06-13 #9
Comments
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 ( Update: Neo4j 3.2.12 has a permissions issue when mapping the logs volume. see neo4j/docker-neo4j#131 (comment). |
Upgrade in case newer version contains a fix for the memory issues from #9. 3.2.9 to 3.2.12 are released but have a permissions issue with volume mapping the logs directory. See neo4j/docker-neo4j#131
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 9f214ab will fix it. |
Upgrade in case newer version contains a fix for the memory issues from #9. 3.2.9 to 3.2.12 are released but have a permissions issue with volume mapping the logs directory. See neo4j/docker-neo4j#131 Former-commit-id: 9f214ab
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 neo4j/neo4j#9209. We have also had an issue where Neo4j runs out of memory but does not die as a process: see #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:
The text was updated successfully, but these errors were encountered: