Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Wierd bug: MULTIPLE:SINGLE?

    Scheduled Pinned Locked Moved Firewalling
    13 Posts 4 Posters 5.9k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E Offline
      energy
      last edited by

      @hoba:

      RC3b changes the ntp-daemon that is in use for syncing your time. Do you see lots of ntpd messages ( like Oct 4 08:10:11 ntpd[660]: adjusting local clock by 0.150322s ) in your systemlogs? Maybe your hardwareclock is not very accurate and it tries to compensate this by syncing very often? I checked states at one of my boxes that runs RC3b since a day before we released it and it only shows few connections like these and also not all the time. However ntpd seems to be a bit more active than the previously used version that was replaced due to having randomly kind of dns issues on some hardware.

      Yes its spamming like hell and its sending lots of packages, so its a bug that need to be fixed?

      1 Reply Last reply Reply Quote 0
      • H Offline
        hoba
        last edited by

        Maybe we need to have a closer look to only let ntp jump in to the specified periods. We'll look into it.

        1 Reply Last reply Reply Quote 0
        • E Offline
          energy
          last edited by

          My hardware clock is setup right but check out the system log:

          Oct 4 18:59:49 ntpd[1131]: adjusting local clock by 0.208591s
          Oct 4 18:48:12 ntpd[1131]: adjusting local clock by 0.144876s
          Oct 4 17:51:08 ntpd[1131]: adjusting local clock by 0.175209s
          Oct 4 17:46:53 ntpd[1131]: adjusting local clock by 0.228473s
          Oct 4 17:36:52 ntpd[1131]: adjusting local clock by 0.170004s
          Oct 4 16:27:00 ntpd[1131]: adjusting local clock by 0.187381s
          Oct 4 15:30:26 ntpd[1131]: adjusting local clock by 0.166316s
          Oct 4 15:27:04 ntpd[1131]: adjusting local clock by 0.252670s
          Oct 4 15:20:42 ntpd[1131]: adjusting local clock by 0.170410s
          Oct 4 14:17:06 ntpd[1131]: adjusting local clock by 0.140318s
          Oct 4 14:10:38 ntpd[1131]: adjusting local clock by 0.203578s
          Oct 4 14:00:32 ntpd[1131]: adjusting local clock by 0.219042s
          Oct 4 12:45:40 ntpd[1131]: adjusting local clock by 0.192782s
          Oct 4 12:38:23 ntpd[1131]: adjusting local clock by 0.174781s
          Oct 4 12:12:46 ntpd[1131]: adjusting local clock by -0.306057s
          Oct 4 12:09:40 ntpd[1131]: adjusting local clock by -1.844034s
          Oct 4 12:06:59 ntpd[1131]: adjusting local clock by -2.422097s
          Oct 4 12:04:11 ntpd[1131]: adjusting local clock by -3.195886s
          Oct 4 12:00:42 ntpd[1131]: adjusting local clock by -4.306083s
          Oct 4 11:56:56 ntpd[1131]: adjusting local clock by -5.861005s
          Oct 4 11:52:34 ntpd[1131]: adjusting local clock by -6.574293s
          Oct 4 11:48:50 ntpd[1131]: adjusting local clock by -7.879791s
          Oct 4 11:45:09 ntpd[1131]: adjusting local clock by -9.119301s
          Oct 4 11:41:19 ntpd[1131]: adjusting local clock by -10.229933s
          Oct 4 11:37:50 ntpd[1131]: adjusting local clock by -11.361811s
          Oct 4 11:34:41 ntpd[1131]: adjusting local clock by -12.165456s
          Oct 4 11:30:21 ntpd[1131]: adjusting local clock by -13.657401s
          Oct 4 11:28:30 ntpd[1131]: adjusting local clock by -14.681717s
          Oct 4 11:24:09 ntpd[1131]: adjusting local clock by -15.575149s
          Oct 4 11:22:01 ntpd[1131]: adjusting local clock by -16.541050s
          Oct 4 11:17:43 ntpd[1131]: adjusting local clock by -17.187066s
          Oct 4 11:15:02 ntpd[1131]: adjusting local clock by -18.556671s
          Oct 4 11:11:44 ntpd[1131]: adjusting local clock by -19.297054s
          Oct 4 11:07:38 ntpd[1131]: adjusting local clock by -20.383986s
          Oct 4 11:04:32 ntpd[1131]: adjusting local clock by -21.382426s
          Oct 4 11:00:13 ntpd[1131]: adjusting local clock by -22.650962s
          Oct 4 10:55:54 ntpd[1131]: adjusting local clock by -24.131263s
          Oct 4 10:52:09 ntpd[1131]: adjusting local clock by -25.482542s
          Oct 4 10:48:18 ntpd[1131]: adjusting local clock by -26.317656s
          Oct 4 10:46:02 ntpd[1131]: adjusting local clock by -27.360983s
          Oct 4 10:43:53 ntpd[1131]: adjusting local clock by -28.251769s
          Oct 4 10:41:12 ntpd[1131]: adjusting local clock by -28.717556s
          Oct 4 10:37:35 ntpd[1131]: adjusting local clock by -30.159572s
          Oct 4 10:33:42 ntpd[1131]: adjusting local clock by -31.241637s
          Oct 4 10:29:59 ntpd[1131]: adjusting local clock by -32.539856s
          Oct 4 10:26:55 ntpd[1131]: adjusting local clock by -33.061540s
          Oct 4 10:23:35 ntpd[1131]: adjusting local clock by -33.993178s
          Oct 4 10:20:19 ntpd[1131]: adjusting local clock by -35.136921s
          Oct 4 10:16:09 ntpd[1131]: adjusting local clock by -36.758732s
          Oct 4 10:13:20 ntpd[1131]: adjusting local clock by -37.223784s
          Oct 4 10:09:43 ntpd[1131]: adjusting local clock by -38.490783s
          Oct 4 10:06:01 ntpd[1131]: adjusting local clock by -39.261836s
          Oct 4 10:02:20 ntpd[1131]: adjusting local clock by -40.538240s
          Oct 4 09:59:36 ntpd[1131]: adjusting local clock by -41.759971s
          Oct 4 09:56:23 ntpd[1131]: adjusting local clock by -42.565387s
          Oct 4 09:53:21 ntpd[1131]: adjusting local clock by -43.679063s
          Oct 4 09:51:02 ntpd[1131]: adjusting local clock by -44.550676s
          Oct 4 09:47:26 ntpd[1131]: adjusting local clock by -45.461797s
          Oct 4 09:43:49 ntpd[1131]: adjusting local clock by -46.222141s
          Oct 4 09:40:23 ntpd[1131]: adjusting local clock by -47.694072s
          Oct 4 09:37:06 ntpd[1131]: adjusting local clock by -48.746400s
          Oct 4 09:33:21 ntpd[1131]: adjusting local clock by -50.021202s
          Oct 4 09:29:47 ntpd[1131]: adjusting local clock by -51.066253s
          Oct 4 09:26:01 ntpd[1131]: adjusting local clock by -51.894315s
          Oct 4 09:21:42 ntpd[1131]: adjusting local clock by -53.156179s
          Oct 4 09:17:58 ntpd[1131]: adjusting local clock by -54.381976s
          Oct 4 09:14:04 ntpd[1131]: adjusting local clock by -55.422368s
          Oct 4 09:12:26 ntpd[1131]: adjusting local clock by -56.479535s
          Oct 4 09:09:18 ntpd[1131]: adjusting local clock by -57.207745s
          Oct 4 09:06:48 ntpd[1131]: adjusting local clock by -57.557736s

          1 Reply Last reply Reply Quote 0
          • S Offline
            sullrich
            last edited by

            This is normal.  Your machines REAL TIME CLOCK is being adjusted.  The amount of times that it is doing this tells me your motherboards time keeping is crap, and it is fixing this.

            1 Reply Last reply Reply Quote 0
            • E Offline
              energy
              last edited by

              @sullrich:

              This is normal.  Your machines REAL TIME CLOCK is being adjusted.  The amount of times that it is doing this tells me your motherboards time keeping is crap, and it is fixing this.

              You say its normal but it still cant fix it cause its allways trying to fix it.

              1 Reply Last reply Reply Quote 0
              • H Offline
                hoba
                last edited by

                It's not always trying to fix it DOES fix it and keeps your broken clock accurate or at least it tries to do it's best. With the latest RC3 update these messages are in their own systemlogstab to not "spam" the main tab in kind your clock is really that broken.

                1 Reply Last reply Reply Quote 0
                • E Offline
                  enCecity
                  last edited by

                  me running on wrap from pcengines.ch

                  important note from doc http://www.pcengines.ch/wrap1c.pdf:
                  WRAP does not include a battery backup for the real-time clock (RTC).

                  1 Reply Last reply Reply Quote 0
                  • H Offline
                    hoba
                    last edited by

                    @enCecity:

                    me running on wrap from pcengines.ch

                    important note from doc http://www.pcengines.ch/wrap1c.pdf:
                    WRAP does not include a battery backup for the real-time clock (RTC).

                    That's no problem as it will do a timesync as soon as the specified timeserver is reachable right after bootup.

                    1 Reply Last reply Reply Quote 0
                    • E Offline
                      enCecity
                      last edited by

                      does this thread provide a solution to our problem?
                      http://forum.openwrt.org/viewtopic.php?pid=20909

                      1 Reply Last reply Reply Quote 0
                      • E Offline
                        enCecity
                        last edited by

                        never mind, consider it as done.
                        only point left: adjust txt on syslog to 'Last 50 OpenNTPD log entries'

                        1 Reply Last reply Reply Quote 0
                        • S Offline
                          sullrich
                          last edited by

                          Already fixed in cvs.  Thanks.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.