Update to 24.7.1: dyndns not starting after reboot?

[bringha]

G'day,

Updated just to 24.7.1 which ran smooth as usual. Time to say a big thank you to all who made this happen - Great job again!!!

A (small) heads up I would like to bring to your attention which is the dyndns service resp. GUI behavior once the system reboots after update.

I am running ddclient with native backend and my dyndns update runs in two steps, one for ipv4 and one for ipv6. In between, my provider (dedyn.io) demands for a ~5 min pause and it is throttling the update requests to this interval. Already after the 24.7 (and now also 24.7.1) upgrade reboot, I am running then in a kind of (race) condition showing a very inconsistent picture about the state of the dyndns service. Reproducible, after the update reboot

• the Dashboard widget shows dyndns as 'not running', ps says it runs. Dashboard value is not changing without manual interaction
• the dyndns services page shows the correct new ipv6 address and the old ipv4 address
• the interface overview widget shows for WAN the correct new ipv4 address and ipv6 address

So, the state of internet connection reads somewhat confusing after the update ....

When manually restarting dyndns service on the dashboard service widget, nothing changes
When manually stopping dyndns and starting on the configuration page, the widget on the dashboard gets then the correct new ipv4 and ipv6 addresses; on the service configuration page, still the old ipv4 address is shown.
When manually restarting dyndns for a second time, everything is OK again.

So it takes in my case up to 10 min and two manual interactions until GUI values for WAN addresses are shown consistent to the reality.

I am aware that a fix of this is somewhat shaky as the service restart behavior is different from system to system
but perhaps over time, some optimization could be considered for this.

Br br

[franco]

Hey,

The widget only shows the status, which means this has been going on for a while.

For now I'd suggest concentrating on:

> the Dashboard widget shows dyndns as 'not running', ps says it runs. Dashboard value is not changing without manual interaction

The PID value is wrong, but the question is what (re)started the Python script to end up clashing with its PID file.


Cheers,
Franco