November 8, 20187 yr I noticed a few messages in the system log regarding what looks like an ntp failure- Nov 8 15:50:58 Brunnhilde emhttpd: shcmd (127): /etc/rc.d/rc.ntpd restart Nov 8 15:50:58 Brunnhilde ntpd[31603]: ntpd exiting on signal 1 (Hangup) Nov 8 15:50:58 Brunnhilde ntpd[31603]: 127.127.1.0 local addr 127.0.0.1 -> <null> Nov 8 15:50:58 Brunnhilde ntpd[31603]: 10.0.1.1 local addr 10.0.1.20 -> <null> Nov 8 15:50:58 Brunnhilde root: Stopping NTP daemon... Nov 8 15:50:59 Brunnhilde ntpd[3902]: ntpd [email protected] Thu Aug 16 17:20:22 UTC 2018 (1): Starting Nov 8 15:50:59 Brunnhilde ntpd[3902]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Nov 8 15:50:59 Brunnhilde root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp Nov 8 15:50:59 Brunnhilde ntpd[3904]: proto: precision = 0.039 usec (-25) Nov 8 15:50:59 Brunnhilde ntpd[3904]: Listen normally on 0 lo 127.0.0.1:123 Nov 8 15:50:59 Brunnhilde ntpd[3904]: Listen normally on 1 bond0 10.0.1.20:123 Nov 8 15:50:59 Brunnhilde ntpd[3904]: Listen normally on 2 lo [::1]:123 Nov 8 15:50:59 Brunnhilde ntpd[3904]: Listen normally on 3 bond0 [fe80::225:90ff:fe44:11e6%12]:123 Nov 8 15:50:59 Brunnhilde ntpd[3904]: Listening on routing socket on fd #20 for interface updates Nov 8 15:50:59 Brunnhilde ntpd[3904]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Nov 8 15:50:59 Brunnhilde ntpd[3904]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Tried using several different NTP servers but get the same message in the system log every time I apply the new settings. brunnhilde-diagnostics-20181108-1555.zip
November 8, 20187 yr Author Linux 4.18.15-unRAID. Last login: Thu Nov 8 13:51:09 -0500 2018 on /dev/pts/0. root@Brunnhilde:~# ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) .LOCL. 10 l 1203 64 0 0.000 0.000 0.000 *odin.dahoney.me 45.56.118.161 3 u 46 64 377 0.182 0.014 0.038 root@Brunnhilde:~# odin is the local pfsense ntp server so I'm guessing this is proper? Maybe the unsynchronized message is normal when the daemon starts? I had just rebooted the server prior to seeing that initial message in the log.
Archived
This topic is now archived and is closed to further replies.