-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
docker ipfs auto stoped but dont know why,how can i get the detail logs? #6557
Comments
It will also eixt if you do nothing. in ssh run |
It's probably running out of memory. Your issue is:
You're running as a public relay and telling the entire network to use you as a relay. Additionally, your connection limit is set to 900. That means you're repeatedly disconnecting, reconnecting, disconnecting, etc. which is probably trashing your CPU. I'd:
|
thanks. ps: |
It's mostly a protocol issue. Nodes don't ask relays before they start advertising that they should be contacted via that relay. There was some discussion in libp2p/go-libp2p-circuit#67 but that didn't go anywhere. For now, relays can only reasonably run on very large machines. Note: setting lower connection limits will make this worse as peers will repeatedly try to reconnect to the relay. |
This ipfs has been running for a long time with aws s3.
but recently, it always auto stoped.
docker log
docker ipfs logs
:and the config
i don't know why it stoped.
can i get some more detailed error log.
the aws s3 now has 300G+ files and 310W+ fragment files.
The text was updated successfully, but these errors were encountered: