Neo4j 桌面数据库无法启动，状态为“KILLED”

Question

Running Neo4j Desktop version 1.0.15. Trying to start DB causes the start fail:

Database failed to start: DB [database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a] 'v3.3.1' exited with status 'KILLED'. Check the logs

Major Log parts are below

2018-02-26 23:03:38.004+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@6411d3c8' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".

Caused by: java.lang.RuntimeException: Error starting org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory, C:\Users\kiril\AppData\Roaming\Neo4j Desktop\Application\neo4jDatabases\database-f8950fdd-6b5f-4fea-8c9f-e8457ee1da9a\installation-3.3.1\data\databases\graph.db

Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.backup.OnlineBackupKernelExtension@c6e0f32' was successfully initialized, but failed to start. Please see the attached cause exception "Connection timed out: connect".

    Suppressed: org.neo4j.kernel.lifecycle.LifecycleException: Exception during graceful attempt to stop partially started component. Please use non suppressed exception to see original component failure.

Caused by: java.io.IOException: Unable to establish loopback connection

Answer 1

It might be your neo4j was still running. I solved this problem by shutting down the database and restarting it.

Platform: Windows 10; Neo4j Desktop version: 1.1.13

Open a commend-line window and go to the directory of your neo4j database. run

bin\neo4j status 

to check the status of your database.

If it is running, run

bin\neo4j stop

to shut down your database. Then go back to the Neo4j Desktop, click the start button, and it could be symptom-free.

Answer 2

I had the same problem and the issue was resolved when I cloned the graph I was connecting. Thereafter, I could connect to the new graph without any problem.