Main process exited when get error response from DDNS server
mia0x75 opened this issue · 2 comments
mia0x75 commented
Error log:
# systemctl status inadyn
× inadyn.service - Internet Dynamic DNS Client
Loaded: loaded (/lib/systemd/system/inadyn.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Wed 2024-05-01 18:08:14 CST; 1 day 16h ago
Duration: 6.516s
Docs: man:inadyn
man:inadyn.conf
file:/usr/share/doc/inadyn/README.md
Main PID: 315335 (code=exited, status=48)
CPU: 1.532s
May 01 18:08:08 HLab inadyn[315335]: Update forced for alias sub-domain.duckdns.org, new IP# 2408:8256:3110:5800:f949:>
May 01 18:08:09 HLab inadyn[315335]: Fatal error in DDNS server response: DDNS server response not OK
May 01 18:08:11 HLab inadyn[315335]: Updating IPv6 cache for sub-domain.duckdns.org
May 01 18:08:14 HLab inadyn[315335]: Error response from DDNS server, exiting!
May 01 18:08:14 HLab inadyn[315335]: Error code 48: DDNS server response not OK
May 01 18:08:14 HLab systemd[1]: inadyn.service: Main process exited, code=exited, status=48/n/a
May 01 18:08:14 HLab systemd[1]: inadyn.service: Failed with result 'exit-code'.
May 01 18:08:14 HLab systemd[1]: inadyn.service: Consumed 1.532s CPU time.
troglobit commented
Yes, this is by design. The following lines tell something is not OK with the server:
May 01 18:08:09 HLab inadyn[315335]: Fatal error in DDNS server response: DDNS server response not OK
May 01 18:08:11 HLab inadyn[315335]: Updating IPv6 cache for sub-domain.duckdns.org
May 01 18:08:14 HLab inadyn[315335]: Error response from DDNS server, exiting!
May 01 18:08:14 HLab inadyn[315335]: Error code 48: DDNS server response not OK
I suggest you investigate the problem, e.g., by running with debug logs enabled to see what other information is returned from the server, or you can ignore the problem by running inadyn with --continue-on-error, as stated in the documentation.
troglobit commented
No response from reporter, closing.