Bug 12939 - Python exception "get_address KeyError: 'ipv4'" during DDNS update
Summary: Python exception "get_address KeyError: 'ipv4'" during DDNS update
Status: NEW
Alias: None
Product: DDNS Updater
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: x86_64 Unspecified
: - Unknown - - Unknown -
Assignee: Stefan Schantl
QA Contact: Michael Tremer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-24 11:22 UTC by Leo Hofmann
Modified: 2022-09-26 16:34 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leo Hofmann 2022-09-24 11:22:50 UTC
This error message appears in the IPFire system log after each DDNS update:

Dynamic DNS update for [mydomain_redacted].de (Joker.com Dynamic DNS) threw an unhandled exc eption: Traceback (most recent call last): File "/usr/lib/python3.10/site-pack ages/ddns/system.py", line 276, in get_address return self.__addresses[proto ] KeyError: 'ipv4' During handling of the above exception, another exception oc curred: Traceback (most recent call last): File "/usr/lib/python3.10/site-pac kages/ddns/__init__.py", line 178, in _update entry(force=force) File "/us r/lib/python3.10/site-packages/ddns/providers.py", line 157, in __call__ eli f self.has_failure or not self.requires_update: File "/usr/lib/python3.10/site -packages/ddns/providers.py", line 202, in requires_update if self.ip_addres s_changed(self.protocols): File "/usr/lib/python3.10/site-packages/ddns/provid ers.py", line 270, in ip_address_changed current_address = self.get_address( proto) File "/usr/lib/python3.10/site-packages/ddns/providers.py", line 329, i n get_address return self.core.system.get_

The DNS update is performed correctly, but DDNS fails after that and doesn't print the usual update status message. My provider is joker.com.

I have checked old logs and I think this issues appeared back in 03/2022 with core 164.
Comment 1 Adolf Belka 2022-09-24 12:18:14 UTC
I have the same message on the 1st of September with my DDNS provider. dynu.com

I have two DDNS domain names with them and both had that message. Nothing else since then as my IP from my ISP is static but new hardware triggered the update.

As with you the update was successfully executed.