Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

error accepting connection #16

Closed
i1u5 opened this issue Sep 13, 2019 · 2 comments
Closed

error accepting connection #16

i1u5 opened this issue Sep 13, 2019 · 2 comments
Labels
upstream upstream problems wontfix This will not be worked on

Comments

@i1u5
Copy link

i1u5 commented Sep 13, 2019

Every 50ms this error is logged :

...
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
2019-09-13 12:14:18 client.go:440: error accepting connection: read udp4 0.0.0.0:50007: wsarecvfrom: A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.
...
@boypt
Copy link
Owner

boypt commented Sep 16, 2019

It seems a race condition problem on windows.
I'll report it to upstrem.

@boypt
Copy link
Owner

boypt commented Sep 16, 2019

It turns out that this is an long existing problem on windows, and the author are unwilling to look deepth into it(for mostly it's working after all)

anacrolix/torrent#83

I added an option MuteEngineLog to hide such loggings. https://github.com/boypt/simple-torrent/wiki/Detailed-Explanation-of-config.json . will be available next version

@boypt boypt mentioned this issue Sep 20, 2019
@boypt boypt added wontfix This will not be worked on upstream upstream problems labels Sep 20, 2019
@boypt boypt closed this as completed Sep 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream upstream problems wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants