-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
Tweak NTP error reporting #2125
base: development
Are you sure you want to change the base?
Conversation
Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: |
This pull request has been mentioned on Pi-hole Userspace. There might be relevant details there: |
Working well for me. No issues in two days of testing! EDIT: See below, spoke too soon. |
There is an reported crash on with this branch |
This crash happened somewhere in the DNS resolver thread, not code that is even remotely touched by this PR. So this may be 100% coincidence. |
Signed-off-by: DL6ER <[email protected]>
Nonetheless, I went through the resolver code line-by-line and added quite a few extra checks wherever possible. I don't think there was an issue but now everything should be even better because we are not believing in large enough buffers but actually check that before working on them. |
Signed-off-by: DL6ER <[email protected]>
Signed-off-by: DL6ER <[email protected]>
…ERROR message from showing up in the logs Signed-off-by: DL6ER <[email protected]>
…c was sufficiently far off (> 0.1 s) to postpone the start of the embedded NTP server Signed-off-by: DL6ER <[email protected]>
…pile-time constant) and enlarge retry interval to 10 minutes (or ntp.sync.interval if smaller) Signed-off-by: DL6ER <[email protected]>
Signed-off-by: Dominik <[email protected]>
This branch has been working very well for me. I haven't seen any issues since the last commits. |
What does this implement/fix?
This PR has three changes regarding the NTP implementation:
If there was a timeout, we log the used IP address in addition to the host name. This may be useful to determine if only specific servers cause timeouts (as suggested by @deHakkelaar)
Do not issue double warnings when receiving NTP replies fails, e.g. skip the first of these two:
In case the upstream server sends a "kiss code", we interpret and show it (e.g. "access denied" when authentication is required or "rate exceeded" when querying too often). Before, we simply logged
in such a case.
Related issue or feature (if applicable): N/A
Pull request in docs with documentation (if applicable): N/A
By submitting this pull request, I confirm the following:
git rebase
)Checklist:
developmental
branch.