cartography
cartography copied to clipboard
Neo4j Server not responding after syncing with Azure Subscription
Neo4j server is not responding after syncing with Azure Subscription.


After the sync stage the neo4j server is not able to load the graphs for azure. Have tried to restart the server several times but facing the same issue.
Neo4j version:3.5.0 OS: Windows 11 RAM:16GB
Hi there,
- Just double checking, does the sync complete successfully or does it fail with an error message? I'm wondering if you are trying to access the database while the sync job is going on.
- Also double checking, are you running the database on the same machine that is loading the data? (this is fine btw, just wanting to understand your configuration)
Hi,
Thanks for your response.
1.Yes the sync completes successfully, there is no error message. Also I am accessing database after completion of the sync. 2. I am using the same machine for loading and accessing the data.
This is an older issue, but I thought I'd ask a few questions to help troubleshoot your issue.
- How are you using neo4j? Are you using neo4j desktop or neo4j via docker using the included
docker-compose.yml
that is included with cartography? - Does neo4j work as expected after restarting it?
- Do you have any explicit memory parameters defined for your neo4j instance?
- What do your
debug.log
,neo4j.log
, andquery.log
log files look like? Are there any errors or other entries of interest in those log files?
Based on what you're describing and my own experience with neo4j and cartography, it sounds like you don't have enough memory allocated to neo4j.
It's weird that things would be frozen after the sync job.
I'm going to close this issue though since we are now on Neo4j 4.x and I'm hoping that once you upgrade to the new version you'll see better behavior. Please reopen the issue if this persists though.