Copy fails to start
Diaspar4u opened this issue · 4 comments
Neo4j 2.1.5 (changed version in the pom file).
Original graph.db works peachy. After done copying (and moving the resulting dir in place of original), neo4j fails to start. trying to start produces:
process [40888]... waiting for server to be ready... Failed to start within 120 seconds.
Neo4j Server may have failed to start, please check the logs.
(As a note, it does NOT wait 120 seconds, but the messages appear rather quickly... from the time it says "waiting" to "failed" literally a few seconds pass.
checking the console.log shows the following:
2014-11-25 22:18:21.635+0000 INFO [API] Setting startup timeout to: 120000ms based on -1
Detected incorrectly shut down database, performing recovery..
Neo4j version is 2.1.5, running on Ubuntu 14 in AWS. Database ends up being shrunk from 100 gigs to about 25 gigs. The process does complete successfully (or at least reports success).
This is urgent, as neo4j doesn't seem to free up space and the db grows uncontrollably even though the relationships are cycled (about the same amount is deleted as created, so db size should stay the same).
Issue resolved!
Noticed that running neo4j-console by root started db just fine. what this code doesn't do is apply final permissions, which was confirmed by compare (original is owned by user "neo4j", while result dir has everything owned by root).
To fix: "chown neo4j -R graph.db".
Ok, yes, permission changes is admin work, not task of this code :)
Because you ran this tool as root, if you had it run as neo user it would have set the right permissions.
The issue is that server just dies without telling you why, so the first
assumption is that copy failed since there is nothing else to go on.
Knowing this Would be saved me a day of digging and redoing.
On Wed, Nov 26, 2014 at 2:00 AM Michael Hunger notifications@github.com
wrote:
Ok, yes, permission changes is admin work, not task of this code :)
Because you ran this tool as root, if you had it run as neo user it would
have set the right permissions.—
Reply to this email directly or view it on GitHub
#1 (comment).
That is a great point, I send it as feedback to the Neo4j engineers.