Inadyn 2.8.1 "freezes" and does not detect/apply updated IPs after some time since upgrade to jammy

[Benjamin Schmid]

I'm a long-term inadyn user. Since my upgrade from focal (which was von v1.99.x) to jammy (which is 2.8.1) inadyn has changed its modi operandi from "just works" to "needs manual attention every few days/weeks" since

Upstream redirected me to here, because v2.8.1 is outdated & unsupported by upstream. Current version as of now is 2.10.0. For reference upstream bug filed is: bug https://github.com/troglobit/inadyn/issues/399

Situation is plain simple. `/etc/inadyn.conf` reads like

```
# /etc/inadyn.conf

# How often the IP is checked. The value denotes seconds
period = 300
provider <email address hidden>:1 {
 …
}
provider <email address hidden>:2 {
 …
}
```

Situation: It fails to update my IP every once in a while. I assume that maybe the Freedns provide might be temporarily unavailable at the moment of the IP change detected; a manual `sudo systemctl restart inadyn` immediately mends the situation.

Here the log. See my manual restart immediately caused an successful update!

```
Nov 27 12:38:56 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.127
Nov 27 12:38:56 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.127
Nov 27 12:38:56 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.127
Nov 27 12:38:56 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.127
Nov 27 12:38:56 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.127
Nov 28 05:18:48 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.140
Nov 28 05:18:48 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.140
Nov 28 05:18:48 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.140
Nov 28 05:18:48 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.140
Nov 28 05:18:48 neptun inadyn[2178777]: Update needed for alias ###, new IP# ###.140

[restart]

Nov 29 09:49:30 neptun systemd[1]: Stopping LSB: DynDNS client...
Nov 29 09:49:30 neptun inadyn[3369480]: * Stopping DynDNS client inadyn
Nov 29 09:50:00 neptun inadyn[3369480]: ...done.
Nov 29 09:50:00 neptun systemd[1]: inadyn.service: Deactivated successfully.
Nov 29 09:50:00 neptun systemd[1]: Stopped LSB: DynDNS client.
Nov 29 09:50:00 neptun systemd[1]: inadyn.service: Consumed 54.305s CPU time.
Nov 29 09:50:00 neptun systemd[1]: Starting LSB: DynDNS client...
Nov 29 09:50:00 neptun inadyn[3370340]: * Starting DynDNS client inadyn
Nov 29 09:50:00 neptun inadyn[3370340]: ...done.
Nov 29 09:50:00 neptun systemd[1]: Started LSB: DynDNS client.
Nov 29 09:50:00 neptun inadyn[3370346]: In-a-dyn version 2.8.1 -- Dynamic DNS update client.
Nov 29 09:50:01 neptun inadyn[3370346]: Update forced for alias ###, new IP# ###.207
Nov 29 09:50:01 neptun inadyn[3370346]: Update forced for alias ###, new IP# ###.207
Nov 29 09:50:01 neptun inadyn[3370346]: Update forced for alias ###, new IP# ###.207
Nov 29 09:50:01 neptun inadyn[3370346]: Update forced for alias ###, new IP# ###.207
Nov 29 09:50:01 neptun inadyn[3370346]: Update forced for alias ###, new IP# ###.207
```

I could now add a cronjob to restart the daemon regularily. But IMHO this would miss the point of inadyn, right?