naveenatwork
commented
2 weeks ago bloodhound-1 | {"level":"warn","time":"2024-09-13T06:58:49.524922919Z","message":"Unable to fetch migration data from graph: not found"} bloodhound-1 | {"level":"info","time":"2024-09-13T06:58:49.526017167Z","message":"This is a new graph database. Creating a migration entry for GraphDB version v5.15.0"} bloodhound-1 | {"level":"error","time":"2024-09-13T06:58:49.615194995Z","message":"Invalid neo4j configuration supplied; returning default values"}
Description:
When I am trying to run the container image using the instructions provided in the documentation I get an error "Invalid neo4j configuration supplied; returning default values". https://support.bloodhoundenterprise.io/hc/en-us/articles/17468450058267-Install-BloodHound-Community-Edition-with-Docker-Compose
Are you intending to fix this bug? no
Component(s) Affected:
Steps to Reproduce:
Follow the instructions by downloading the docker compose, and run the container. (https://support.bloodhoundenterprise.io/hc/en-us/articles/17468450058267-Install-BloodHound-Community-Edition-with-Docker-Compose)
Expected Behavior:
User login should be successful with no error in the docker logs
Actual Behavior:
User login failed and the bloodhound-1 service stops with error "bloodhound-1 exited with code 137" When looking at the details of the logs I can see message ""message":"Invalid neo4j configuration supplied; returning default values"}" I tried to change the image version of the bloodhound to 5.14 from latest but it is the same error. Updating the Neo4j configuration file also didn't help.
Screenshots/Code Snippets/Sample Files:
If applicable, add screenshots, relevant code snippets, or sample files that help illustrate the issue.
Environment Information:
BloodHound: latest, 5.14, tried in both version Collector: N/A, couldn't login to bloodhound
OS: MAC OS 14.5
Browser (if UI related): chrome
Node.js (if UI related: [Node.js version]
Go (if API related): [Go version]
Database (if persistence related): Neo4j 4.4
Docker (if using Docker): Docker version 26.1.0-rd, build cca8e72
Additional Information:
Any additional context or information that might be helpful in understanding and diagnosing the issue.
Potential Solution (optional):
If you have any ideas about what might be causing the issue or how it could be fixed, you can share them here.
Related Issues:
If you've found related issues in the project's issue tracker, mention them here.
Contributor Checklist: