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

    NTP clock sync

    Scheduled Pinned Locked Moved
    2.1 Snapshot Feedback and Problems - RETIRED
    4
    8
    2.9k
    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.
    • O
      owner524
      last edited by

      i dont understand why i have so much trouble with the NTP clock thing it never starts ??

      Jul 3 02:31:42 ntp: Starting NTP Daemon.
      Jul 3 02:31:42 ntpd[38477]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:31:42 ntpd[38566]: proto: precision = 0.838 usec
      Jul 3 02:31:42 ntpd[38566]: ntp_io: estimated max descriptors: 11095, initial socket boundary: 20
      Jul 3 02:31:42 ntpd[38566]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
      Jul 3 02:31:42 ntpd[38566]: Listen and drop on 1 v6wildcard :: UDP 123
      Jul 3 02:31:42 ntpd[38566]: Listen normally on 2 re1 ... UDP 123
      Jul 3 02:31:42 ntpd[38566]: Listen normally on 3 re1 ... UDP 123
      Jul 3 02:31:42 ntpd[38566]: Listen normally on 4 lo0 127.0.0.1 UDP 123
      Jul 3 02:31:42 ntpd[38566]: Listen normally on 5 lo0 ::1 UDP 123
      Jul 3 02:31:42 ntpd[38566]: peers refreshed
      Jul 3 02:31:42 ntpd[38566]: Listening on routing socket on fd #26 for interface updates
      Jul 3 02:31:48 ntpd[38566]: ntpd exiting on signal 15
      Jul 3 02:31:50 ntpdate[98992]: adjust time server 64.85.165.128 offset -0.066381 sec
      Jul 3 02:31:50 ntp: Successfully synced time after 1 attempts.
      Jul 3 02:31:50 ntp: Starting NTP Daemon.
      Jul 3 02:31:50 ntpd[195]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:32:02 ntpd[6487]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:33:38 ntpdate[40376]: adjust time server 69.65.40.29 offset -0.109100 sec
      Jul 3 02:33:38 ntp: Successfully synced time after 1 attempts.
      Jul 3 02:33:38 ntp: Starting NTP Daemon.
      Jul 3 02:33:38 ntpd[41228]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:33:38 ntpd[41499]: proto: precision = 0.838 usec
      Jul 3 02:33:38 ntpd[41499]: ntp_io: estimated max descriptors: 11095, initial socket boundary: 20
      Jul 3 02:33:38 ntpd[41499]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
      Jul 3 02:33:38 ntpd[41499]: Listen and drop on 1 v6wildcard :: UDP 123
      Jul 3 02:33:38 ntpd[41499]: Listen normally on 2 re1 ... UDP 123
      Jul 3 02:33:38 ntpd[41499]: Listen normally on 3 re1 ... UDP 123
      Jul 3 02:33:38 ntpd[41499]: Listen normally on 4 lo0 127.0.0.1 UDP 123
      Jul 3 02:33:38 ntpd[41499]: Listen normally on 5 lo0 ::1 UDP 123
      Jul 3 02:33:38 ntpd[41499]: peers refreshed
      Jul 3 02:33:38 ntpd[41499]: Listening on routing socket on fd #26 for interface updates
      Jul 3 02:33:44 ntpd[41499]: ntpd exiting on signal 15
      Jul 3 02:33:46 ntpdate[86595]: adjust time server 69.65.40.29 offset -0.106208 sec
      Jul 3 02:33:46 ntp: Successfully synced time after 1 attempts.
      Jul 3 02:33:46 ntp: Starting NTP Daemon.
      Jul 3 02:33:46 ntpd[90624]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:34:41 ntpd[43805]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:34:50 ntpd[59433]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:37:30 ntpd[3366]: ntpd 4.2.6p5@1.2349-o Fri Jun 21 14:59:38 UTC 2013 (1)
      Jul 3 02:37:30 ntpd[3436]: proto: precision = 0.837 usec
      Jul 3 02:37:30 ntpd[3436]: ntp_io: estimated max descriptors: 11095, initial socket boundary: 20
      Jul 3 02:37:30 ntpd[3436]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
      Jul 3 02:37:30 ntpd[3436]: Listen and drop on 1 v6wildcard :: UDP 123
      Jul 3 02:37:30 ntpd[3436]: Listen normally on 2 re1 ... UDP 123
      Jul 3 02:37:30 ntpd[3436]: Listen normally on 3 re1 ... UDP 123
      Jul 3 02:37:30 ntpd[3436]: Listen normally on 4 lo0 127.0.0.1 UDP 123
      Jul 3 02:37:30 ntpd[3436]: Listen normally on 5 lo0 ::1 UDP 123
      Jul 3 02:37:30 ntpd[3436]: peers refreshed
      Jul 3 02:37:30 ntpd[3436]: Listening on routing socket on fd #28 for interface updates

      1 Reply Last reply Reply Quote 0
      • G
        gogol
        last edited by

        Can you define your troubles? This output looks the same as on my system after an upgrade

        1 Reply Last reply Reply Quote 0
        • O
          owner524
          last edited by

          @gogol:

          Can you define your troubles? This output looks the same as on my system after an upgrade

          I have two other PFsense boxes that I manage from different places plus my own the only thing that's different is mine is 64bit an the others aren't..  when I upgrade or reboot for something on the other box everything is good but when I do the same thing on my box the NTP service never starts an I don't know why I have to keep hitting start service

          1 Reply Last reply Reply Quote 0
          • G
            gogol
            last edited by

            Maybe you are not patient enough or looking at the wrong place. The last line in your logs says it is running after two exits on signal 15. Maybe that was you hitting the start service?
            Please go to shell after reboot or upgrade and post the output of:

            ps aux | grep ntpd
            1 Reply Last reply Reply Quote 0
            • O
              owner524
              last edited by

              @gogol:

              Maybe you are not patient enough or looking at the wrong place. The last line in your logs says it is running after two exits on signal 15. Maybe that was you hitting the start service?
              Please go to shell after reboot or upgrade and post the output of:

              ps aux | grep ntpd

              use that command to pull it up??

              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                @owner524:

                use that command to pull it up??

                No, to see if ntpd is still running.
                @gogol:

                The last line in your logs says it is running after two exits on signal 15.

                1 Reply Last reply Reply Quote 0
                • P
                  pfSenseRocks
                  last edited by

                  I reproduce the issue. I worked around it by selecting the interfaces on the NTP settings page.

                  1 Reply Last reply Reply Quote 0
                  • G
                    gogol
                    last edited by

                    @pfSenseRocks:

                    I reproduce the issue. I worked around it by selecting the interfaces on the NTP settings page.

                    I did that on my system and the only difference was that my system is now listening on an interface I did add later. So that was a good advice  ;)

                    But according to the log file the TS posted the last line said that NTPD is listening and running.

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