Ipfs seems to produce heaps of errors in system.log

Whenever I start the ipfs daemon, system.log receives an error like 2017-07-16 21:01:40,000 kernel[0]: tcp_connect: inp=0x94578359a53c096b err=EADDRINUSE almost once every second. Not sure what’s behind it. Anyone know?

OS X : 10.11.6
go-ipfs version: 0.4.10-4679f80
Repo version: 5
System version: amd64/darwin
Golang version: go1.8.3
Running via VPN (udp 443)

go-ipfs tries using REUSEPORT for NAT traversal.
You can try disabling it by starting the daemon with IPFS_REUSEPORT=false environment variable.

I don’t have much of an idea why it would be spamming it.

1 Like

That seems to have worked. Thank you. Used export IPFS_REUSEPORT=false ; ipfs daemon --writable … will keep monitoring. But isn’t IPFS_REUSEPORT=true the default ipfs behavior? Will false have any unwanted consequences? At any rate, as for the log spam, that would be a Darwin kernel issue, not an ipfs bug, right? EDIT: or maybe it is ipfs after all, and it’s telling the system to log these events. (?) If so, it should be rectified, I guess.