"
I may have found something helpful in my case.
For EasyDNS, anyways, the problem may be that ddclient as configured in OPNsense uses a min interval of 5 minutes and EasyDNS API complains back that it wants a minimum interval of 10 minutes. I'm not sure what started the first string of errors in the very first place, but now it seems stuck in a loop where every 5 minutes it tries to update because the previous failed, and the failure may be due to the unknown status (unknown to ddclient anyways) that I should only send updates every 10 minutes or more.
The logs show attempts and failures with "unknown status" every 5 minutes. So it considers that a failure and tries again in 5 minutes, but the "failure" is due to a message that ddclient is trying too often.
Could a knob be added to the opnsense config screen to set the minimum interval / max frequency? Is this the "-daemon <delay>" option?
EDIT: was overlooking the interval setting on the general tab. Changed that to '700' in my case to continue testing. Still believe that ddclient should understand the TOO FREQ error - leaving issue in place.
logging from running 'ddclient -V -force' manually:
The setting of <delay> from within opnsense may be a useful option, and workaround for a few problems including this one. I'm guessing that the real problem here is that ddclient needs to be made to understand a "TOO FREQ" response from my particular API? Of course whatever originally set it into this loop is still unknown.
EDIT: Issue #525 opened
For EasyDNS, anyways, the problem may be that ddclient as configured in OPNsense uses a min interval of 5 minutes and EasyDNS API complains back that it wants a minimum interval of 10 minutes. I'm not sure what started the first string of errors in the very first place, but now it seems stuck in a loop where every 5 minutes it tries to update because the previous failed, and the failure may be due to the unknown status (unknown to ddclient anyways) that I should only send updates every 10 minutes or more.
The logs show attempts and failures with "unknown status" every 5 minutes. So it considers that a failure and tries again in 5 minutes, but the "failure" is due to a message that ddclient is trying too often.
EDIT: was overlooking the interval setting on the general tab. Changed that to '700' in my case to continue testing. Still believe that ddclient should understand the TOO FREQ error - leaving issue in place.
Code Select
<29>1 2023-03-10T23:45:11-05:00 OPNplenum ddclient[16714] 31563 - [meta sequenceId="1"] FAILED: updating <REDACTED1>: unexpected status (9d)
<29>1 2023-03-10T23:45:11-05:00 OPNplenum ddclient[16714] 32911 - [meta sequenceId="2"] FAILED: updating <REDACTED2>: unexpected status (9e)
<29>1 2023-03-10T23:50:12-05:00 OPNplenum ddclient[16714] 82372 - [meta sequenceId="1"] FAILED: updating <REDACTED1>: unexpected status (bb)
<29>1 2023-03-10T23:50:12-05:00 OPNplenum ddclient[16714] 83451 - [meta sequenceId="2"] FAILED: updating <REDACTED2>: unexpected status (ba)
<29>1 2023-03-10T23:55:12-05:00 OPNplenum ddclient[16714] 18466 - [meta sequenceId="1"] FAILED: updating <REDACTED1>: unexpected status (9d)
<29>1 2023-03-10T23:55:12-05:00 OPNplenumn ddclient[16714] 19477 - [meta sequenceId="2"] FAILED: updating <REDACTED2>: unexpected status (9e)
logging from running 'ddclient -V -force' manually:
Code Select
RECEIVE: HTTP/1.1 200 OK
RECEIVE: Date: Sat, 11 Mar 2023 12:53:52 GMT
RECEIVE: Server: Apache
RECEIVE: Expires: Thu, 19 Nov 1981 08:52:00 GMT
RECEIVE: Cache-Control: no-store, no-cache, must-revalidate
RECEIVE: Pragma: no-cache
RECEIVE: Set-Cookie: easydns_language=en_US; expires=Sun, 10-Mar-2024 12:53:52 GMT; Max-Age=31536000; path=/
RECEIVE: Set-Cookie: EasyDNS_SID=REDACTED; expires=Sat, 11-Mar-2023 14:53:52 GMT; Max-Age=7200; path=/; domain=api.cp.easydns.com; secure; HttpOnly
RECEIVE: X-Frame-Options: sameorigin
RECEIVE: Content-Security-Policy: frame-ancestors 'self';
RECEIVE: Vary: Accept-Encoding
RECEIVE: Connection: close
RECEIVE: Transfer-Encoding: chunked
RECEIVE: Content-Type: text/html; charset=UTF-8
RECEIVE:
RECEIVE: bb
RECEIVE: <HTML><BODY><FONT FACE="sans-serif" SIZE="-1">TOO_FREQ<br />
RECEIVE: <hr noshade size="1">
RECEIVE: Increase your time between updates for <REDACTED> to 600 seconds or more.<br />
RECEIVE: </FONT></BODY></HTML>
RECEIVE: 0
The setting of <delay> from within opnsense may be a useful option, and workaround for a few problems including this one. I'm guessing that the real problem here is that ddclient needs to be made to understand a "TOO FREQ" response from my particular API? Of course whatever originally set it into this loop is still unknown.
EDIT: Issue #525 opened
