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

v0.21.1 crash looping on docker #845

Open
kw1knode opened this issue Jan 12, 2024 · 6 comments
Open

v0.21.1 crash looping on docker #845

kw1knode opened this issue Jan 12, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@kw1knode
Copy link
Contributor

No logs to report, container not able to start.

@alex-pakalniskis alex-pakalniskis added the bug Something isn't working label Jan 12, 2024
@fordN
Copy link
Contributor

fordN commented Jan 12, 2024

Both indexer-service and indexer-agent?

@kw1knode
Copy link
Contributor Author

Both indexer-service and indexer-agent?

I only had issues with service, but some reports of both.

@fordN
Copy link
Contributor

fordN commented Jan 12, 2024

Ok, that's what I'm seeing too. I'm able to reproduce on indexer-service; I'm getting an odd segfault error that doesn't produce any logs.

I'm bisecting back through git commit history to identify the issue now.

@madnadyka
Copy link

madnadyka commented Jan 15, 2024

Hello! Have same issue with indexer-service, network arbitrum-sepolia, trying to start with docker

@lincolncpp
Copy link

Same issue with indexer-service:

  • Docker container exited without logs
  • segfault when running from npm packages (@graphprotocol/indexer-service@0.21.1)
  • segfault when running from source (branch main)

@rafael-protofire
Copy link

same issue here with indexer-service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🐛 Bug reports
Development

No branches or pull requests

6 participants