NTP updating every 30 seconds

Community Playground General Discussions
1

I realize this might not bother everyone else but it’s one of those things that drives me nuts. I decided to break out the Ethernet sniffer and see why the Weather plugin is delivering bad & no information. In doing so I discovered that the Vera is asking for an NTP update every 60 seonds. While the Vera folks are not the blame (it was the OpenWRT folks) the developers should have been wise enough to notice. >:(

To correct this from the command line, login to the very and edit /etc/config/ntpclient. Change the last line from 60 to 600 (the deault for ntpclient). Then restart ntpclient or reboot.

2

Thank you, does it make the Google Weather Plug-In more responsive? or is this fixing something that was driving you crazy with unnecessary updates.

3

I filed this to get it corrected in MiOS:
http://bugs.micasaverde.com/view.php?id=1383

Interestingly, my Vera2 (1.1.11xx Beta release) doesn’t have this config file…

4

Looked and did not find this file either. What I found was an init.d file to start and stop the service but the service’s program is not installed on my Vera2 (UI4 v1.1.1047). Plug in seems to work okay, but I must admit I have not paid attention to the frequency of updates.

5

My Vera (V1@1.1.1156) does have this config file:

config ntpserver
        option hostname '0.openwrt.pool.ntp.org'
        option port     '123'

config ntpserver
        option hostname '1.openwrt.pool.ntp.org'
        option port     '123'

config ntpserver
        option hostname '2.openwrt.pool.ntp.org'
        option port     '123'

config ntpserver
        option hostname '3.openwrt.pool.ntp.org'
        option port     '10123'

config ntpdrift
        option freq     '0'

config ntpclient
        option interval 60
        #option count   10
6

I can confirm that my vera2 does not have this. It looks like this is a vera1 related issue. The ntpclient on my unit does not even exist. The only config file I have it /etc/config/timeserver.

  • Garrett
7

Basically something that was driving me nuts. I don’t like unnecessary traffic eating away at bandwidth (even if it’s just a few bytes). It’s just the embedded engineer in me.

For those of you without the /etc/config/ntpclient, check to see if you have an ntpclient running (ps) and you should see something like this:

3281 root 1312 S /usr/sbin/ntpclient -i 60 -s -l -D -p 123 -h 192.16

That -i 60 means that the interval is set to 60 seconds. If you have no -i then it’s set to the default of 600 seconds. If you want to extend the interval time you can edit the /etc/init.d/ntpclient and change the -i value of find where it’s getting the value from, such as with config_get (maybe a config_set?). OpenWRT has a few ways to set the values such as nvram -set name=value (do nvram show to show all the variables).

8

[quote=“garrettwp, post:6, topic:167400”]I can confirm that my vera2 does not have this. It looks like this is a vera1 related issue. The ntpclient on my unit does not even exist. The only config file I have it /etc/config/timeserver.

  • Garrett[/quote]
    I can find no information on timeserver. You can take a look in the file (it’s text) but I’d avoid making changes until you know what parameter does what. You may not even need to make any changes.
9

[quote=“Ap15e, post:5, topic:167400”]My Vera (V1@1.1.1156) does have this config file:

[code]
config ntpserver
option hostname ‘0.openwrt.pool.ntp.org’
option port ‘123’

config ntpserver
option hostname ‘1.openwrt.pool.ntp.org’
option port ‘123’

config ntpserver
option hostname ‘2.openwrt.pool.ntp.org’
option port ‘123’

config ntpserver
option hostname ‘3.openwrt.pool.ntp.org’
option port ‘10123’

config ntpdrift
option freq ‘0’

config ntpclient
option interval 60
#option count 10
[/code][/quote]
Yes that’s the file, just change the 60 to 600. I’ve also added my own ntpserver to the top of that list. I have enough devices in my home that using a local ntpserver cuts down on a lot of internet bandwidth usage.

10

Vera2 runs OpenWRT Backfire which use rdate instead of ntpclient.
Vera1 runs OpenWRT Kamikaze which use ntpclient.
I’ve committed the change, from now on it should be 600 sec the retry interval.

11

Thanks @CJ!

12

Ah CJ, welcome back to the forum, its missed you guys! :wink:

13

[quote=“cj, post:10, topic:167400”]Vera2 runs OpenWRT Backfire which use rdate instead of ntpclient.
Vera1 runs OpenWRT Kamikaze which use ntpclient.
I’ve committed the change, from now on it should be 600 sec the retry interval.[/quote]
CJ, thanks!