[GH-ISSUE #320] Odd error once in a while (wsarecvfrom) #174

New issue

Open

opened 2026-03-13 16:02:29 +03:00 by kerem · 3 comments

kerem commented

2026-03-13 16:02:29 +03:00

Owner

Originally created by @csm10495 on GitHub (Nov 2, 2022).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/320

Hey folks,

Once in a long while I get an error like this on Win10:

time="2022-11-01T22:46:15-07:00" level=fatal msg="read udp [::]:53: 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."

Then the process exits.

Any ideas about how we can not crash in this case? I have no idea what sends what message that leads to the crash.

Originally created by @csm10495 on GitHub (Nov 2, 2022). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/320 Hey folks, Once in a long while I get an error like this on Win10: ``` time="2022-11-01T22:46:15-07:00" level=fatal msg="read udp [::]:53: 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." ``` Then the process exits. Any ideas about how we can not crash in this case? I have no idea what sends what message that leads to the crash.

kerem commented

2026-03-13 16:02:35 +03:00

Author

Owner

@csm10495 commented on GitHub (Nov 2, 2022):

I'm not quite sure what version of acme-dns I'm using.. there isn't a --version or something like that to check as far as I can tell.

@csm10495 commented on GitHub (Nov 2, 2022): I'm not quite sure what version of acme-dns I'm using.. there isn't a --version or something like that to check as far as I can tell.

kerem commented

2026-03-13 16:02:40 +03:00

Author

Owner

@webprofusion-chrisc commented on GitHub (Nov 2, 2022):

You would have to had to build acme-dns yourself or get someone to build it for you (last I checked it doesn't build without minor modification), there is no prebuilt version for Windows. That error is a standard windows sockets error and is not controlled by acme-dns, that said the exception should generally be caught and logged then processing should resume as public DNS is a very hostile place. If you have acme-dns running as a service you could just configure it to auto restart on failure.

@webprofusion-chrisc commented on GitHub (Nov 2, 2022): You would have to had to build acme-dns yourself or get someone to build it for you (last I checked it doesn't build without minor modification), there is no prebuilt version for Windows. That error is a standard windows sockets error and is not controlled by acme-dns, that said the exception should generally be caught and logged then processing should resume as public DNS is a very hostile place. If you have acme-dns running as a service you could just configure it to auto restart on failure.

kerem commented

2026-03-13 16:02:45 +03:00

Author

Owner

@csm10495 commented on GitHub (Nov 2, 2022):

I must have done that then.. sorry it's been a while.

I have it setup to auto restart on crash, just figured maybe we could somehow avoid the crash to begin with.

Though if Windows isn't really supported to begin with: sorry for the trouble and feel free to close this out.

@csm10495 commented on GitHub (Nov 2, 2022): I must have done that then.. sorry it's been a while. I have it setup to auto restart on crash, just figured maybe we could somehow avoid the crash to begin with. Though if Windows isn't really supported to begin with: sorry for the trouble and feel free to close this out.