Closed ztheory closed 1 year ago
Thanks for the post. The log entry the output that was received from the update server verbatim to help with debugging any issues. It adds updateAvailable
boolean value to indicate what it detected which in this case is False
meaning that no update is available.
The update check is done only when you login to the DNS server web panel. It is actually triggered by the js on the client side to check if update is available. If there is an update available then you will see a notification in the GUI. There is no timer to check for update.
The frequent log entries you see are thus your attempts to login that frequently on the web panel or that you used F5 to refresh the entire web app which will lead the js to call the update check API.
Since the web app is a single page app, I would recommend that you click on the tabs on the GUI to refresh content in it, for example, clicking on the Dashboard tab will refresh the dashboard data. Some tabs do not refresh this way to preserve its view state but you will find a refresh option in there to refresh the data.
When starting the latest version, I see that the update checker still prints messages encouraging downloading the latest version.
Perhaps something like this simple message is expected if no update available:
Also, the updater checker runs quite often, at least initially after service start. Perhaps consider checking once during service start and then a few times per day afterwards to reduce the noisiness of the logs and the amount of web calls on your side.