Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant login new instance, bloodhound-1 exited with code 137 #640

Closed
11 tasks
TheKevinWang opened this issue May 30, 2024 · 2 comments
Closed
11 tasks

Cant login new instance, bloodhound-1 exited with code 137 #640

TheKevinWang opened this issue May 30, 2024 · 2 comments
Labels
bug Something isn't working triage This issue requires triaging

Comments

@TheKevinWang
Copy link

TheKevinWang commented May 30, 2024

Description:

cant login new instance. bloodhound crashes.

bloodhound-1 exited with code 137

Component(s) Affected:

  • UI
  • API
  • Neo4j
  • PostgreSQL
  • Data Collector (SharpHound, AzureHound)
  • Other (tooling, documentation, etc.)

Steps to Reproduce:

setup new instance, docker compose up then using password supplied and admin as username it fails and then I get error blooodhound exit

Expected Behavior:

A description of what you expected to happen.

Actual Behavior:

A description of what actually happened.

Screenshots/Code Snippets/Sample Files:

If applicable, add screenshots, relevant code snippets, or sample files that help illustrate the issue.

Environment Information:

BloodHound: [BloodHound version or revision]

Collector: [SharpHound version / AzureHound version]

OS: Ubuntu ARM

Browser (if UI related): [browser name and version]

Node.js (if UI related: [Node.js version]

Go (if API related): [Go version]

Database (if persistence related): [Neo4j version / PostgreSQL version]

Docker (if using Docker): [docker version]

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:

  • I have searched the issue tracker to ensure this bug hasn't been reported before or is not already being addressed.
  • I have provided clear steps to reproduce the issue.
  • I have included relevant environment information details.
  • I have attached necessary supporting documents.
  • I have checked that any JSON files I am attempting to upload to BloodHound are valid.
@TheKevinWang TheKevinWang added bug Something isn't working triage This issue requires triaging labels May 30, 2024
@TheKevinWang TheKevinWang changed the title Cant login, bloodhound crash Cant login new instance, bloodhound-1 exited with code 137 May 30, 2024
@TheKevinWang
Copy link
Author

just have to use debug for now I guess

@StephenHinck
Copy link
Contributor

Docker exit code 137 means insufficient memory was supplied for the container to function. If you'd like to provide additional information such as fuller logs or system details we can take a look, but generally it means more resources (memory) are required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage This issue requires triaging
Projects
None yet
Development

No branches or pull requests

2 participants