TCP KEEPALIVE and SETSOCKOPT: INVALID ARGUMENT

At this moment I am running several IPFS websites and they all work fine, however, I keep receiving an ERROR message (see screenshot) over and over again. I tried to lookup how to keep the TCP alive or solutions regarding the setsockopt but unfortunately I am not experienced enough to find a solution for this problem. I hope someone knows which steps (as exact as possible) I should take to resolve the issue.

Thanks in advance!!

1 Like

Can you give us more info on your system and ipfs node (OS, arch, go-ipfs version, etc…)

Heey @fusetim thank you for your reply. I am sorry I forgot to mention this:

Operating software: Mac OS Mojave, version 10.14.6
go-ipfs version: 0.9.0
System version: amd64/darwin
Golang version: go1.16.5

Unfortunately I don’t know how to find the architecture type but if it is necessary please let me know
how to find it

No worry you just gave it: amd64/darwin

1 Like

Interesting, I wonder if other OSX users see these errors. Did they just start with v0.9.0? If so, what version did you have before you saw these messages?

Heey, @Discordian before I had these messages I had version 0.6.0. Maybe it is just my computer, that I have certain settings that I don’t know off that create those issues.

1 Like

This change was introduced in 0.9.0. We enabled TCP keep alive to more quickly detect stalled connections.

It sounds like the connection may be dead at this point? We should probably just ignore that error and move on.

1 Like
1 Like