Skip to content
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 does not work in DocumentLoader #10

Open
mark-orion opened this issue Feb 10, 2016 · 2 comments
Open

neo4j does not work in DocumentLoader #10

mark-orion opened this issue Feb 10, 2016 · 2 comments
Labels
Milestone

Comments

@mark-orion
Copy link

following the instructions in the Readme file does not create a working DocumentLoader:
Rake wants to start neo4j from ./db/neo4j/development what is an empty directory.
Installing neo4j through their debian repo results in a working neo4j installation, but the rails server is not acknowledging it.
Copying neo4j in the ./db/neo4j/development folder allows to start neo4j with the "Rake" command, but the rails server still crashes:
Exiting
/home/mark/.rvm/gems/ruby-2.2.1/gems/neo4j-core-5.1.12/lib/neo4j-server/resource.rb:37:in `handle_response_error!': Expected response code 200 Error for request http://localhost:7474/db/data/, 401 (Neo4j::Server::Resource::ServerException)
Please fix and/or give clear instructions in the Readme

@bnvk
Copy link
Member

bnvk commented Mar 29, 2016

@mark-orion thanks for reporting this. What OS are you using? Debian? I notice a case, whereby after installing neo4j it is always automatically running in the background as a user: neo4j I have to kill the process, then when it restarts via the rake command, it runs as the same user as the Rails app and does not crash. Obviously this is not good, but we will probably resolve it once we packages our tools

@bnvk bnvk added the bug label Mar 29, 2016
@bnvk bnvk added this to the Packaging milestone Mar 29, 2016
@mark-orion
Copy link
Author

@bnvk thanks for looking into this. I am running XUbuntu 14.04 "Trusty". I did not see any neo4j process running, but this might be because I usually clean up all autostart scripts and only start the server demons I really need manually. I am not a Ruby expert, but I notice that it wants to start from the empty development directory. I wonder if that path is set somewhere within the software and needs changing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants