ntp Questions

[bimmerdriver]

I have two opnsense systems, both running on windows server 2012r2 hyper-v. One system is running the latest release and the other is running 19.1b. I've noticed on both systems that the ntp service is taking longer to start up after rebooting than it used to. Both systems are using the default ntp settings.

I took a look at the status and I have some questions.

Here are the messages in the log, beginning after restarting the ntp service:

Dec 15 09:13:09   ntpd[84257]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Dec 15 09:13:09   ntpd[84257]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized
Dec 15 09:13:09   ntpd[84257]: mlockall(): Cannot allocate memory
Dec 15 09:13:09   ntpd[84257]: Listening on routing socket on fd #26 for interface updates
Dec 15 09:13:09   ntpd[84257]: Listen normally on 5 hn0 162.156.75.11:123
Dec 15 09:13:09   ntpd[84257]: Listen normally on 4 hn0 [fe80::215:5dff:fe5c:e233%5]:123
Dec 15 09:13:09   ntpd[84257]: Listen normally on 3 lo0 127.0.0.1:123
Dec 15 09:13:09   ntpd[84257]: Listen normally on 2 lo0 [::1]:123Dec 15 09:13:09   ntpd[84257]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Dec 15 09:13:09   ntpd[84257]: Listen and drop on 0 v6wildcard [::]:123
Dec 15 09:13:09   ntpd[84257]: restrict: 'monitor' cannot be disabled while 'limited' is enabled
Dec 15 09:13:09   ntpd[84257]: proto: precision = 0.100 usec (-23)
Dec 15 09:13:09   ntpd[84036]: Command line: /usr/local/sbin/ntpd -g -c /var/etc/ntpd.conf -p /var/run/ntpd.pid
Dec 15 09:13:09   ntpd[84036]: ntpd 4.2.8p12@1.3728-o Mon Sep 17 00:37:07 UTC 2018 (1): Starting
Dec 15 09:13:09   ntpd[77483]: 206.108.0.134 local addr 162.156.75.11 -> <null>
Dec 15 09:13:09   ntpd[77483]: 2001:6a0:0:31::2 local addr fe80::215:5dff:fe5c:e233%5 -> <null>
Dec 15 09:13:09   ntpd[77483]: 162.248.221.109 local addr 162.156.75.11 -> <null>
Dec 15 09:13:09   ntpd[77483]: 54.39.173.225 local addr 162.156.75.11 -> <null>
Dec 15 09:13:09   ntpd[77483]: ntpd exiting on signal 15 (Terminated)

One of the message refers to memory. The system is currently using only 20% of memory.

Also, it appears that one of the default servers is not reachable. Refer to the screen capture.

[der-mechaniker]

Hi bimmerdriver,

When looking at your screenshot, I noticed that it was only the IPv6 address that was having an issue.  How is your network infrastructure setup?  Can you use an IPv4 address instead?

Regarding the memory lock error: Dec 15 09:13:09   ntpd[84257]: mlockall(): Cannot allocate memory

I was referred to this 2017 October 21 by @lattera (Shawn Webb) and @mjharmon: https://mobile.twitter.com/lattera/status/921787114580213761 

[topuli]

these are standard messages.
The opnsense gui shows the servertime and the sync source under dashboard\lobby in the section network time.

for me to work correctly, i had to set kern.timecounter.hardware in the system\settings\tunables
i have set the value to "HPET"

t.