-
-
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
v0.9.0 panics on OpenBSD #8211
Comments
The error from the keepalive bit seems to be from https://github.com/golang/go/blob/2ebe77a2fda1ee9ff6fd9a3e08933ad1ebaea039/src/net/tcpsockopt_openbsd.go#L13 So that might not be the issue. |
Agreed, this is definitely not related to the socket option. The problem is in https://github.com/multiformats/go-multiaddr/blob/2f4fae4104af2df7036afcdd93d2075845e68ed0/net/net.go#L234-L267. Now I'm not sure why a |
I figure this is more of a question for this thread: Given libp2p/go-tcp-transport#80 (comment)
It looks like go-tcp-transport just sets the keepalive to 30 seconds. I maintain the port of go-ipfs on OpenBSD and we have a doc that makes a number of tuning recommendations - Would recommending that users set their keepalive to 30 seconds be worth mentioning? |
We probably should keep this open until the change is bubbled up here. |
@qbit depending on the default value that OpenBSD uses, it might or might not be worth it. |
Version information:
go-ipfs version: 0.9.0
Repo version: 11
System version: amd64/openbsd
Golang version: go1.16.5
Description:
After running for a period of time,
ipfs daemon
panics with the following:The daemon also produces a plethora of this error while running:
The text was updated successfully, but these errors were encountered: