Neo4j running on Ubuntu but cannot connect to database

I receive this error Neo.TransientError.Database.DatabaseUnavailable when trying to connect to the my Neo4j database. My neo4j.conf file is set up so dbms.default_database=pocgraph.db and the pocgraph.db directory that contains all my database files are sitting in the /var/lib/neo4j/data/databases directory.

There doesn't seem to be any resolution regarding this error online, so I'm hoping somebody here can point me in the right direction. I'm happy to provide any additional information or screenshots if necessary.

Thanks in advance!

Make sure you're actually connected to your neo4j instance first.

Try :server disconnect followed by :server connect and ensure you can actually contact the server and log in.

If you can get that far, then use :dbs to see what databases are available.

You may also want to switch to the system db and use show databases to see their status.

Hi Andrew, thanks for the response.

I'm already connected to the server and have logged in. For the database, it gives me the error ""An error occurred! Unable to start database with name pocgraph.db.""

Any ideas? I'm not sure what to do because when i did this with my local server all I had to do was point the default database to that directory.

Screenshot for reference:

I have the same problem.
Did you fix it?
Thanks a lot.

Can confirm that this happens in docker's image too while following this tutorial.
Trying to create a new database from a dump file it always appears broken when created and cannot be started with start database $dbname

try un-commenting in neo4j.conf and check again.

another possibility might be, your original database may have some plugins that are not compatible with neo4j 4.0 version.

1 Like

Didn't work for me unfortunately. I did put the in my neo4j.conf but am still getting "An error occurred! Unable to start database with name movies2." on the newly-created database and it is "Unavailable".
This is for the docker instance.

can you share neo4j.log ?

1 2020-06-30 16:20:18.244+0000 INFO [StoreCopy] ### Copy Data ###
2 2020-06-30 16:20:18.246+0000 INFO [StoreCopy] Source: /data/databases/movies
3 2020-06-30 16:20:18.246+0000 INFO [StoreCopy] Target: /data/databases/movies2
4 2020-06-30 16:20:18.247+0000 INFO [StoreCopy] Empty database created, will start importing readable data from the source.
5 2020-06-30 16:20:18.749+0000 INFO [o.n.i.b.ImportLogic] Import starting
6 2020-06-30 16:20:20.072+0000 INFO [o.n.i.b.ImportLogic] Import completed successfully, took 1s 318ms. Imported:
7 171 nodes
8 253 relationships
9 564 properties
10 2020-06-30 16:20:20.135+0000 INFO [StoreCopy] Import summary: Copying of 1026 records took 1 seconds (1026 rec/s). Unused Records 602 (58%) Removed Records 0 (0%)
11 2020-06-30 16:20:20.136+0000 INFO [StoreCopy] ### Extracting schema ###
12 2020-06-30 16:20:20.136+0000 INFO [StoreCopy] Trying to extract schema...
13 2020-06-30 16:20:20.145+0000 INFO [StoreCopy] ... found 0 schema definition. The following can be used to recreate the schema:
14 2020-06-30 16:20:20.149+0000 INFO [StoreCopy]

Nothing suspicios there that i see...

I have the same problem with the default database graph.db.
I am afraid the reason may be breaking the orders: I installed version 4.1 over 3.5. before studying carefully the manual, which says only 3.5 -> 4.0 is supported. :grimacing:
Is there any shorter solution, or is the only working way to install whole Neo4j from scratch to my Ubuntu developement workstation? Help!

Installing Community version 4.1 over 3.5 fails, as it is impossible to migrate the database directly to 4.1.

Solution to my problem is to remove the graph.db directory, and restart neo4j. Now it seems like I could try to rebuild the contents to the empty database. :sweat:

Hi Artie,

I experienced the same issue while I am working on the same tutorial.

I am using a neo4j:4.1.3-enterprise edition instance running in a docker container. The issue occurred both in neo4j Browser and cypher-shell running on Ubuntu 20.04 (see snapshots below).

I resolved the issue by stopping and starting the neo4j:4.1.3-enterprise instance in the docker container.