L0rdRaiden Posted July 29, 2020 Posted July 29, 2020 (edited) I was getting NTP related errors and when I update NTS settings I get this, can someone please help me to find a solution? It happend after a hard shutdown (electricity went off) but I don't know if it's related. Jul 28 18:44:14 Unraid ntpd[2010]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Jul 28 18:44:15 Unraid ntpd[2010]: frequency error 2004 PPM exceeds tolerance 500 PPM Jul 28 18:46:03 Unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jul 28 18:46:45 Unraid root: Fix Common Problems: Other Warning: Could not perform docker application port tests Jul 29 17:39:20 Unraid nginx: 2020/07/29 17:39:20 [error] 8729#8729: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. Jul 29 17:39:20 Unraid nginx: 2020/07/29 17:39:20 [error] 8729#8729: nchan: A message from the past has just been published. Unless the system time has been adjusted, this should never happen. Jul 29 17:44:01 Unraid emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Jul 29 17:44:47 Unraid emhttpd: shcmd (96): ln -sf /usr/share/zoneinfo/Europe/Paris /etc/localtime-copied-from Jul 29 17:44:47 Unraid emhttpd: shcmd (97): cp /etc/localtime-copied-from /etc/localtime Jul 29 17:44:47 Unraid emhttpd: shcmd (98): /usr/local/emhttp/webGui/scripts/update_access Jul 29 17:44:47 Unraid root: sshd: no process found Jul 29 17:44:48 Unraid emhttpd: shcmd (99): /etc/rc.d/rc.ntpd restart Jul 29 17:44:48 Unraid ntpd[21257]: ntpd exiting on signal 1 (Hangup) Jul 29 17:44:48 Unraid ntpd[21257]: 127.127.1.0 local addr 127.0.0.1 -> <null> Jul 29 17:44:48 Unraid root: Stopping NTP daemon... Jul 29 17:44:49 Unraid ntpd[22061]: ntpd [email protected] Tue Jun 23 18:44:10 UTC 2020 (1): Starting Jul 29 17:44:49 Unraid ntpd[22061]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Jul 29 17:44:49 Unraid ntpd[22061]: ---------------------------------------------------- Jul 29 17:44:49 Unraid ntpd[22061]: ntp-4 is maintained by Network Time Foundation, Jul 29 17:44:49 Unraid ntpd[22061]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Jul 29 17:44:49 Unraid ntpd[22061]: corporation. Support and training for ntp-4 are Jul 29 17:44:49 Unraid ntpd[22061]: available at https://www.nwtime.org/support Jul 29 17:44:49 Unraid ntpd[22061]: ---------------------------------------------------- Jul 29 17:44:49 Unraid ntpd[22063]: proto: precision = 0.050 usec (-24) Jul 29 17:44:49 Unraid ntpd[22063]: line 86 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 86, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: line 87 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 87, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: line 88 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 88, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: line 89 column 14 syntax error, unexpected T_String, expecting T_EOC Jul 29 17:44:49 Unraid ntpd[22063]: syntax error in /etc/ntp.conf line 89, column 14 Jul 29 17:44:49 Unraid ntpd[22063]: basedate set to 2020-06-11 Jul 29 17:44:49 Unraid ntpd[22063]: gps base set to 2020-06-14 (week 2110) Jul 29 17:44:49 Unraid ntpd[22063]: Listen normally on 0 lo 127.0.0.1:123 Jul 29 17:44:49 Unraid ntpd[22063]: Listen normally on 1 br0 192.168.1.200:123 Jul 29 17:44:49 Unraid ntpd[22063]: Listen normally on 2 lo [::1]:123 Jul 29 17:44:49 Unraid ntpd[22063]: Listening on routing socket on fd #19 for interface updates Jul 29 17:44:49 Unraid ntpd[22063]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Jul 29 17:44:49 Unraid ntpd[22063]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Jul 29 17:44:49 Unraid root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp Jul 29 17:54:21 Unraid smbd[25083]: [2020/07/29 17:54:21.267529, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:21 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:24 Unraid smbd[25083]: [2020/07/29 17:54:24.237445, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:24 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:24 Unraid smbd[25083]: [2020/07/29 17:54:24.253927, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:24 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:24 Unraid smbd[25083]: [2020/07/29 17:54:24.272429, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:24 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 17:54:25 Unraid smbd[25083]: [2020/07/29 17:54:25.691188, 0] ../../lib/param/loadparm.c:415(lp_bool) Jul 29 17:54:25 Unraid smbd[25083]: lp_bool(no): value is not boolean! Jul 29 18:00:41 Unraid kernel: kvm: already loaded the other module Edited July 29, 2020 by L0rdRaiden Quote
L0rdRaiden Posted July 29, 2020 Author Posted July 29, 2020 (edited) Some more info NTP conf file # Sample /etc/ntp.conf: Configuration file for ntpd. # # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. The # default stratum is usually 3, but in this case we elect to use stratum # 0. Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other other # synchronization source is available. In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # disregard all other synchronization sources, unless the kernel # modifications are in use and declare an unsynchronized condition. # server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 # # NTP server (list one or more) to synchronize with: #server 0.pool.ntp.org iburst #server 1.pool.ntp.org iburst #server 2.pool.ntp.org iburst #server 3.pool.ntp.org iburst # # Full path of a directory where statistics files should be created # statsdir /var/lib/ntp/stats # # Location of an alternate log file to be used instead of the default system syslog(3) facility # #logfile /var/log/ntp # # Drift file. Put this in a directory which the daemon can write to. # No symbolic links allowed, either, since the daemon updates the file # by creating a temporary in the same directory and then rename()'ing # it to the file. # driftfile /var/lib/ntp/drift # # Location of PID file # pidfile /var/run/ntpd.pid # # Uncomment to use a multicast NTP server on the local subnet: #multicastclient 224.0.1.1 # listen on default 224.0.1.1 # Set an optional compensation for broadcast packet delay: #broadcastdelay 0.008 # # Keys file. If you want to diddle your server at run time, make a # keys file (mode 640 owned by root:ntp) and define the key number to # be used for making requests. # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote # systems might be able to reset your clock at will. # #keysdir /etc #keys /etc/ntp.keys #trustedkey 65535 #requestkey 65535 #controlkey 65535 # # Don't serve time or stats to anyone else by default (more secure) restrict default limited kod nomodify notrap nopeer noquery restrict -6 default limited kod nomodify notrap nopeer noquery # # Use these lines instead if you do want to serve time and stats to # other machines on the network: #restrict default limited kod nomodify notrap nopeer #restrict -6 default limited kod nomodify notrap nopeer # # Trust ourselves. :-) restrict 127.0.0.1 restrict ::1 # Generated entries follow: interface ignore wildcard interface listen br0 server time1.google.com iburst server time2.google.com iburst server time3.google.com iburst Edited July 29, 2020 by L0rdRaiden Quote
L0rdRaiden Posted August 3, 2020 Author Posted August 3, 2020 (edited) For some reason when I reboot unraid move the time 2 hours forward. Look at the date command, it resolves ok, the others are wrong? how can I fix this? I have removed the drift file from the flash but might not be related, and for some reason NTP is not re-creating the file Aug 3 20:55:56 Unraid root: Stopping NTP daemon... Aug 3 20:55:57 Unraid ntpd[18975]: ntpd [email protected] Tue Jun 23 18:44:10 UTC 2020 (1): Starting Aug 3 20:55:57 Unraid ntpd[18975]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Aug 3 20:55:57 Unraid ntpd[18975]: ---------------------------------------------------- Aug 3 20:55:57 Unraid ntpd[18975]: ntp-4 is maintained by Network Time Foundation, Aug 3 20:55:57 Unraid ntpd[18975]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Aug 3 20:55:57 Unraid ntpd[18975]: corporation. Support and training for ntp-4 are Aug 3 20:55:57 Unraid ntpd[18975]: available at https://www.nwtime.org/support Aug 3 20:55:57 Unraid ntpd[18975]: ---------------------------------------------------- Aug 3 20:55:57 Unraid ntpd[18977]: proto: precision = 0.080 usec (-23) Aug 3 20:55:57 Unraid ntpd[18977]: basedate set to 2020-06-11 Aug 3 20:55:57 Unraid ntpd[18977]: gps base set to 2020-06-14 (week 2110) Aug 3 20:55:57 Unraid ntpd[18977]: Listen normally on 0 lo 127.0.0.1:123 Aug 3 20:55:57 Unraid ntpd[18977]: Listen normally on 1 br0 192.168.1.200:123 Aug 3 20:55:57 Unraid ntpd[18977]: Listen normally on 2 lo [::1]:123 Aug 3 20:55:57 Unraid ntpd[18977]: Listening on routing socket on fd #19 for interface updates Aug 3 20:55:57 Unraid ntpd[18977]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 3 20:55:57 Unraid ntpd[18977]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 3 20:55:57 Unraid root: Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp Aug 3 20:56:00 Unraid crond[2106]: time disparity of -119 minutes detected Edited August 3, 2020 by L0rdRaiden Quote
L0rdRaiden Posted August 5, 2020 Author Posted August 5, 2020 (edited) Can someone please help me here? it shouln't be that hard for someone with a little bit of knowledge around linux. I have spent hours googling I have tried everything but still can not solve this issue unraid-diagnostics-20200805-1959.zip Edited August 5, 2020 by L0rdRaiden Quote
pras1011 Posted September 12, 2020 Posted September 12, 2020 I am having the same error on my syslog. Is this a problem? Can it be ignored? Did you fix it? Quote
L0rdRaiden Posted September 12, 2020 Author Posted September 12, 2020 4 minutes ago, pras1011 said: I am having the same error on my syslog. Is this a problem? Can it be ignored? Did you fix it? I did an almost fresh install to solve it Quote
pras1011 Posted September 12, 2020 Posted September 12, 2020 Does this error cause an issue with the server? Quote
L0rdRaiden Posted September 12, 2020 Author Posted September 12, 2020 2 minutes ago, pras1011 said: Does this error cause an issue with the server? Not that I notice, but i didn't like it xD. If you know how in 30 mins you can do a fresh install by just keeping some config file from the flash. In the wiki there is an explanation for all the config files. Quote
pras1011 Posted September 12, 2020 Posted September 12, 2020 Do you have a link to that wiki?Sent from my SM-G977B using Tapatalk Quote
ChatNoir Posted September 12, 2020 Posted September 12, 2020 The wiki is linked at the bottom of the pages as Documentation. Quote
pras1011 Posted September 12, 2020 Posted September 12, 2020 Thanks. But I cant find it. Please can you tell me where it is?Sent from my SM-G977B using Tapatalk Quote
L0rdRaiden Posted September 12, 2020 Author Posted September 12, 2020 14 minutes ago, pras1011 said: Thanks. But I cant find it. Please can you tell me where it is? Sent from my SM-G977B using Tapatalk https://wiki.unraid.net/Files_on_v6_boot_drive Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.