SOLVED How to fix incorrect time?

[TheDubiousDubber]

FreeNAS is showing the wrong time on one of my servers. Which I only noticed recently since it is causing issues with my PVR plugin. I have it set to the correct timezone, and the clock in bios is set to the proper time as well. I have no idea why it's displaying the wrong time but it remains quite a few hours off.

As of right now (10:30 CST) it is displaying 4:30 CST.

 

[DrKK]

Is the time difference exactly the difference between Zulu (UTC) time, and local time?

 

[TheDubiousDubber]

Not sure, just ran date 2250 and it set to correct time. Hopefully that fixes it. Seems to have worked for now.

Edit:

Just checked. It is exactly 6 hours behind and CST is 6 hours from UTC
Also tried running ntpd and it kept erroring out, something about not being able to bind to socket.

 

[DrKK]

Not sure, just ran date 2250 and it set to correct time. Hopefully that fixes it. Seems to have worked for now.

Edit:

Just checked. It is exactly 6 hours behind and CST is 6 hours from UTC
Also tried running ntpd and it kept erroring out, something about not being able to bind to socket.

Isn't there a question, on original install, "Is this system clock intended to represent UTC or local time?" I seem to recall that. Perhaps you answered wrong.

And also, ntpd should already be running (which is why you can't bind to the socket---it's already bound).

Try this:

Code:

[root@giskard] ~# ntpq -np
  remote  refid  st t when poll reach  delay  offset  jitter
==============================================================================
+204.2.134.162  204.123.2.72  2 u  516 1024  357  114.729  -3.096  18.343
+108.61.73.244  18.26.4.105  2 u  714 1024  377  16.246  1.416  1.185
*108.61.56.35  128.59.0.245  2 u  513 1024  377  12.799  0.572  1.634

 

[TheDubiousDubber]

I don't recall a question like that. I quit out of the wizard half way through so perhaps that is why. I configured it manually for the most part.

Ran that command and I get this:

Code:

  remote  refid  st t when poll reach  delay  offset  jitter
==============================================================================
*69.164.201.165  130.207.244.240  2 u  58  64  377  39.722  -20.510  4.576
+204.2.134.163  44.24.199.34  3 u  2  64  377  82.609  -20.127  9.938
+104.156.99.30  164.67.62.194  2 u  37  64  377  66.132  -14.213  7.022

 

[DrKK]

I don't recall a question like that. I quit out of the wizard half way through so perhaps that is why. I configured it manually for the most part.

Ran that command and I get this:

Code:

  remote  refid  st t when poll reach  delay  offset  jitter
==============================================================================
*69.164.201.165  130.207.244.240  2 u  58  64  377  39.722  -20.510  4.576
+204.2.134.163  44.24.199.34  3 u  2  64  377  82.609  -20.127  9.938
+104.156.99.30  164.67.62.194  2 u  37  64  377  66.132  -14.213  7.022

OK, well that means your ntpd is running correctly, and almost certainly tracking/setting your system clock as needed.

I think your problem was a too-large offset in the clock to start with; as I said, ntpd will refuse to deal with a clock that is too insanely off. Now that you manually updated the clock, ntpd can probably take it from here.