Neo4J Enterprise 3.0.4 Indefinite Hang, Recovery Requires Restart - neo4j

Neo4J enterprise is hanging indefinitely. Recovery requires a Neo4J restart. We use Python scripts with py2neo to ingest public data into Neo4J enterprise 3.0.4. So far we have been unable to complete the ingestion script. Before the script completes, Neo4J hangs indefinitely. There is nothing interesting in the logs. If we try the browser, the busy cursor appears and spins. This problem started for us when we upgraded from 3.0.2 to 3.0.4.
Has anyone else encountered this problem? For now, we'll try reverting the Neo4J release and see if that fixes the problem.

Related

neo4j on CENTOS 6.9 keeps stopping

I'm running Neo4j 3.2.6 on CENTOS 6.9. I have two problems:
First, Neo4j keeps stopping (typically about 5 times per day). There is nothing in the debug.log at the time of the failure (although there are many lines from the time I restart the service). How can I identify the problem? Which log files would give me a clue to the problem? Happy to share log files here if someone tells me which files to share.
Second, the above problem is compounded by the fact that I can't get Neo4j to restart automatically when it fails. I believe CENTOS 6.9 uses Upstart but I'm not having much luck setting this up. How do I set up Neo4j to restart on failure in CENTOS 6.9?

Why APOC (apoc-3.0.4.1-all.jar) not able to load in neo4j community edition, the same with other custom neo4j plugins?

However, the plugin as loaded in the enterprise edition with issue even with warnings. Also, there is not way to check for logs.
error : Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase#4006b29' was successfully initialized, but failed to start. Please see attached cause exception.
Both Community and enterprise version of Neo4j running on the same machine.
This is command used to find the running process
ps aux | grep java
Kill the enterprise process and restart the community edition.

Neo4j database maxing CPU following upgrade to 3.0

I upgraded to Community version 3.0 and now when I open my database the CPU stays consistently above 85%. I've tried uninstalling and reinstalling, deleting the old installs and their config files and reinstalling, and letting it run in case neo4j was reindexing or similar and just needed time. The database was running very well under 3.0.0-M02 but I don't have that exe to try reinstalling that. I've tried 3.0.0-M05 which didn't help.
Can anyone suggest a way for me to get the database running properly again?
Is it doing recovery? If you start the database, does it fully start as expected and then go into this "mode"? Can you do a thread dump and paste here? For capturing a thread dump use jps -lm to figure out which process ID your neo4j process has and capture the thread dump using jstack <pid>, e.g. jstack 15432 > myfile.txt

Gremlin on Neo4j 2.2.7

I need to incorporate the possibility of sending Gremlin scripts to my Neo4j 2.2.7 DB so I tried to install the thinkaurelius neo4j plugin by using one of the prebuilt releases.
Unfortunately I guess those releases were built for older Neo4j versions (2.1.6) and, as a result, I got this error when I tried to start Neo4j from my Windows machine with Java 8:
Starting Neo4j Server failed: javax.servlet.ServletException: org.neo4j.server.web.NeoServletContainer-e1dd969#ae4c07fc==org.neo4j.server.web.‌​NeoServletContainer,-1,false
To experiment a bit with the Gremlin language I tried to connect to my DB from the gremlin console (the DB wasn't used by any other process) but, when I run graph = Neo4jGraph.open('<path to my db>') the console stopped responding (there was no new prompt appearing).
Does anybody know what I could do to run some Gremlin script on my database?

Problems restarting Neo4j 1.8.1

I am using Neo4j version 1.8.1.
When I stopped the Neo4j service and started it up again, it will not respond at all.
I am unable to connect to the database using the Neo4j browser even though the service is running.
Any ideas/suggestions on how to troubleshoot this issue? It was working fine until I restarted the service.
Thanks
If you log Java's garbage collection to a file, you can tail this file to get a clue how busy neo4j is during startup, especially, as pointed out, following an unclean shutdown.
The Java startup option you need is:
-Xloggc:neo4j-gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps

Resources