Neo4j Desktop 1.0.15启动数据库失败：状态为‘KILLED’求助

Hey there, let's dig into why your Neo4j database is getting killed on startup. The "KILLED" status almost always points to a resource or configuration issue—here's how to diagnose and fix it step by step:

1. Check for Out-of-Memory (OOM) Issues (Most Common) #

The system's OOM killer often terminates Neo4j when it consumes too much memory.

• Open your system's resource monitor:
  • Windows: Task Manager → Performance tab
  • Mac: Activity Monitor → Memory tab
  • Linux: htop or top command
• Watch memory usage when you try to start the database—if it spikes to near full capacity, that's your culprit.
• Adjust Neo4j's memory settings:
  1. In Neo4j Desktop, click the ... next to your database → Open Folder → Configuration
  2. Edit the neo4j.conf file with these adjusted values (tweak based on your total system memory):

     dbms.memory.heap.initial_size=512m
     dbms.memory.heap.max_size=1G
     dbms.memory.pagecache.size=1G
     

     Rule of thumb: Heap max should be no more than half your system's available RAM; pagecache can be 1/4 to 1/2 of total RAM.

2. Verify File Permissions #

If Neo4j can't read/write its data or log files, it might get terminated unexpectedly:

• In Neo4j Desktop, go to ... → Open Folder → Data (and Logs)
• Windows: Right-click the folder → Properties → Security → Ensure your user account has "Full Control" permissions.
• Linux/Mac: Run this command in the terminal (replace <db-folder> with your database's root directory):

  chmod -R 755 <db-folder>
  

  (You can use 777 temporarily to test, but revert to 755 for security once it works.)

3. Check Java Version Compatibility #

Neo4j 3.3.1 requires Java 8 (Oracle JDK or OpenJDK)—newer Java versions can cause compatibility crashes:

• In Neo4j Desktop, click ... → Settings → Java Version
• Ensure the selected Java version is 8. If not, install Java 8 manually and add its path to Desktop's settings.

4. Dig Into Full Logs for Clues #

Your snippet is helpful, but full logs will reveal what happened right before the kill:

• Open ... → Open Folder → Logs
• Look at neo4j.log and debug.log for errors prior to the "KILLED" message:
  • "Address already in use": Port 7474/7687 is occupied—update neo4j.conf with new ports:

    dbms.connector.http.listen_address=:7475
    dbms.connector.bolt.listen_address=:7688
    

  • "Corrupted database": Your data files might be damaged—skip to step 5 for recovery.

5. Test With a Fresh Database #

To rule out corrupted data:

• Create a new blank database in Neo4j Desktop, using the same 3.3.1 version.
• If the new database starts successfully, your original database likely has corrupted files:
  1. Use the neo4j-admin dump command to back up the damaged database.
  2. Load the dump into a new database with neo4j-admin load.
  3. Run neo4j-admin check-consistency to scan for and fix data integrity issues.

6. Update Neo4j Desktop #

Version 1.0.15 is pretty outdated, and it might have known bugs that cause unexpected kills:

• Download the latest Neo4j Desktop version, install it, and try starting your database again.

内容的提问来源于stack exchange，提问作者Kirill Kiselev