Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Odd error once in a while (wsarecvfrom) #320

Open
csm10495 opened this issue Nov 2, 2022 · 3 comments
Open

Odd error once in a while (wsarecvfrom) #320

csm10495 opened this issue Nov 2, 2022 · 3 comments

Comments

@csm10495
Copy link

csm10495 commented Nov 2, 2022

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.

@csm10495 csm10495 changed the title Odd error once in a while Odd error once in a while (wsarecvfrom) Nov 2, 2022
@csm10495
Copy link
Author

csm10495 commented 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.

@webprofusion-chrisc
Copy link
Contributor

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.

@csm10495
Copy link
Author

csm10495 commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants