NTP clock sync

owner524 · Jul 3, 2013, 6:40 AM

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

gogol · Jul 3, 2013, 9:18 AM

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

owner524 · Jul 3, 2013, 6:04 PM

@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

gogol · Jul 3, 2013, 7:59 PM

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

owner524 · Jul 3, 2013, 10:46 PM

@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??

wallabybob · Jul 4, 2013, 12:47 AM

@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.

pfSenseRocks · Jul 4, 2013, 4:24 AM

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

gogol · Jul 4, 2013, 7:09 AM

@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.