-
Notifications
You must be signed in to change notification settings - Fork 169
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
Random exits #32
Comments
@coeus01 Do you see anything in the logs for the failed container? Most likely problem is running out of memory, I would have thought. You may need to set an increased size for heap or cache size -- the environment variable you need depends on which version of Neo4j you're using. |
@benbc Nothing in the logs, this problem also happens sometimes on
other times it exits earlier:
after a few |
@coeus01 Do you have any insight into why there are those repeated logs "Starting/Bolt enabled"? Are you trying to start it multiple times there, or is Docker Compose doing that? |
@benbc no.. they are completely random, sometimes it's only one, other times they are 10 |
@coeus01 Can you give us as much information as possible about your system? Docker and Neo4j versions, OS and version, system memory available, anything else that might be relevant. |
|
UPDATE even when I start all the containers with |
@coeus01 Thank you, that's useful information. We'll take a look. |
@coeus01 the problem is in your this line:
change the password to anything other than
Neo4j does not support setting a custom password equal to the default neo4j password. That's why the container never comes up. An error message is shown if you try to do it in the browser. We should probably add some logic to the docker entrypoint script that clearly tells you not to set the password to |
@spacecowboy my password is not |
@coeus01 We have now reproduced your problem. Setting the password via |
… password This start-up was timing out on Debian Jessie but not other platforms. The timeout should have been longer anyway because, while it's reasonable to expect the database to start in 10 seconds, we can afford to give it a very long timeout to accommodate slow edge cases since it will only fail if something is badly wrong. Fixes #32.
@coeus01 The fix for this will be in Neo4j 3.0.2. |
@benbc when will this version be available in the Docker Hub? Currently it's still showing 3.0.1, so I think the issue should still show as open. |
@textbook The 3.0.2 image will be published later today. |
For anyone else wondering, the new image will be available when this PR is accepted: docker-library/official-images#1809 |
Hello, I'm using neo4j in a docker-compose project and sometimes I need to start the neo4j docker 3-4 times in order to stay up and it randomly exits (Exited (137)) sometimes after 3 days, sometimes after 3 hours. The same thing happens for
docker-compose up
as well asdocker start project_db
, the other services that I have along are working as expected.docker-compose.yml
The text was updated successfully, but these errors were encountered: