• [6.12] NTP not syncing Automaticly

    nade

    By nade

      • Solved Minor

    After update on 6.12 app store and dockerhub version information stopped working.

    I checked the usual suspects and found out that my server time was stuck at 2002.

     

    I'm using ntp with the pool: pool.ntp.org

    I disabled ntp and enabled it again, without a change.

    I rebooted the server without a change.

    I changed the ntp address to plain ipv4 addresses instead of dns without a change.

     

    [Temporary solution]

    Only manualy syncing ntp on the command line with the command "ntpdate -u pool.ntp.org" seem to fix the issue: 

    root@unraid:~# ntpdate -u pool.ntp.org
17 Jun 17:38:56 ntpdate[29808]: step time server 94.16.114.254 offset +677166288.870671 sec

     

    After a manual sync, all worked fine again.

    So it seems the automatically syncing is broken anyhow.

    I heard that problem from multiple people now in my bubble, and all had to manually sync to get the app store and docker versions back to work.

     

    Regards

     

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    bonienl

    Reboot your system and post the output of 

    ntpq -p

     

    I have no problems with NTP.

     

    Also understand that NTP does not immediately correct the time in one go, but adjust in gradual steps, which may take days if the time difference is big.

     

     

    Link to comment
    nade

    @bonienl can do that later for now i need to finish my work.

     

    But until now about 6 friends had the same problem, and a couple ppl on the unofficial unraid discord also.

     

    Link to comment
    bonienl
    5 hours ago, bkwq said:

    NTP is also not working for me as of 6.12.  

     

    See my earlier answer. Post result of the requested command.

     

    Link to comment
    lepresidente

    copied from my post in general issues,

    Was about to make a issue about this as well, after updating to 6.12 none of the time servers ever sync as they complain they are unreachable
      

    ntpq> peer
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*LOCAL(0)        .LOCL.          10 l   26   64  377    0.000   +0.000   0.002
 10.0.0.1 (OPNse .INIT.          16 u    -   64    0    0.000   +0.000   0.000
 tock.sol.net    .INIT.          16 u    -   64    0    0.000   +0.000   0.000
 108.61.23.93 (1 .INIT.          16 u    -   64    0    0.000   +0.000   0.000
 af-south-1.clea .INIT.          16 u    -   64    0    0.000   +0.000   0.000

ntpq> as
ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 64788  961a   yes   yes  none  sys.peer    sys_peer  1
  2 64789  8011   yes    no  none    reject    mobilize  1
  3 64790  8011   yes    no  none    reject    mobilize  1
  4 64791  8011   yes    no  none    reject    mobilize  1
  5 64792  8011   yes    no  none    reject    mobilize  1


    Debug info using the above time server manually

      

    root@Zeus:/mnt/user/appdata/Authelia# ping tock.sol.net
PING tock.sol.net (206.55.65.229) 56(84) bytes of data.
64 bytes from tock.sol.net (206.55.65.229): icmp_seq=1 ttl=49 time=928 ms
64 bytes from tock.sol.net (206.55.65.229): icmp_seq=2 ttl=49 time=889 ms
64 bytes from tock.sol.net (206.55.65.229): icmp_seq=3 ttl=49 time=807 ms
^C
--- tock.sol.net ping statistics ---
4 packets transmitted, 3 received, 25% packet loss, time 2999ms
rtt min/avg/max/mdev = 806.710/874.363/927.824/50.452 ms
root@Zeus:/mnt/user/appdata/Authelia# killall ntpd
root@Zeus:/mnt/user/appdata/Authelia# ntpdate tock.sol.net
17 Jun 09:49:56 ntpdate[20969]: step time server 206.55.65.229 offset +6.650815 sec


    ntpd started in debug

      

    root@Zeus:/mnt/user/appdata/Authelia# ntpd -d
17 Jun 09:50:48 ntpd[26008]: ntpd [email protected] Fri Jun  3 04:17:10 UTC 2022 (1): Starting
17 Jun 09:50:48 ntpd[26008]: Command line: ntpd -d
17 Jun 09:50:48 ntpd[26008]: ----------------------------------------------------
17 Jun 09:50:48 ntpd[26008]: ntp-4 is maintained by Network Time Foundation,
17 Jun 09:50:48 ntpd[26008]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
17 Jun 09:50:48 ntpd[26008]: corporation.  Support and training for ntp-4 are
17 Jun 09:50:48 ntpd[26008]: available at https://www.nwtime.org/support
17 Jun 09:50:48 ntpd[26008]: ----------------------------------------------------
17 Jun 09:50:48 ntpd[26008]: proto: precision = 2.304 usec (-19)
Finished Parsing!!
17 Jun 09:50:48 ntpd[26008]: basedate set to 2022-05-22
17 Jun 09:50:48 ntpd[26008]: gps base set to 2022-05-22 (week 2211)
hack_restrict: op RESTRICT_FLAGS addr 0.0.0.0 mask 0.0.0.0 ippeerlimit -1 mflags 00000000 rflags 00000bd0
hack_restrict: op RESTRICT_FLAGS addr :: mask :: ippeerlimit -1 mflags 00000000 rflags 00000bd0
hack_restrict: op RESTRICT_FLAGS addr :: mask :: ippeerlimit -1 mflags 00000000 rflags 00000bd0
hack_restrict: op RESTRICT_FLAGS addr 127.0.0.1 mask 255.255.255.255 ippeerlimit -1 mflags 00000000 rflags 00000000
hack_restrict: op RESTRICT_FLAGS addr ::1 mask ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff ippeerlimit -1 mflags 00000000 rflags 00000000
move_fd: estimated max descriptors: 40960, initial socket boundary: 16
17 Jun 09:50:48 ntpd[26008]: Listen normally on 0 lo 127.0.0.1:123
hack_restrict: op RESTRICT_FLAGS addr 127.0.0.1 mask 255.255.255.255 ippeerlimit -4 mflags 00003000 rflags 00000001
17 Jun 09:50:48 ntpd[26008]: Listening on routing socket on fd #17 for interface updates
newpeer(127.127.1.0) - ippeerlimit -1 ignored
key_expire: at 0 associd 7312
peer_clear: at 0 next 1 associd 7312 refid INIT
event at 0 LOCAL(0) 8011 81 mobilize assoc 7312
newpeer: 127.0.0.1->127.127.1.0 mode 3 vers 4 poll 6 6 flags 0x9 0x1 ttl 0 key 00000000
newpeer(10.0.0.1) - ippeerlimit -1 ignored
key_expire: at 0 associd 7313
peer_clear: at 0 next 2 associd 7313 refid INIT
event at 0 10.0.0.1 8011 81 mobilize assoc 7313
newpeer: <null>->10.0.0.1 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000
kernel loop status 0x2041 (Clock Unsynchronized)
17 Jun 09:50:48 ntpd[26008]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
event at 0 0.0.0.0 c01d 0d kern kernel time sync enabled
kernel loop status 0x2041 (Clock Unsynchronized)
17 Jun 09:50:48 ntpd[26008]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized
event at 0 0.0.0.0 c012 02 freq_set kernel 5.815 PPM
event at 0 0.0.0.0 c016 06 restart
peer_name_resolved(pool.ntp.org) rescode 0
newpeer(162.159.200.123) - ippeerlimit -1 ignored
key_expire: at 0 associd 7314
peer_clear: at 0 next 2 associd 7314 refid INIT
event at 0 162.159.200.123 8011 81 mobilize assoc 7314
newpeer: <null>->162.159.200.123 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000
peer_name_resolved(0.pool.ntp.org) rescode 0
newpeer(102.64.113.152) - ippeerlimit -1 ignored
key_expire: at 0 associd 7315
peer_clear: at 0 next 2 associd 7315 refid INIT
event at 0 102.64.113.152 8011 81 mobilize assoc 7315
newpeer: <null>->102.64.113.152 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000
peer_name_resolved(1.pool.ntp.org) rescode 0
newpeer(196.10.54.58) - ippeerlimit -1 ignored
key_expire: at 0 associd 7316
peer_clear: at 0 next 1 associd 7316 refid INIT
event at 0 196.10.54.58 8011 81 mobilize assoc 7316
newpeer: <null>->196.10.54.58 mode 3 vers 4 poll 6 10 flags 0x101 0x1 ttl 0 key 00000000
refclock_transmit: at 1 127.127.1.0
refclock_receive: at 1 127.127.1.0
event at 1 LOCAL(0) 8014 84 reachable
refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000002
clock_filter: n 1 off 0.000000 del 0.000000 dsp 7.937501 jit 0.000002
auth_agekeys: at 1 keys 0 expired 0
restrictions: looking up 127.0.0.1
restrictions: looking up 127.0.0.1
restrictions: looking up 127.0.0.1
restrictions: looking up 127.0.0.1
restrictions: looking up 127.0.0.1
restrictions: looking up 127.0.0.1
refclock_transmit: at 65 127.127.1.0
refclock_receive: at 65 127.127.1.0
refclock_sample: n 1 offset 0.000000 disp 0.010000 jitter 0.000002
clock_filter: n 2 off 0.000000 del 0.000000 dsp 3.937741 jit 0.000002


    Generated Config in /etc/ntp.conf

      

    # Generated entries follow:
interface ignore wildcard
interface ignore ipv6
server 10.0.0.1 iburst
server pool.ntp.org iburst
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst

     

    Link to comment
    lepresidente

    It's working for me again with 6.12.1, thank you

    Test Info

      

    root@Zeus:~# ntpq
ntpq> peers
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 LOCAL(0)        .LOCL.          10 l    -   64    0    0.000   +0.000   0.000
-10.0.0.1 (OPNse 196.10.52.58     3 u   59  128  377    0.598   -7.694   5.025
+ntp3.inx.net.za 102.176.227.254  2 u   98  128  377   27.313   -0.840   3.399
*102.217.251.123 .GPS.            1 u   42  128  377   21.880  +10.473   4.609
+ntp5.inx.net.za 41.223.245.3     2 u   62  128  377    3.929   -0.279   6.828
ntpq> as
ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 57120  8014   yes    no  none    reject   reachable  1
  2 57121  9314   yes   yes  none   outlier   reachable  1
  3 57122  9424   yes   yes  none candidate   reachable  2
  4 57123  962a   yes   yes  none  sys.peer    sys_peer  2
  5 57124  942a   yes   yes  none candidate    sys_peer  2
ntpq>

     

    Edited by lepresidente
    • Like 1
    Link to comment


    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.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.