-
Notifications
You must be signed in to change notification settings - Fork 636
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
Crash with invalid DNS server #688
Comments
@lopsided98 It might be caused by NtpClient library used in espurna, which periodicaly checks ntp server availability. Does your build use ntp and is ntp server stored as domain name (not as ip)? This can be related to #682 (comment) |
I am using a NTP server with a domain name. I just got a chance to update to the official build of 1.12.6, and the problem still exists. |
The problem goes away if I use an IP address of an NTP server. @mcspr I tried the commit you suggested (which seems to be a different branch that requires async UDP), and it had the same problem. I also tried the develop and master versions of NtpClient, as well as different versions of the Arduino core, and they all exhibited the bug. |
May I know what NTP server you are using (the domain name)? In general, using the ntp pool (pool.ntp.org) should be enough. |
I was using |
You said you are using static IP, then you have defined an static DNS too, right? Is that pointing to your local server? |
Yes, normally I use a local DNS server (and everything works fine unless the DNS server isn't running). For a while I was using Google's DNS as another workaround, which also works. |
So the problem is that it crashes when the DNS server is not available. It should just fail to not using NTP at all... |
Duplicate of #1617 |
Espurna crashes when an non-functioning DNS server is specified. I run a DNS server on my local network, which is used by Espurna. Espurna is using a static IP, not DHCP. I took the DNS server down for maintenance and I noticed that my device stopped working (Tonbux Powerstrip02, running the latest dev branch). The crash seems to be triggered by loading the web interface.
Here is the crash dump:
and the decoded stack trace:
It looks like this might not be an Espurna specific problem, but I'm not sure how to debug it further.
The text was updated successfully, but these errors were encountered: