Marcs Updater
There have been some reports about issues with the Updater not updating anymore. Please try the latest beta version and switch to another IP Check provider instead of the previous default dnsomatic.com. For some reason they are rate-limiting the number of requests to their service. The new IP Check provider selection allows you to choose another provider in such cases. You can test the functionality with the new "Test" panel.
If you want to add a custom provider to the unstable testing version, store a JSON file like the following under %PROGRAMDATA%\Marcs Updater\ServiceProviders\dyndns.json:
{
"name": "DynDNS.org (Test)",
"endpoint": "https://members.dyndns.org/nic/update",
"method": "GET",
"queryString": "hostname={HOSTNAME}&myip={MYIP}",
"dataPayload": "",
"defaults": {
"username": "test",
"password": "test",
"hostname": "test1.customtest.dyndns.org"
}
}Supported query and payload tags are {USERNAME}, {PASSWORD}, {HOSTNAME} and {MYIP}. Restart the background service and foreground application to apply any changes.
Issue created on
Posted on
Malte wrote:
Marc, some time ago, I described that the updater on my PC takes 30-40 minutes to update, although I had selected an update interval of 5 minutes. After many unsuccessful experiments, I now decided to start all services on my XP SP3 that were set to "manual" and that did not run. Et voilà: The updater updated as is should.
So, there is probably one of these 30 services that should be set to "automatic". I checked each with a list of default settings, but they looked OK. Now, before I switch on all of these services in turn and wait 5 minutes, do you have an idea what dependencies your service has? Or maybe your servcive could take care that all required services are started?
Posted on
Malte wrote:
After further testing, I have to alter my comment a bit. The issue is somewhat heisenbugish of nature. Starting other processes does not always trigger the correct behaviour of the updater process. What I can say now is the following:
1. When I start the PC, the updater process gets started, but does not do its job (to update).
2. When I stop and restart the updater process, the IP gets updated immediately. When I then change my router's IP, it gets properly updated after 5 minutes.
Can you make any sense of that? Am I the only one having this problem? My PCs are fairly standard: XP SP3, Laptop with WLAN (tried LAN, too, with similar results), only few additional programs that might interfere.
Posted on
Marc wrote:
I will look into this issue in detail. Thanks for all the information. I hope to be able to look into this soon.
Posted on
Guest wrote:
I wonder if it has anything to do with what the PC thinks it's IP is when the updater attempts to update (right after startup) Perhaps, due to process priority and order of system boot-up procedures, the updater runs before ipconfig has finished starting/configuring. I know that the network connection "stuff" on my system seems to take a couple long minutes...
Just a guess.
Posted on
Malte wrote:
Yes, that was my thought, too. I added a dependency in the registry for the updater service, so that it depends on "Tcpip", but that did not solve the problem. I tried other dependencies, too, but did not succeed. Anyway, I would have hoped that the updater would do a next try 5 minutes after startup (the update interval was set to 5 minutes), but it takes much longer until the first update happens.
Posted on
Marc wrote:
Could you try adding LanmanServer and LanmanWorkstation as a dependency for the service? Normally the updater automatically checks for a new IP as soon as anything inside the registry key SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces changes, but it might not get the first change. It automatically issues a check on launch, but that might be too early in your case.