ddns watchdog restarting every 30 seconds

[jorhett]

Watchdog is starting DDNS every 30 seconds.

Dec  6 04:38:09 watchdog: start ddns.
Dec  6 04:38:09 ddns: update CUSTOM , wan_unit 0
Dec  6 04:38:09 ddns: Clear ddns cache.
Dec  6 04:38:09 custom_script: Running /jffs/scripts/ddns-start (args: 200.82.19.61)
Dec  6 04:38:10 ddns: Completed custom ddns update
Dec  6 04:38:39 watchdog: start ddns.
Dec  6 04:38:39 ddns: update CUSTOM , wan_unit 0
Dec  6 04:38:39 ddns: Clear ddns cache.
Dec  6 04:38:39 custom_script: Running /jffs/scripts/ddns-start (args: 200.82.19.61)
Dec  6 04:38:40 ddns: Completed custom ddns update
Dec  6 04:39:09 watchdog: start ddns.
Dec  6 04:39:09 ddns: update CUSTOM , wan_unit 0
Dec  6 04:39:09 ddns: Clear ddns cache.
Dec  6 04:39:09 custom_script: Running /jffs/scripts/ddns-start (args: 200.82.19.61)
Dec  6 04:39:10 ddns: Completed custom ddns update

(that's not my real IP)

I've confirmed my ddns-start script is working, and also confirmed that it's setting the completed variable:

router:/jffs/scripts# nvram get ddns_updated
1

Looking at other threads, the only thing I've found is that ddns_ipaddr is not set

router:/jffs/scripts# nvram show 2>/dev/null | grep -E "ddns_ipaddr=|wan0_ipaddr=|wan0_realip_ip="
wan0_ipaddr=200.82.19.61
routwan0_realip_ip=200.82.19.61

Model RT-AX86U running 3004.388.5

 

[Ripshod]

What scripts do you have installed? I don't find /jffs/scripts/ddns-start on my router. Is this only since updating to 388.5?
It's possible a script needs updating, or is no longer compatible, or you need a factory reset and manual setup.

Edit: RT-AC86U running 388.5?

 

[Rik Stigter]

Watchdog is starting DDNS every 30 seconds.

Dec  6 04:38:09 watchdog: start ddns.
Dec  6 04:38:09 ddns: update CUSTOM , wan_unit 0
Dec  6 04:38:09 ddns: Clear ddns cache.
Dec  6 04:38:09 custom_script: Running /jffs/scripts/ddns-start (args: 200.82.19.61)
Dec  6 04:38:10 ddns: Completed custom ddns update
Dec  6 04:38:39 watchdog: start ddns.
Dec  6 04:38:39 ddns: update CUSTOM , wan_unit 0
Dec  6 04:38:39 ddns: Clear ddns cache.
Dec  6 04:38:39 custom_script: Running /jffs/scripts/ddns-start (args: 200.82.19.61)
Dec  6 04:38:40 ddns: Completed custom ddns update
Dec  6 04:39:09 watchdog: start ddns.
Dec  6 04:39:09 ddns: update CUSTOM , wan_unit 0
Dec  6 04:39:09 ddns: Clear ddns cache.
Dec  6 04:39:09 custom_script: Running /jffs/scripts/ddns-start (args: 200.82.19.61)
Dec  6 04:39:10 ddns: Completed custom ddns update

(that's not my real IP)

I've confirmed my ddns-start script is working, and also confirmed that it's setting the completed variable:

router:/jffs/scripts# nvram get ddns_updated
1

Looking at other threads, the only thing I've found is that ddns_ipaddr is not set

router:/jffs/scripts# nvram show 2>/dev/null | grep -E "ddns_ipaddr=|wan0_ipaddr=|wan0_realip_ip="
wan0_ipaddr=200.82.19.61
routwan0_realip_ip=200.82.19.61

Model RT-AC86U running 3004.388.5

I had noticed a similar behavior, but after an update to the latest firmware on my AX88U Pro it has stopped. Since you are running that version that needs some more digging I'm afraid.

 

[jorhett]

What scripts do you have installed? I don't find /jffs/scripts/ddns-start on my router.

This is the script you have to create if you use the "custom" choice for DDNS. It's not a matter of what's inside the script, it's that it is being invoked every 30 seconds even though it completes successfully.

 

[jorhett]

So I tried turning off the "IPv6 Update" option showing in the screenshot above, and the 30-second refresh disappeared. Very odd behavior given that every time it called the script it only offered the IPv4 address

 

[unknownz]

#bump

Observing the same behaviour and stops when "IPv6 Update" is turned off

 

[Deetlemore]

I've noticed that I run into this update cycle if my WAN goes down as well. Once my WAN connection is stable again and I have a visible WAN address on the Network Map page, I get the same 30 second refresh loop. Hitting "apply" on the DDNS page forces a restart of the DDNS service and corrects it.

I have IPv6 Update on as well, using 3004.388.5 on an AX-86U Pro. The only script I have installed is scmerlin, along with a 2 GB swap file. I didn't use DDNS on original firmware, so I'm not sure if this is exclusive to Merlin or not.

 

[mrf0ster]

Hi all, I am having this same issue of late as well, and its in a continual loop and friggin annoying. No scripts are installed for me.

Does anyone know how I get rid of it or stop it?

Current Setup:
RT-AX86U Pro
Firmware:3004.388.6_2

May 11 19:15:02 Mastiff: init
May 11 19:15:32 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:15:32 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:15:32 rc_service: waitting "stop_aae" via watchdog ...
May 11 19:28:28 Mastiff: init
May 11 19:28:58 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:28:58 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:28:58 rc_service: waitting "stop_aae" via watchdog ...
May 11 19:28:59 Mastiff: init
May 11 19:29:29 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:29:29 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:29:29 rc_service: waitting "stop_aae" via watchdog ...
May 11 19:29:30 Mastiff: init
May 11 19:30:00 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:30:00 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:30:00 rc_service: waitting "stop_aae" via watchdog ...

 

[ColinTaylor]

Hi all, I am having this same issue of late as well,

I don't see anything to do with DDNS in your output so it's not the same issue.

May 11 19:15:02 Mastiff: init
May 11 19:15:32 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:15:32 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:15:32 rc_service: waitting "stop_aae" via watchdog ...
May 11 19:28:28 Mastiff: init
May 11 19:28:58 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:28:58 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:28:58 rc_service: waitting "stop_aae" via watchdog ...
May 11 19:28:59 Mastiff: init
May 11 19:29:29 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:29:29 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:29:29 rc_service: waitting "stop_aae" via watchdog ...
May 11 19:29:30 Mastiff: init
May 11 19:30:00 rc_service: watchdog 2343:notify_rc stop_aae
May 11 19:30:00 rc_service: watchdog 2343:notify_rc start_mastiff
May 11 19:30:00 rc_service: waitting "stop_aae" via watchdog ...

Tools - Other Settings > Disable Asusnat tunnel = Yes.