bug: tcp/tcp.go:58 failed set keepalive period #2217
Comments
|
@SgtPooki is this something that's affecting your use of Kubo? Wondering if this can be closed as a works as intended |
|
I mean, trying to set keepalive on a nonexistent connection/stream seems like a bug that would have all kinds of implications that should be fixed, but kubo does “work” |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I can consistently repro the errors mentioned at
go-libp2p/p2p/transport/tcp/tcp.go
Lines 43 to 47 in b23d8b5
Note that for this issue, I am running this code directly from a
make buildversion of kubo on the master branch (updated today, so v0.19), but these errors also occur on my previously installed kubo v0.18running
GOLOG_LOG_LEVEL="error,core/server=debug,tcp-tpt=debug" cmd/ipfs/ipfs daemon-> https://ipfs.io/ipfs/QmXhxLbuVrNTiFdGzPXb68NDoiyrNFSfjQwNSD6GaQXFJUtroubleshooting
OS Restart
And after an OS level restart (@MarcoPolo recommendation): running
GOLOG_LOG_LEVEL="error,core/server=debug,tcp-tpt=debug" cmd/ipfs/ipfs daemon-> https://ipfs.io/ipfs/QmUd5zx5KiTw8A4WXSXdHVeM5WFNCHGEhS4ovuiL2zCJGqStill connected to peers?
`ipfs swarm peers | grep 47.108.58.134`
`cmd/ipfs/ipfs swarm peers | grep tcp`
Determine if peer is connected immediately on DEBUG/ERROR
In terminal1, run
GOLOG_LOG_LEVEL="error,core/server=debug,tcp-tpt=debug" cmd/ipfs/ipfs daemon 2>&1 | tee kubo-log.txtNOTE For the below commands, on my mac, I have GNU findutils installed via brew, and they're available with a
gprefix, so I can still use macOS/BSD available grep/sed/etc.. If you do not have the same setup, you may need to install gnutils (mac/non-GNU systems), remove thegprefix (linux/GNU native systems), or alter the commands (idk your life).In terminal2, run
tail -f kubo-log.txt | grep --line-buffered ERROR | gsed -E --unbuffered 's/^.*ERROR.*set tcp.*:.+->([^:]+):.*/\1/' | gxargs -L1 -I% sh -c 'ipfs swarm peers | grep %'. This tells you whether you're connected to the peer you received this error for by spitting out the multiaddr.In terminal3, run
tail -f kubo-log.txt | grep --line-buffered DEBUG | gsed -E --unbuffered 's/^.*DEBUG.*set tcp.*:.+->([^:]+):.*/\1/' | gxargs -L1 -I% sh -c 'ipfs swarm peers | grep %'. This tells you whether you're connected to the peer you received the DEBUG message for by spitting out the multiaddr.related
libp2p/go-tcp-transport#113
libp2p/go-tcp-transport#115
Version Information
The text was updated successfully, but these errors were encountered: