Console messages after update

Status
Not open for further replies.

trentk10

Explorer
Joined
Jan 7, 2017
Messages
69
I think I have resolved all the known issues (smart bug for flash drive and nvme devices, system health warning) but one since updating to 11.1 today

I keep getting the following, I did not get this message regularly in 11.0 U4 and earlier.

Code:
Feb 14 14:41:03 freenas inadyn[29246]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 14:51:06 freenas inadyn[29246]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 15:01:08 freenas inadyn[29246]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 15:11:11 freenas inadyn[29246]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 15:21:14 freenas inadyn[29246]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx


My time is set to 600 in the dynamic dns settings and I am using no-ip, but I did not get these messages every 10 minutes before I upgraded.

I am not sure where to look in my system for more information, or if I need to change a setting somewhere.
Thanks :)
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
Those messages come from the dynamic DNS service. If you are updating every 600 seconds, that is updating every 10 mins, which are exactly what you're seeing in the logs. You probably shouldn't be force updating that frequently. I would set the force update to daily at most frequent, and the regular update period to 10 mins.
 

trentk10

Explorer
Joined
Jan 7, 2017
Messages
69
Those messages come from the dynamic DNS service. If you are updating every 600 seconds, that is updating every 10 mins, which are exactly what you're seeing in the logs. You probably shouldn't be force updating that frequently. I would set the force update to daily at most frequent, and the regular update period to 10 mins.

Where can I set the "force update" and the "regular update" settings at? In the GUI (using the old one currently) there is only one field for "Update Period" , that is what I have set to 600.
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
I am not running 11.1, but according to the docs, there should be both a "Update Period" and "Forced Update Period" fields: https://doc.freenas.org/11/services.html#dynamic-dns

EDIT: I just noticed that the table lists different options than the picture shows. I'll file a bug report for that one. I'm not sure at this point, then, what the correct option is for you. I would suggest turning down the setting to once per day to avoid being banned by your DDNS provider for too frequent updates.

EDIT 2: Bug report: https://redmine.ixsystems.com/issues/28512
 

trentk10

Explorer
Joined
Jan 7, 2017
Messages
69
Ok thanks, I will turn it down for now :)
 

trentk10

Explorer
Joined
Jan 7, 2017
Messages
69
Ok, I was not able to stop this or slow it down without stopping the service completely. I still kept getting a forced update every 10 mins (my pre upgrade time was 600) no matter what number of seconds I put into the GUI.

I tried the new beta GUI, which does have both fields for force update and standard update, and it would not save any changes I made. Also, I didn't get a message about the service stopping/starting in the new GUI footer either, so maybe that's why it didn't accept any changes I made ?

I found a config file at:
Code:
root@freenas:/usr/local/etc # cat inadyn.conf


It has the following parameters:
Code:
period = 600
provider default@no-ip.com {
	username = my no-ip username
	password = my no-ip password
	hostname = { "my no-ip domain.net" }
}



I used nano and changed the period to 60, stopped and started the service, and it took the change (wanted to prove it worked so only went a minute). I got a forced update every minute. So, I changed the period in the config to 86400, stopped and started the service, and now it will happen a lot less :)

Code:
Feb 14 19:34:25 freenas inadyn[61103]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 19:44:28 freenas inadyn[61103]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 19:54:31 freenas inadyn[61103]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 20:04:34 freenas inadyn[61103]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 20:14:37 freenas inadyn[61103]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 20:16:11 freenas inadyn[61103]: STOP command received, exiting.
Feb 14 20:16:27 freenas inadyn[2359]: In-a-dyn version 2.2 -- Dynamic DNS update client.
Feb 14 20:16:27 freenas inadyn[2359]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 20:17:27 freenas inadyn[2359]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 20:18:28 freenas inadyn[2359]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx
Feb 14 20:18:41 freenas inadyn[2359]: STOP command received, exiting.
Feb 14 20:18:47 freenas inadyn[2763]: In-a-dyn version 2.2 -- Dynamic DNS update client.
Feb 14 20:18:47 freenas inadyn[2763]: Update forced for alias mydomain.net, new IP# xxx.xxx.xxx.xxx


I did a google search on In-a-dyn and went to the following link: https://github.com/troglobit/inadyn

I skimmed through the main page there, they had some example configs, but I did not see anything about how to differentiate between an forced update period and a standard update period. I did go through it pretty fast though, due to lack of time to play with this any more this evening. Hopefully I get time tomorrow to look into this a little deeper.
 
Last edited:

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
Good troubleshooting! I would recommend filing a bug on this behavior (and post the link back here) because this is clearly not expected behavior.
 

trentk10

Explorer
Joined
Jan 7, 2017
Messages
69
Last edited:
Status
Not open for further replies.
Top