[opensuse-arm] NTP on nanopi neo (air) ?
I don't seem to be able to run NTP on my nanopi neo air - when I try to start it, it enters a loop of stopping and starting, reporting "0.0.0.0 c01d 0d kern kernel time sync disabled". If I do a single-shot "ntpd -g -q", it works. The RTC seems very stable and I don't need microsecond accuracy, so a once-a-day "ntpd -g -q" would probably be enough. Still, I'd like to run ntp - is this some sort of hardware support issue? AFAICT, the Allwinner H3 does have an RTC.
From dmesg:
[6.850728] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0 [6.850736] sun6i-rtc 1f00000.rtc: RTC enabled Thanks for your suggestions. -- Per Jessen, Zürich (6.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mittwoch, 15. März 2017 08:52:28 CET Per Jessen wrote:
I don't seem to be able to run NTP on my nanopi neo air - when I try to start it, it enters a loop of stopping and starting, reporting "0.0.0.0 c01d 0d kern kernel time sync disabled".
Are you sure this is the complete message? Please post the complete message,including the timestamps and linebreaks, as you did for the dmesg output.
If I do a single-shot "ntpd -g -q", it works. The RTC seems very stable and I don't need microsecond accuracy, so a once-a-day "ntpd -g -q" would probably be enough. Still, I'd like to run ntp - is this some sort of hardware support issue? AFAICT, the Allwinner H3 does have an RTC.
From dmesg: [6.850728] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0 [6.850736] sun6i-rtc 1f00000.rtc: RTC enabled
Thanks for your suggestions.
Read https://www.novell.com/coolsolutions/feature/15345.html and try if this helps ... Kind regards, Stefan-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Brüns, Stefan wrote:
On Mittwoch, 15. März 2017 08:52:28 CET Per Jessen wrote:
I don't seem to be able to run NTP on my nanopi neo air - when I try to start it, it enters a loop of stopping and starting, reporting "0.0.0.0 c01d 0d kern kernel time sync disabled".
Are you sure this is the complete message? Please post the complete message,including the timestamps and linebreaks, as you did for the dmesg output.
Sorry, no, that wasn't the complete log. This is the bit that repeats when ntpd is being restarted: 15 Mar 19:55:39 ntpd[6275]: 192.168.2.254 local addr 192.168.2.40 -> <null> 15 Mar 19:55:39 ntp_intres[6276]: 0.0.0.0 c01d 0d kern kernel time sync disabled 15 Mar 19:55:39 ntpd[6275]: 0.0.0.0 c01d 0d kern kernel time sync disabled 15 Mar 19:55:40 ntpd[6292]: Listen and drop on 0 v6wildcard [::]:123 15 Mar 19:55:40 ntpd[6292]: Listen and drop on 1 v4wildcard 0.0.0.0:123 15 Mar 19:55:40 ntpd[6292]: Listen normally on 2 lo 127.0.0.1:123 15 Mar 19:55:40 ntpd[6292]: Listen normally on 3 wlan0 192.168.2.40:123 15 Mar 19:55:40 ntpd[6292]: Listen normally on 4 lo [::1]:123 15 Mar 19:55:40 ntpd[6292]: Listen normally on 5 wlan0 [2a03:7520:4c68:1:ff99::bf4f]:123 15 Mar 19:55:40 ntpd[6292]: Listen normally on 6 wlan0 [2a03:7520:4c68:1:890f:3340:d181:8f2e]:123 15 Mar 19:55:40 ntpd[6292]: Listen normally on 7 wlan0 [2a03:7520:4c68:1:96a1:a2ff:fea3:ba7a]:123 15 Mar 19:55:40 ntpd[6292]: Listen normally on 8 wlan0 [fe80::96a1:a2ff:fea3:ba7a%2]:123 15 Mar 19:55:40 ntpd[6292]: Listening on routing socket on fd #25 for interface updates 15 Mar 19:55:40 ntpd[6292]: Listen normally on 9 multicast [ff05::101]:123 15 Mar 19:55:40 ntpd[6292]: Joined ff05::101 socket to multicast group ff05::101 15 Mar 19:55:40 ntpd[6292]: 0.0.0.0 c01d 0d kern kernel time sync enabled 15 Mar 19:55:40 ntpd[6292]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM 15 Mar 19:55:40 ntpd[6292]: 0.0.0.0 c016 06 restart 15 Mar 19:55:41 ntpd[6292]: Listen for broadcasts to 192.168.7.255 on interface #3 wlan0 15 Mar 19:55:42 ntpd[6292]: ::1 config: server 192.168.2.254 15 Mar 19:55:42 ntpd[6292]: ntpd exiting on signal 15 (Terminated) 15 Mar 19:55:42 ntpd[6292]: 192.168.2.254 local addr 192.168.2.40 -> <null> 15 Mar 19:55:42 ntpd[6292]: 0.0.0.0 c01d 0d kern kernel time sync disabled 15 Mar 19:55:42 ntp_intres[6293]: 0.0.0.0 c01d 0d kern kernel time sync disabled
Read https://www.novell.com/coolsolutions/feature/15345.html and try if this helps ...
Nope - I added "server 192.168.2.254 burst iburst", almost the same result as above. Interesting - then I ran "strace ntpd -u ntp:ntp -c /etc/ntp.conf", and that worked. At least it keeps running: 15 Mar 19:59:28 ntpd[8033]: ntpd exiting on signal 15 (Terminated) 15 Mar 19:59:28 ntpd[8033]: 192.168.2.254 local addr 192.168.2.40 -> <null> 15 Mar 19:59:28 ntpd[8033]: 0.0.0.0 c01d 0d kern kernel time sync disabled 15 Mar 19:59:28 ntp_intres[8034]: 0.0.0.0 c01d 0d kern kernel time sync disabled 15 Mar 20:01:26 ntpd[8263]: Listen and drop on 0 v6wildcard [::]:123 15 Mar 20:01:26 ntpd[8263]: Listen and drop on 1 v4wildcard 0.0.0.0:123 15 Mar 20:01:26 ntpd[8263]: Listen normally on 2 lo 127.0.0.1:123 15 Mar 20:01:26 ntpd[8263]: Listen normally on 3 wlan0 192.168.2.40:123 15 Mar 20:01:26 ntpd[8263]: Listen normally on 4 lo [::1]:123 15 Mar 20:01:26 ntpd[8263]: Listen normally on 5 wlan0 [2a03:7520:4c68:1:ff99::bf4f]:123 15 Mar 20:01:26 ntpd[8263]: Listen normally on 6 wlan0 [2a03:7520:4c68:1:890f:3340:d181:8f2e]:123 15 Mar 20:01:26 ntpd[8263]: Listen normally on 7 wlan0 [2a03:7520:4c68:1:96a1:a2ff:fea3:ba7a]:123 15 Mar 20:01:26 ntpd[8263]: Listen normally on 8 wlan0 [fe80::96a1:a2ff:fea3:ba7a%2]:123 15 Mar 20:01:26 ntpd[8263]: Listening on routing socket on fd #25 for interface updates 15 Mar 20:01:26 ntpd[8263]: Listen normally on 9 multicast [ff05::101]:123 15 Mar 20:01:26 ntpd[8263]: Joined ff05::101 socket to multicast group ff05::101 15 Mar 20:01:26 ntpd[8263]: 0.0.0.0 c01d 0d kern kernel time sync enabled 15 Mar 20:01:26 ntpd[8263]: 0.0.0.0 c012 02 freq_set kernel 0.000 PPM 15 Mar 20:01:26 ntpd[8263]: 0.0.0.0 c016 06 restart 15 Mar 20:01:27 ntpd[8263]: Listen for broadcasts to 192.168.7.255 on interface #3 wlan0 15 Mar 20:01:48 ntpd[8263]: 0.0.0.0 c615 05 clock_sync 15 Mar 20:03:56 ntpd[8263]: 0.0.0.0 0618 08 no_sys_peer # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 192.168.2.254 .DCFa. 1 u 52 64 1 9.115 -0.233 0.001 fe80::202:a5ff: LOCAL(0) 11 u 14 16 7 7.196 -26.854 7.523 So it seems to only affect ntp when it's started from systemd? -- Per Jessen, Zürich (11.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Brüns, Stefan -
Per Jessen