Three reboots in 24 hours

[evansnp]

My 8800AXL R2 has rebooted three times in the last 24 hours. On inspection, the logs are full of DDNS errors:

Code: Select all

Mar  8 08:38:16 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:27 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:27 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:37 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:37 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:47 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:47 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:57 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:57 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:39:07 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:39:07 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:39:17 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:39:17 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:39:27 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:39:27 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
etc.

Note: I am running the firmware that fixed the DDNS https login problem: 2.52.d16

For now, I have removed the DDNS setting to see if the reboots go away, as there may be a memory leak in the DDNS daemon.

[billion_fan]

My 8800AXL R2 has rebooted three times in the last 24 hours. On inspection, the logs are full of DDNS errors:

Code: Select all

Mar  8 08:38:16 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:27 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:27 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:37 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:37 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:47 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:47 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:38:57 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:38:57 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:39:07 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:39:07 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:39:17 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:39:17 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
Mar  8 08:39:27 user info syslog: ddnsd: evansnp.uk (ppp1.1) IP has changed from (null) to xxxxxx
Mar  8 08:39:27 user info syslog: ddnsd: update evansnp.uk request failed. Please check the setting.
etc.

Note: I am running the firmware that fixed the DDNS https login problem: 2.52.d16

For now, I have removed the DDNS setting to see if the reboots go away, as there may be a memory leak in the DDNS daemon.

How strange, let me know if disabling the DDNS stops the reboot

[evansnp]

I don't understand why this has suddenly started happening. The credentials are correct, and have not changed, and I can perform a manual request without problems.

[billion_fan]

I don't understand why this has suddenly started happening. The credentials are correct, and have not changed, and I can perform a manual request without problems.

Is it still happening??

Have you tried to delete the credentials and try to re-enter them?

[evansnp]

Hi Billion_Fan. It's too early to say whether it still happens, but I did try re-entering the creds after trying a manual update to confirm that the DNS-O-Matic service was happy ...... no change, loads of DDNS errors in the logs.

[billion_fan]

Hi Billion_Fan. It's too early to say whether it still happens, but I did try re-entering the creds after trying a manual update to confirm that the DNS-O-Matic service was happy ...... no change, loads of DDNS errors in the logs.

Something might have changed again (on Dns-o-Matic) side, I will check with our engineers if they know anything about it.

For now disable it, and do a manual update if needed

[evansnp]

Hi Billion_Fan. I've run for a week now with no reboots, and a very clean log. Any news from your R&D guys re the DDNS daemon?

[billion_fan]

Hi Billion_Fan. I've run for a week now with no reboots, and a very clean log. Any news from your R&D guys re the DDNS daemon?

No update yet, still waiting for feedback from our engineers

[billion_fan]

Hi Billion_Fan. I've run for a week now with no reboots, and a very clean log. Any news from your R&D guys re the DDNS daemon?

No update yet, still waiting for feedback from our engineers

Attached is a newer firmware that should work with the DNS-O-Matic, (this is for the Bipac 8800AXL R2)

[evansnp]

Thanks Billion_Fan, and your engineering team
I'll give it try in a sec!