-
Notifications
You must be signed in to change notification settings - Fork 380
Closed
Description
It works, but I noticed it grabbing an abnormal amount of CPU every few seconds and I looked at the logs and found it's basically attempting to update every few seconds. I thought there was a min of 5 minutes imposed (which is still way faster than I need) but would be reasonable.
Here is the log:
...
FAILED: updating mydomain.duckdns.org: Server said: '0'
WARNING: skipping update of mydomain.duckdns.org from <nothing> to 123.456.789.101.
WARNING: last updated <never> but last attempt on Mon Jan 30 23:34:10 2023 failed.
WARNING: Wait at least 5 minutes between update attempts.
FAILED: updating mydomain.duckdns.org: Server said: '0'
WARNING: skipping update of mydomain.duckdns.org from <nothing> to 123.456.789.101.
WARNING: last updated <never> but last attempt on Mon Jan 30 23:34:12 2023 failed.
WARNING: Wait at least 5 minutes between update attempts.
FAILED: updating mydomain.duckdns.org: Server said: '0'
WARNING: skipping update of mydomain.duckdns.org from <nothing> to 123.456.789.101.
WARNING: last updated <never> but last attempt on Mon Jan 30 23:34:15 2023 failed.
WARNING: Wait at least 5 minutes between update attempts.
FAILED: updating mydomain.duckdns.org: Server said: '0'
WARNING: skipping update of mydomain.duckdns.org from <nothing> to 123.456.789.101.
WARNING: last updated <never> but last attempt on Mon Jan 30 23:34:18 2023 failed.
WARNING: Wait at least 5 minutes between update attempts.
FAILED: updating mydomain.duckdns.org: Server said: '0'
WARNING: skipping update of mydomain.duckdns.org from <nothing> to 123.456.789.101.
WARNING: last updated <never> but last attempt on Mon Jan 30 23:34:20 2023 failed.
WARNING: Wait at least 5 minutes between update attempts.
...
Here is my config:
use=web, \
web=checkip.dyndns.org, \
protocol=duckdns, \
password=bf34128d-d5c6-4111-bf3f-6260d8aad49c \
domain.duckdns.org
Here is its section in the docker-compose:
...
ddns:
container_name: ddns
image: linuxserver/ddclient:latest # https://hub.docker.com/r/linuxserver/ddclient
networks:
vpn:
ipv4_address: 10.1.0.11
environment:
PUID: 1001
PGID: 1001
TZ: America/New_York
volumes:
- ./ddclient.conf:/config/ddclient.conf
restart: unless-stopped
...
I was looking for a way to specify in the config a minimum polling period, but all docs say that it should never run like this. Any ideas how I can tell it that this is not okay?
Metadata
Metadata
Assignees
Labels
No labels